1
0
mirror of https://github.com/danog/phpseclib.git synced 2024-12-11 00:29:36 +01:00
Go to file
2014-12-15 14:29:34 -08:00
build Merge branch 'master' into php5 2014-07-20 21:22:19 +02:00
phpseclib Temporary constant fix 2014-12-15 14:29:34 -08:00
tests Updated unit tests 2014-12-15 14:29:34 -08:00
travis Run HHVM tests in parallel. 2014-12-14 01:27:57 +01:00
.gitattributes added build status and extra lines 2012-06-11 02:30:46 -06:00
.gitignore Only apply git ignores relative to repository root. 2013-11-23 20:33:37 +01:00
.scrutinizer.yml Specify the runs option for external code coverage. 2014-06-01 13:52:24 +02:00
.travis.yml Merge branch 'master' into php5 2014-12-14 01:51:44 +01:00
AUTHORS AUTHORS: add more developers 2013-03-11 16:36:27 -05:00
CHANGELOG.md add CHANGELOG.md 2014-11-09 20:30:27 -06:00
composer.json Merge branch 'master' into php5 2014-12-03 12:30:55 +01:00
composer.lock Merge branch 'master' into php5 2014-12-12 22:21:54 +01:00
LICENSE Updated LICENSE 2013-11-23 21:18:24 +01:00
phpunit.xml.dist Split Unit/Functional Test Suites. 2014-06-01 21:13:20 +02:00
README.md Merge branch 'master' into php5 2014-11-14 00:35:35 +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

PEAR Channel PEAR Channel: [phpseclib.sourceforge.net](http://phpseclib.sourceforge.net/pear.htm)

Documentation

Support

Need Support?

Installing Development Dependencies

Dependencies are managed via Composer.

  1. Download the composer.phar executable as per the Composer Download Instructions, e.g. by running

    curl -sS https://getcomposer.org/installer | php
    
  2. Install Dependencies

    php composer.phar install --dev
    

Contributing

  1. Fork the Project

  2. Install Development Dependencies

  3. Create a Feature Branch

  4. (Recommended) Run the Test Suite

    vendor/bin/phpunit
    
  5. (Recommended) Check whether your code conforms to our Coding Standards by running

    vendor/bin/phing -f build/build.xml sniff
    
  6. Send us a Pull Request