This entry is part 4 of 6 in the series PKI

One of the more interesting approaches to preventing brute force cracking is to actually use MULTIPLE private keys that all map to the SAME public key.

Now, only ONE of these keys is assigned to our user (Alice). What the assignment process is – is not too relevant. All Alice knows is that she has a key pair – and her private key is possibly one of many.

A hacker can now listen in and see the encrypted data and reverse engineer this encrypted data to retrieve the private key (a computationally difficult task).

Let us say the hacker is successful in doing so. All the hacker has done is retrieve A private key – not THE private key (since all those private keys map to the same public key!)

 

Also read – Different key pairs for signature and encryption and Group Encryption Keys

 

Anuj holds professional certifications in Google Cloud, AWS as well as certifications in Docker and App Performance Tools such as New Relic. He specializes in Cloud Security, Data Encryption and Container Technologies.

Initial Consultation

Anuj Varma – who has written posts on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.


Series NavigationGroup Encryption KeysEncryption and Signing – Same Key Pair – or different key pairs?