{"id":30214,"date":"2019-10-31T21:34:16","date_gmt":"2019-10-31T18:34:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ietf-odobrili-acme-eto-standart-dlya-raboty-s-ssl-sertifikatami\/"},"modified":"2019-10-31T21:34:16","modified_gmt":"2019-10-31T18:34:16","slug":"ietf-odobrili-acme-eto-standart-dlya-raboty-s-ssl-sertifikatami","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/ietf-odobrili-acme-eto-standart-dlya-raboty-s-ssl-sertifikatami","title":{"rendered":"IETF approved ACME \u2014 a standard for working with SSL certificates","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The IETF approved the standard<\/a><\/noindex> Automatic Certificate Management Environment (ACME), which will help automate the obtaining of SSL certificates. Let\u2019s explain how it works.<\/p>\n

\"IETF<\/a><\/noindex><\/a><\/noindex>
\n\/ Flickr \/ Cliff Johnson<\/a><\/noindex> \/ CC BY-SA<\/a><\/noindex><\/i><\/p>\n

Why the standard is needed<\/h2>\n

\nOn average, for configuration an SSL certificate.<\/a><\/noindex> for a domain, an administrator may spend between one to three hours. If a mistake is made, one has to wait for the application to be rejected before it can be submitted again. This complicates the deployment of large-scale systems.<\/p>\n

The domain validation procedure may differ among certification authorities. The lack of standardization often leads to security issues. A well-known case<\/a><\/noindex>, where due to a bug in the system, one CA verified all declared domains. In such situations, SSL certificates can be issued to fraudulent resources.<\/p>\n

The IETF-approved ACME protocol (specification RFC8555<\/a><\/noindex>) is intended to automate and standardize the certificate obtaining process. Eliminating the human factor will help to enhance the reliability and security of domain name verification.<\/p>\n

The standard is open, and anyone interested can contribute to its development. In the GitHub repository<\/a><\/noindex> , relevant instructions are published.<\/p>\n

How it works<\/h2>\n

\nRequest exchanges in ACME occur over HTTPS using JSON messages. To work with the protocol, it is necessary to install an ACME client on the target node, which generates a unique key pair upon the first contact with the CA. Subsequently, these keys will be used to sign all messages between the client and the server.<\/p>\n

The first message contains the contact information of the domain owner. It is signed with the private key and sent to the server along with the public key. The server verifies the authenticity of the signature and, if everything is in order, begins the SSL certificate issuance procedure.<\/p>\n

To obtain a certificate, the client must prove to the server their ownership of the domain. To do this, they perform certain actions available only to the owner. For example, the certification authority may generate a unique token and ask the client to place it on the website. Next, the CA generates an HTTP or DNS request to retrieve the key from this token.<\/p>\n

For example, in the case of HTTP, the key from the token must be placed in a file that will be served by the web server. During DNS verification, the certification authority will look for a unique key in the DNS record text document. If everything is in order, the server confirms that the client has passed validation and the CA issues the certificate.<\/p>\n

\"IETF
\n\/ Flickr \/ Blondinrikard Fr\u00f6berg<\/a><\/noindex> \/ CC BY<\/a><\/noindex><\/i><\/p>\n

Opinions<\/h2>\n

\nAccording to words<\/a><\/noindex> IETF, ACME will be useful for administrators who need to work with multiple domain names. The standard will help link each of them to the appropriate SSL.<\/p>\n

Among the advantages of the standard, experts also note several security mechanisms<\/a><\/noindex>. They must ensure that SSL certificates are issued only to the actual domain owners. In particular, a set of extensions is used to protect against DNS attacks, DNSSEC<\/a><\/noindex>, while to protect against DoS, the standard limits the rate of execution of individual requests\u2014for example, HTTP for the method POST<\/a><\/noindex>. The developers of ACME recommend<\/a><\/noindex> adding entropy to DNS requests and performing them from multiple points in the network for increased security.<\/p>\n

Similar solutions<\/h2>\n

\nProtocols are also used to obtain certificates, SCEP<\/a><\/noindex> and EST<\/a><\/noindex>.<\/p>\n

The first was developed at Cisco Systems. Its goal was to simplify the procedure for issuing X.509 digital certificates and make it as scalable as possible. Before the advent of SCEP, this process required active participation from sysadmins and was poorly scalable. Today, this protocol is one of the most widely used.<\/p>\n

As for EST, it allows PKI clients to obtain certificates over secure channels. It applies TLS for message transmission and SSL issuance, as well as for linking the CSR to the sender. Additionally, EST supports elliptic cryptography methods, providing an extra layer of protection.<\/p>\n

According to According to experts,<\/a><\/noindex>, solutions like ACME should gain broader adoption. They offer a simplified and secure SSL setup model and speed up the process.<\/p>\n

Additional posts from our corporate blog:<\/h5>\n

<\/p>\n