diff options
author | Nick Mathewson <nickm@torproject.org> | 2018-05-24 09:40:06 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2018-05-24 09:40:06 -0400 |
commit | f48fb8a720c7cca79249248f92e3bc99cee3414d (patch) | |
tree | f0284c6e1f69f1137f417aadb0feb49b2f2ec4ee /src | |
parent | d3a972561aeb38d7b346be1826054c60bf3adfaa (diff) | |
parent | c380562aed5242eab6449b054199d742f02833dd (diff) | |
download | tor-f48fb8a720c7cca79249248f92e3bc99cee3414d.tar.gz tor-f48fb8a720c7cca79249248f92e3bc99cee3414d.zip |
Merge branch 'maint-0.2.9' into maint-0.3.1
Diffstat (limited to 'src')
-rw-r--r-- | src/common/crypto.c | 7 | ||||
-rw-r--r-- | src/test/test_crypto.c | 41 |
2 files changed, 47 insertions, 1 deletions
diff --git a/src/common/crypto.c b/src/common/crypto.c index b82f181a39..d2801e0d45 100644 --- a/src/common/crypto.c +++ b/src/common/crypto.c @@ -653,7 +653,12 @@ pem_no_password_cb(char *buf, int size, int rwflag, void *u) (void)size; (void)rwflag; (void)u; - return 0; + /* The openssl documentation says that a callback "must" return 0 if an + * error occurred. But during the 1.1.1 series (commit c82c3462267afdbbaa5 + * they changed the interpretation so that 0 indicates an empty password and + * -1 indicates an error. We want to reject any encrypted PEM buffers, so we + * return -1. This will work on older OpenSSL versions and LibreSSL too. */ + return -1; } /** Read a PEM-encoded private key from the <b>len</b>-byte string <b>s</b> diff --git a/src/test/test_crypto.c b/src/test/test_crypto.c index ec9d4e2709..75cd30ebb5 100644 --- a/src/test/test_crypto.c +++ b/src/test/test_crypto.c @@ -1362,6 +1362,46 @@ test_crypto_pk_base64(void *arg) tor_free(encoded); } +static void +test_crypto_pk_pem_encrypted(void *arg) +{ + crypto_pk_t *pk = NULL; + (void)arg; + + pk = crypto_pk_new(); + /* we need to make sure that we won't stall if somebody gives us a key + that's encrypted with a password. */ + { + const char *s = + "-----BEGIN RSA PRIVATE KEY-----\n" + "Proc-Type: 4,ENCRYPTED\n" + "DEK-Info: AES-128-CBC,EFA86BB9D2AB11E80B4E3DCD97782B16\n" + "\n" + "Z2Je4m0cFepc6coQkVbGcvNCHxTf941N2XYEVE6kn0CqWqoUH4tlwV6for5D91np\n" + "5NiEFTkWj31EhrvrYcuiJtQ/iEbABxZULFWFeJ058rb+1izBz5rScqnEacIS/3Go\n" + "YntnROBDwiKmUnue6PJVYg==\n" + "-----END RSA PRIVATE KEY-----\n"; + tt_int_op(-1, OP_EQ, + crypto_pk_read_private_key_from_string(pk, s, strlen(s))); + } + /* For fun, make sure we aren't hit by OpenSSL issue + https://github.com/openssl/openssl/issues/6347 , where we get in trouble + if a cipher doesn't use an IV. + */ + { + const char *s = + "-----BEGIN RSA PUBLIC KEY-----\n" + "Proc-Type:4,ENCRYPTED\n" + "DEK-Info:des-ede -\n" + "\n" + "iRqK\n" + "-----END RSA PUBLIC KEY-----\n"; + tt_int_op(-1, OP_EQ, + crypto_pk_read_public_key_from_string(pk, s, strlen(s))); + } + done: + crypto_pk_free(pk); +} #ifdef HAVE_TRUNCATE #define do_truncate truncate #else @@ -2890,6 +2930,7 @@ struct testcase_t crypto_tests[] = { CRYPTO_LEGACY(pk), { "pk_fingerprints", test_crypto_pk_fingerprints, TT_FORK, NULL, NULL }, { "pk_base64", test_crypto_pk_base64, TT_FORK, NULL, NULL }, + { "pk_pem_encrypted", test_crypto_pk_pem_encrypted, TT_FORK, NULL, NULL }, CRYPTO_LEGACY(digests), { "digest_names", test_crypto_digest_names, 0, NULL, NULL }, { "sha3", test_crypto_sha3, TT_FORK, NULL, NULL}, |