1
0
mirror of https://github.com/danog/phpseclib.git synced 2024-11-27 12:55:58 +01:00
Go to file
Andreas Fischer 18cc8eb1c3 Merge branch '2.0'
* 2.0:
  Fix PHP invalid index warning
2015-11-24 09:28:00 +01:00
build Merge branch 'PSR2-1.0' into PSR2-2.0 2015-07-17 13:41:59 +02:00
phpseclib Merge branch '2.0' 2015-11-24 09:28:00 +01:00
tests Merge branch '2.0' 2015-11-10 10:23:08 +01:00
travis Backport to 2.0: Add PHP7 to Travis CI. 2015-09-02 20:26:11 +02: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
.travis.yml No longer allow Travis CI to fail on PHP 7. 2015-09-14 14:09:56 +02:00
AUTHORS AUTHORS: add GrahamCampbell 2015-09-15 13:23:52 -05:00
CHANGELOG.md update phpseclib to 1.0.0 2015-08-03 21:22:12 -05:00
composer.json Merge branch '1.0' into 2.0 2015-09-16 13:31:01 +02:00
composer.lock Merge branch '1.0' into 2.0 2015-09-16 13:31:01 +02: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 '2.0' 2015-11-19 09:38:20 +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
    

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