PHP Secure Communications Library
Go to file
2019-01-16 21:15:11 -06:00
build Remove PSR2.Methods.FunctionCallSignature.SpaceAfterOpenBracket exception. 2015-07-17 12:57:41 +02:00
phpseclib SSH2: ssh-rsa is sometimes incorrectly used instead of rsa-sha2-256 2019-01-16 21:15:11 -06:00
tests Tests/X509: add validatedate unit test 2018-11-22 12:40:32 -06:00
travis allow PHPUnit 4, 5 and 6 2017-12-14 23:25:30 -06:00
.gitattributes Exclude some dirs and files from repository auto-generated ZIP archives 2016-01-12 09:37:17 -06:00
.gitignore allow PHPUnit 4, 5 and 6 2017-12-14 23:25:30 -06:00
.travis.yml Update .travis.yml 2018-10-27 17:42:38 -05:00
appveyor.yml add appveyor.yml 2018-05-19 13:46:14 -05:00
AUTHORS AUTHORS: add GrahamCampbell 2015-09-15 13:23:52 -05:00
CHANGELOG.md 1.0.12 release 2018-11-04 00:38:52 -05:00
composer.json allow PHPUnit 4, 5 and 6 2017-12-14 23:25:30 -06: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: Declare 2.0 branch as LTS. #1310 2018-11-14 21:42:06 +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

Documentation

Branches

master

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

2.0

  • Long term support (LTS) release
  • 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