PHP Secure Communications Library
Go to file
2017-05-14 08:49:04 -05:00
build Remove PSR2.Methods.FunctionCallSignature.SpaceAfterOpenBracket exception. 2015-07-17 12:57:41 +02:00
phpseclib X509: include subjectaltname extension even if only one domain name 2017-05-14 08:49:04 -05:00
tests Fixed ASN.1 UTCTime parsing 2017-04-09 10:15:40 -05: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: rm hhvm 2017-05-07 15:07:04 -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: add 1.0.6 release 2017-05-08 00:58:24 -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