PHP Secure Communications Library
Go to file
2019-07-12 07:39:59 -05:00
build Merge branch 'PSR2-1.0' into PSR2-2.0 2015-07-17 13:41:59 +02:00
phpseclib Merge branch 'update-auto-channel-close-2.0' into update-auto-channel-close-master 2019-07-12 07:39:59 -05:00
tests mv Keys/ and Signature/ to Formats/* 2019-06-25 07:52:45 -05:00
travis allow PHPUnit 4, 5 and 6 2017-12-14 23:25:30 -06:00
.gitattributes Revert "Merge branch '2.0'" 2016-04-10 11:30:59 -05:00
.gitignore Merge branch '2.0' 2017-12-14 23:52:18 -06:00
.travis.yml Merge branch '2.0' 2019-06-23 11:08:42 -05:00
appveyor.yml add appveyor.yml 2018-05-19 13:46:14 -05:00
AUTHORS Revert "Merge branch '2.0'" 2016-04-10 11:30:59 -05:00
CHANGELOG.md CHANGELOG: add 2.0.19 and 2.0.20 entries 2019-06-23 11:17:42 -05:00
composer.json Merge branch '2.0' 2017-12-14 23:52:18 -06:00
LICENSE update copyright years on license 2019-07-02 06:42:17 -05:00
phpunit.xml.dist Split Unit/Functional Test Suites. 2014-06-01 21:13:20 +02:00
README.md Merge branch '2.0' 2019-07-02 07:12:24 -05:00

phpseclib - PHP Secure Communications Library

Build Status

Supporting phpseclib

Introduction

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

Security contact information

To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure.

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