phpseclib 2.0 polyfill built with phpseclib 3.0

1.0.6 2024-02-26 14:37 UTC

This package is auto-updated.

Last update: 2024-03-26 14:48:07 UTC


CI Status

phpseclib 2.0 polyfill built with phpseclib 3.0


phpseclib 3.0 breaks backwards compatability with phpseclib 2.0. Most notably, public keys work completely differently. So let's say you wanted to use phpseclib 3.0 whilst some of your other dependencies still use phpseclib 2.0. What would you do in that instance?

That's where phpseclib2_compat comes into play. Require phpseclib/phpseclib:~3.0 and phpseclib/phpseclib2_compat:~1.0 and your dependencies will magically start using phpseclib 3.0 even if they don't know it.

Using phpseclib2_compat will actually bring a few enhancements to your dependencies. For example, while phpseclib 2.0 only supports RSA keys phpseclib2_compat sports support for ECDSA / DSA / Ed25519 / Ed449 keys.

Consider this code sample:

use phpseclib\Crypt\RSA;

$rsa = new RSA;
$rsa->loadKey('ecdsa private key');

$ssh = new SSH2('');
$ssh->login('username', $rsa);

That'll work with phpseclib2_compat, even with an ECDSA private key, whereas in phpseclib 2.0 it would not work.

SSH1 and SCP are not supported but those were likely never frequently used anyway.

Using the old cipher suite

phpseclib 3.0 uses a different cipher suite (an expanded one) than 2.0. If this causes you issues you can use the 2.0 ciphersuite by doing this prior to calling $ssh->login():

$methods = [
    'crypt' => array_intersect([
    ], $ssh->getSupportedEncryptionAlgorithms()),
    'mac' => [
    'comp' => ['none']

    'kex' => [
    'hostkey' => [
    'client_to_server' => $methods,
    'server_to_client' => $methods


With Composer:

composer require phpseclib/phpseclib2_compat:~1.0