PHP Secure Communications Library
Go to file
2015-07-17 12:57:41 +02:00
build Base code sniffer ruleset on PSR2 rather than PEAR. 2015-07-17 12:57:04 +02:00
phpseclib Use phpcbf to fix PHP code to ruleset. 2015-07-17 12:57:41 +02:00
tests Use phpcbf to fix PHP code to ruleset. 2015-07-17 12:57:41 +02:00
travis Scrutinizer CI: Unconfigure external code coverage. This keeps timing out. 2015-07-04 02:04:21 +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 Scrutinizer CI: Unconfigure external code coverage. This keeps timing out. 2015-07-04 02:04:21 +02: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 Update PHP Code Sniffer to 2.3.3 2015-07-17 12:57:04 +02:00
composer.lock Update PHP Code Sniffer to 2.3.3 2015-07-17 12:57:04 +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 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