1
0
mirror of https://github.com/danog/tgseclib.git synced 2024-12-11 16:49:41 +01:00
Go to file
terrafrost 44c2003d4b
Merge pull request #1295 from grongor/fix-wrong-method-name
Fix invalid method name + usages in comments
2018-09-17 00:45:19 -05:00
build Merge branch 'PSR2-1.0' into PSR2-2.0 2015-07-17 13:41:59 +02:00
phpseclib Merge pull request #1295 from grongor/fix-wrong-method-name 2018-09-17 00:45:19 -05:00
tests Merge branch '2.0' 2018-09-17 00:29:24 -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 rm PHP 5.4 from Travis 2018-01-22 06:56:26 -06: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 Merge branch '1.0' into 2.0 2018-04-15 11:55:05 -05:00
composer.json Merge branch '2.0' 2017-12-14 23:52:18 -06: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 Fix composer require syntax in readme 2018-05-10 15:51:30 +02: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