Tag: PKCS#1

Recently, together with B-I-T GmbH Informationen und Prozesse from Hanover, I worked on implementing the electronic data exchange with the statutory health insurance funds and the pension insurance from within an application.

Here, a combination of authenticated data transmission of both signed and encrypted messages is used. PKI technologies are used in all these cases.

Continue reading "Electronic data exchange with the German Pension Insurance"

Sometimes it may be necessary to subsequently change the signature algorithm of an already installed certification authority hierarchy.

This is often the case because one has installed them with PKCS#1 version 2.1 and unfortunately finds out afterwards that not all applications are compatible with the resulting certificates, and thus cannot use the hierarchy.

While it is relatively easy to change the signature algorithm for certificates issued by a certification authority, it is more difficult to do so for certification authority certificates.

Continue reading "Change the signing algorithm of a certification authority hierarchy without issuing new certification authority certificates"

Sometimes it may be necessary to subsequently change the signature algorithm of an already installed certification authority.

Continue reading "Configuring PKCS#1 Version 2.1 for Issued Certificates and CRLs of a Certification Authority"

Before the installation of a standalone root certification authority (standalone root CA), the question arises as to which cryptographic algorithms should be used.

Continue reading "Deploy PKCS#1 version 2.1 for a root CA (own and issued certificates)"

When planning a public key infrastructure, the question arises as to which cryptographic algorithms it should use.

The main principles are explained below.

Continue reading "Basics: key algorithms, signature algorithms and signature hash algorithms"