PHP Secure Communications Library
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
terrafrost 07605e9ce8
Tests: master branch uses ParaTest vs PHPUnit
2 days ago
.github GitHub Actions: add PHP 8.2 2 months ago
build Remove bootstrap.php 4 months ago
phpseclib Merge branch '3.0' 2 days ago
tests Tests: master branch uses ParaTest vs PHPUnit 2 days ago
.gitattributes Update .gitattributes 10 months ago
.gitignore Upgrade to PHP 7.0 7 months ago
AUTHORS Update authors - jack worman 6 months ago
BACKERS.md BACKERS: add cjhaas. thank you! 3 weeks ago
CHANGELOG.md Merge branch '2.0' into 3.0 2 months ago
LICENSE update copyright years on license 4 years ago
README.md Paratest 4 months ago
composer.json Remove bootstrap.php 4 months ago

README.md

phpseclib - PHP Secure Communications Library

CI Status

Supporting phpseclib

Introduction

MIT-licensed pure-PHP implementations of the following:

SSH-2, SFTP, X.509, an arbitrary-precision integer arithmetic library, Ed25519 / Ed449 / Curve25519 / Curve449, ECDSA / ECDH (with support for 66 curves), RSA (PKCS#1 v2.2 compliant), DSA / DH, DES / 3DES / RC4 / Rijndael / AES / Blowfish / Twofish / Salsa20 / ChaCha20, GCM / Poly1305

Documentation

Branches

master

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

3.0

  • Long term support (LTS) release
  • Major expansion of cryptographic primitives
  • Minimum PHP version: 5.6.1
  • PSR-4 autoloading with namespace rooted at \phpseclib3
  • Install via Composer: composer require phpseclib/phpseclib:~3.0

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?

Special Thanks

Special Thanks to our $50+ sponsors!:

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. Run continuous integration checks:

    composer run-script all-quality-tools
    
  6. Send us a Pull Request