पासफ़्रेज़ का उपयोग करके एन्क्रिप्टेड प्राइवेट की ऑफ़लाइन डिक्रिप्ट करें
PHP OpenSSL, Laravel, Symfony, Nginx और Node.js प्रोजेक्ट्स में पासफ़्रेज़-लॉक्ड PEM प्राइवेट की आम हैं। Bramhify का प्राइवेट की डिक्रिप्टर बिना OpenSSL CLI इंस्टॉल किए या किसी सर्वर पर की भेजे सीधे आपके ब्राउज़र में PKCS#8 और OpenSSL PEM कुंजियों को अनलॉक करता है, पब्लिक की निकालता है और JWK एक्सपोर्ट करता है।
Supported Encrypted Private Key Formats
BEGIN ENCRYPTED PRIVATE KEY): Modern RFC 5958 PBES2 containers using PBKDF2 (SHA-1, SHA-256, SHA-384, or SHA-512) with AES-128-CBC, AES-256-CBC, AES-128-GCM, or AES-256-GCM.Proc-Type: 4,ENCRYPTED): Traditional PKCS#1 RSA (BEGIN RSA PRIVATE KEY) and SEC1 EC (BEGIN EC PRIVATE KEY) keys encrypted with AES-128-CBC or AES-256-CBC via EVP_BytesToKey — commonly generated by PHP OpenSSL and older tutorials.BEGIN PUBLIC KEY), computes its SHA-256 fingerprint, and converts the private key to JWK for immediate use in JWT libraries.Encrypt (Re-Lock) Unencrypted Keys with a New Passphrase
Need to protect a plaintext PKCS#8, PKCS#1 RSA, or SEC1 EC private key before storing it in CI/CD secrets or a PHP project? Switch to Encrypt Key (Lock) mode, paste your unencrypted private key, enter a strong passphrase, and export an OpenSSL-compatible BEGIN ENCRYPTED PRIVATE KEY block protected with PBKDF2-SHA256 (100,000 iterations) and AES-256-CBC.
Security Guarantee & Known Limitations
All ASN.1 DER parsing, key derivation, and AES decryption run inside your browser's volatile RAM — zero network calls, zero localStorage, and an instant Wipe Memory button. Limitations: OpenSSH private keys (BEGIN OPENSSH PRIVATE KEY) rely on bcrypt-pbkdf, and obsolete 3DES/DES-CBC keys use deprecated ciphers not exposed by browser Web Crypto; convert those locally with ssh-keygen or openssl pkcs8 first. Need a brand-new key pair? Try our Public & Private Key Pair Generator or inspect tokens in our JWT & SD-JWT Decoder.
Frequently Asked Questions
Why does PHP or OpenSSL throw EVP_DecryptFinal_ex:bad decrypt? That error almost always means the passphrase in your .env file does not match the encrypted PEM key (often caused by trailing spaces, unescaped $ characters, or quoting issues). Paste your PEM key and passphrase here to test decryption instantly offline, and compare the derived SHA-256 public key fingerprint against your certificate or JWKS endpoint.
