PKI
Introduction
PKI
-
Public key infrastructure
Public key infrastructure (PKI) is a set of tools
(technical, material, human, etc.), distributed services and
components used together to support cryptographic tasks based on
private and public keys.
RFC 5280
PKI is based on the use of a public key cryptographic system and several basic principles:
- the private key is known only to its owner;
- the certificate authority creates an electronic document — a public key certificate, thus certifying the fact that the private (secret) key is known exclusively to the owner of this certificate, while the public key is freely transmitted in the certificate;
- nobody trusts each other, but everyone trusts the certificate authority;
- the certificate authority confirms or refutes the belonging of the public key to a given person who owns the corresponding private key.
History
Asymmetric ciphers began with the paper «New Directions in Modern Cryptography»
by Whitfield Diffie and Martin Hellman, published in 1976.
Influenced by the work of Ralph Merkle on public key distribution,
they proposed a method for obtaining secret keys using a public channel.
This method of exponential key exchange, which became known as the Diffie — Hellman key exchange,
was the first published practical method for establishing a shared secret key between
authenticated users of a channel.
In 2002 Hellman proposed calling this algorithm «Diffie — Hellman — Merkle», acknowledging the contribution
of Merkle to the invention of public key cryptography.
The same scheme was developed by Malcolm Williamson in the 1970s, but it was kept secret until 1997.
Merkle's method for distributing a public key was invented in 1974 and published in 1978,
it is also called Merkle's puzzle.
In 1977 the scientists Ronald Rivest, Adi Shamir and Leonard Adleman from the Massachusetts
Institute of Technology developed an encryption algorithm based on the problem of factoring
into primes. The system was named after the first letters of their surnames (RSA — Rivest, Shamir, Adleman).
The same system was invented in 1973 by Clifford Cocks, who worked at the
Government Communications Headquarters (GCHQ), but this work was kept only in the centre's internal documents, so its existence was unknown until 1977. RSA became the first algorithm suitable both for encryption and for electronic signatures.
Main Components of PKI
-
Certificate Authority also known as the certification centre (CA - Certificate Authority)
is the main structure that forms digital certificates of subordinate certification authorities and
end users. The CA is the main component of PKI:
- it is a trusted third party
- it is a server that manages the certificate lifecycle (but not their direct use).
- Public Key Certificate (most often simply a certificate) — these are the data of the user/server and its public key, bound by the electronic signature of the certificate authority. By issuing a public key certificate, the certificate authority thereby confirms that the person named in the certificate owns the private key that corresponds to this public key.
- Registration Authority (RA) — an optional component of the system intended for registering users. The certificate authority trusts the registration authority to verify information about the subject. The registration authority, having verified the correctness of the information, signs it with its key and passes it to the certificate authority, which, having verified the registration authority's key, issues a certificate. One registration authority can work with several certificate authorities (that is, be part of several PKIs), one certificate authority can work with several registration authorities. Sometimes the certificate authority performs the functions of a registration authority.
- Repository — a storage containing certificates and certificate revocation lists (CRLs) and serving to distribute these objects among users. In Federal Law of the Russian Federation No. 63 «On Electronic Signature» it is called the register of signature key certificates.
- Certificate Archive — a storage of all certificates ever issued (including certificates with an expired validity period). The archive is used to verify the authenticity of the electronic signature with which documents were certified.
- Request Centre — an optional component of the system where end users can request or revoke a certificate.
- End Users — users, applications or systems that own a certificate and use the public key management infrastructure.
Main Tasks
The main tasks of an information security system that the public key management infrastructure solves:
- ensuring the confidentiality of information;
- ensuring the integrity of information;
- ensuring the authentication of users and of the resources that users access;
- ensuring the possibility of confirming the actions performed by users with information (non-repudiation).
Data is encrypted in order to control who can read it.
Data is signed so that everyone knows that it came from us.
Data is encrypted with a public key and decrypted with a private key.
After a key pair has been generated, you need to create a certificate and sign it at the CA,
so that other users can trust it.
Article author: Andrei Olegovich
If data is encrypted with a private key, then everyone who has the public key
will be able to read it.
If data is signed with a public key, then only the owner of the private key
will be able to understand that it came from us.
Data is signed with a private key and verified with a public key.
First of all, a certificate signing request is sent
The certificate will include our public key, information about who we are, as well as
some additional information (extensions).
The information about who we are must be written in the format (distinguished name).
The certificate must be signed with our private key.