PHP Secure Communications Library
Go to file
2015-05-23 17:39:17 -05:00
build Adjust sami.conf.php to new branch names. 2015-02-04 16:53:39 +01:00
phpseclib ANSI: fix typo 2015-05-23 17:39:17 -05:00
tests RSA: backport getPublicKeyFingerprint from Lukas-W's PR 2015-05-06 22:55:12 -05:00
travis SSH agent forwarding implementation 2014-12-30 10:44:31 +08: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 PHP 5.2 is not supported by travis anymore 2015-02-07 15:44:23 +00:00
.travis.yml PHP 5.2 is not supported by travis anymore 2015-02-07 15:44:23 +00:00
AUTHORS AUTHORS: add more developers 2013-03-11 16:36:27 -05:00
CHANGELOG.md CHANGELOG: add clarification 2015-02-09 07:56:10 -06:00
composer.json Removed old branch alias 2015-02-07 15:35:37 +00:00
composer.lock Updated dependencies 2015-02-07 15:35:42 +00: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 README: rm codeclimate badge 2015-05-07 08:16:03 -05: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