PHP Secure Communications Library
Go to file
2016-12-18 10:32:35 +01:00
build Remove PSR2.Methods.FunctionCallSignature.SpaceAfterOpenBracket exception. 2015-07-17 12:57:41 +02:00
phpseclib exec authentication, code reuse 2016-12-17 16:37:04 -06:00
tests Backport tests/bootstrap.php from 2.0 / master onto 1.0. 2016-10-20 21:30:42 +02:00
travis Travis: PHP 7.1 tweaks 2016-09-24 11:57:59 -05:00
.gitattributes Exclude some dirs and files from repository auto-generated ZIP archives 2016-01-12 09:37:17 -06:00
.gitignore Only apply git ignores relative to repository root. 2013-11-23 20:33:37 +01:00
.travis.yml Travis: PHP 7.1 tweaks 2016-09-24 11:57:59 -05:00
AUTHORS AUTHORS: add GrahamCampbell 2015-09-15 13:23:52 -05:00
CHANGELOG.md update for 1.0.5 release.. 2016-10-22 12:53:16 -05:00
composer.json Composer: include bootstrap before Crypt/Random 2016-10-22 11:13:01 -05:00
composer.lock Composer: update lock file 2016-10-22 22:57:15 -05:00
LICENSE Update license year range to 2016 2016-01-18 10:27:43 -06:00
phpunit.xml.dist Split Unit/Functional Test Suites. 2014-06-01 21:13:20 +02:00
README.md README: Update Coverage and API URLs. 2016-12-18 10:32:35 +01:00

phpseclib - PHP Secure Communications Library

Build Status

MIT-licensed pure-PHP implementations of an arbitrary-precision integer arithmetic library, fully PKCS#1 (v2.1) compliant RSA, DES, 3DES, RC4, Rijndael, AES, Blowfish, Twofish, SSH-1, SSH-2, SFTP, and X.509

PEAR Channel PEAR Channel: [phpseclib.sourceforge.net](http://phpseclib.sourceforge.net/pear.htm)

Documentation

Support

Need Support?

Installing Development Dependencies

Dependencies are managed via Composer.

  1. Download the composer.phar executable as per the Composer Download Instructions, e.g. by running

    curl -sS https://getcomposer.org/installer | php
    
  2. Install Dependencies

    php composer.phar install
    

Contributing

  1. Fork the Project

  2. Install Development Dependencies

  3. Create a Feature Branch

  4. (Recommended) Run the Test Suite

    vendor/bin/phpunit
    
  5. (Recommended) Check whether your code conforms to our Coding Standards by running

    vendor/bin/phing -f build/build.xml sniff
    
  6. Send us a Pull Request