- What scenarios can the generated key pairs be used for?
- RSA key pairs are widely used for: 1) HTTPS/SSL certificates: Securing website communications; 2) SSH key authentication: Password-less server login; 3) Code signing: Verifying software origin and integrity; 4) Email encryption: PGP/GPG encrypted communications; 5) API authentication: JWT token signing; 6) Digital signatures: Legal proof for documents and transactions; 7) VPN connections: Establishing secure virtual private networks.
- How long does key generation take?
- Generation time depends on key length and device performance. Typically: 2048 bits ~1-3 seconds, 3072 bits ~3-8 seconds, 4096 bits ~5-15 seconds, 8192 bits may take 30+ seconds. First generation may be slower as random entropy needs to be collected. If unresponsive for extended time, refresh page and retry.
- What's the difference between PEM and DER formats?
- PEM (Privacy Enhanced Mail) is text format using Base64 encoding, starting with -----BEGIN RSA PRIVATE KEY-----, easy to copy-paste and view in text editors. DER (Distinguished Encoding Rules) is binary format with smaller file size but not directly readable, commonly used in Java and certain certificate systems. PEM format is recommended for most cases.
- How to verify if the generated key pair is valid?
- Tool auto-validates generated key pairs. You can also manually verify: 1) Validate format with OpenSSL: `openssl rsa -in private.pem -text -noout`; 2) Test encryption/decryption: Encrypt text with public key, decrypt with private key to verify original text recovery; 3) Check key length: Confirm key modulus bit count matches expected.
- Can public key be derived from private key?
- Yes. RSA private key contains all information needed to generate public key (modulus n and public exponent e). You can extract public key from private key using OpenSSL: `openssl rsa -in private.pem -pubout -out public.pem`. However, the reverse is not possible - public key cannot derive private key, which is the foundation of RSA security.
- How to securely store private keys?
- Best practices: 1) Encrypt private key with passphrase (e.g. `openssl rsa -aes256`); 2) Store in secure location: password managers (1Password, LastPass), hardware security modules (HSM), encrypted disk partitions; 3) Set strict file permissions (Linux: chmod 600); 4) Never commit to Git repositories; 5) Regular backups to offline storage; 6) Use multi-factor authentication to protect access.