TypeError: Invalid private key pem file when run crypto.privateDecrypt
#12287
Labels
Comments
mishbah
changed the title
TypeError: Invalid private key pem file when run crypto.privateDecrypt
|
This can only happen when the passphrase is empty, which seems to be an issue with BoringSSL upstream. I reported it at https://issues.chromium.org/issues/362788352. |
|
so, what can I do for this? |
|
The fix has been included in BoringSSL upstream. You'll have to wait for Bun's BoringSSL fork to include the fix and then wait for a new Bun release. Alternatively, don't use an empty passphrase and your code snippet should work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Bun is running?
1.1.17
What platform is your computer?
Linux 5.15.0-107-generic x86_64 x86_64
What steps can reproduce the bug?
I follow tutorial from this site https://www.geeksforgeeks.org/node-js-crypto-privatedecrypt-method/ at "Example 2"
and when I try to run
bun src/index.jsshow up the error:
TypeError: Invalid private key pem fileWhat is the expected behavior?
Plaintext: Geeks!
Encrypted Text:
ACks6H7InpaeGdI4w9MObyD73YB7N1V0nVsG5Jl10SNeH3no6gfgjeD4ZFsSFhCXzFkognMGbRNsg0BReVOHxRs7eQ==
Decrypted Text: Geeks!
What do you see instead?
Plaintext: Geeks!
Encrypted Text: EQfTaY5gnk8wUiDNhsuFO9yJvZjF4qjdeCxg aWUqrKoDS7l6d5nTfnLaZlHN1mMMpGdcYTWSIjZTakIWtREhw==
43 | // Creating a function to decrypt string
44 | function decryptString(ciphertext, privateKeyFile) {
45 | const privateKey = fs.readFileSync(privateKeyFile, "utf8");
46 |
47 | // privateDecrypt() method with its parameters
48 | const decrypted = crypto.privateDecrypt(
^
TypeError: Invalid private key pem file
at node:crypto:66:32
at node:crypto:16:25
at node:crypto:9227:39
at decryptString (/home/my_name/my_project/src/test.js:48:28)
Additional information
if using
pnpmworking wellThe text was updated successfully, but these errors were encountered: