格 千格 KiloCell

RSA Key pair generator

Locally generate high-intensity public-private key pairs, supporting PEM and JWK export

Public Key PUBLIC
Copied
Private Key PRIVATE
Copied
Privacy security assurances: All keys are locally generated in your browser and will never be uploaded to any server.

RSA Key-to-Key Generator: Addressing the core pain points of security authentication and encryption

In the modern web architecture, the Internet is not a place for people to be. RSA Asymmetric Encryption It is the cornerstone for securing data transmission, achieving API signature authentication and remote SSH login. However, manually use OpenSSL The command line tool generates not only high thresholds but also security loopholes due to inappropriate parameter configuration. This tool is intended to provide a Zero threshold, high performance, absolute privacy. The online generation programme.

1. Why choose local online generation (Brownser-Side General)?

Many developers are concerned that online tools will store the generated private key. This tool is based on the browser Web Crypto API The core strengths of achieving this are:

  • Privacy: Key Generation Logic is fully running in your browser sandbox, and there is no network request to send the key to the back.
  • Speed: The acceleration is done using hardware, even with a high-intensity key of 4096 bits in seconds.
  • Compliance: The generated PEM file in the PKCS#8 format is directly used in mainstream backend environments such as Java, Python, Node.js.

2. Professional recommendations on key length and format

As an expert on project landings, I recommend the following configuration in different scenarios:

  1. Standard Web application: Selection 2048 bit Key. It strikes a perfect balance between safety intensity and decryption performance, and is the industry standard for most scenarios.
  2. Financial/government security: You have to choose. 4096 places 。 While performance costs have increased by about 4-8 times, they have been effective in resisting all known attempts at violent decomposition.
  3. Modern front-end interaction: Recommended JWK (JSON Web Key) format. It can be directly identified by front-end encryption libraries (e.g. Jose, WebCrypto) without cumbersome PEM resolution steps.

3. Common operational questions answers (FAQ)

Q: What is the difference between PKCS#1 and PKCS#8?
A: PKCS#1 is an old RSA exclusive standard, and PKCS#8 It is a more common standard that supports more encryption algorithms. This tool is by default exported to PKCS#8, as it has better cross-language compatibility.

Q: Why does the public key that is exported look much shorter than the private key?
A: This is the asymmetric encryption feature. Public key contains only the number of simulators (Modulus) and the index (Exponent), while the private key contains multiple prime factor for acceleration. In RSA-2048, private keys are usually about 1.6 KB, and the public key is only about 450 bytes.

Q: How to use the resulting key on the Linux server?
A: After downloading a private key file, use chmod 600 private_key.pem Modify permissions, i.e. available for use ssh -i Login or configure the SSL certificate for Nginx. The public key has to be added to the server ~/.ssh/authorized_keys document.

Operation successfully