PHP Secure Communications Library
Go to file
2017-11-04 09:42:15 -05:00
build Merge branch 'PSR2-1.0' into PSR2-2.0 2015-07-17 13:41:59 +02:00
phpseclib BigInteger/Engines/PHP: fix issue with regular barrett engine 2017-11-04 02:16:01 -05:00
tests Tests/BigInteger: re-enable primality testing in 32-bit PHP7 2017-11-04 09:42:15 -05:00
travis Travis: PHP 7.1 tweaks 2016-09-24 11:57:59 -05:00
.gitattributes Revert "Merge branch '2.0'" 2016-04-10 11:30:59 -05:00
.gitignore More PHPDOC fixes 2017-08-04 12:06:25 +02:00
.travis.yml Merge branch '2.0' 2017-09-05 22:52:46 -05:00
AUTHORS Revert "Merge branch '2.0'" 2016-04-10 11:30:59 -05:00
CHANGELOG.md Merge branch '2.0' 2017-10-23 00:09:07 -05:00
composer.json Composer: update deps 2017-08-29 22:42:24 -05:00
composer.lock Revert "Composer: update lock file" 2017-09-05 23:06:39 -05:00
LICENSE Revert "Merge branch '2.0'" 2016-04-10 11:30:59 -05:00
phpunit.xml.dist Split Unit/Functional Test Suites. 2014-06-01 21:13:20 +02:00
README.md Merge branch '2.0' 2017-10-23 00:09:07 -05: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

Documentation

Branches

master

  • Development Branch
  • Unstable API
  • Do not use in production

2.0

  • Modernized version of 1.0
  • Minimum PHP version: 5.3.3
  • PSR-4 autoloading with namespace rooted at \phpseclib
  • Install via Composer: composer require phpseclib/phpseclib ~2.0

1.0

Support

Need Support?

Contributing

  1. Fork the Project

  2. Ensure you have Composer installed (see Composer Download Instructions)

  3. Install Development Dependencies

    composer install
    
  4. Create a Feature Branch

  5. (Recommended) Run the Test Suite

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

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