You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to RFC 7468 PKIX Textual Encodings (Chapter 10/11) the Textual Encoding of Private Key Info use the "PRIVATE KEY" label. Encrypted Private Key Info use the "ENCRYPTED PRIVATE KEY" label.
So the key file can also start/end with the following lines
depending on the application, which creates the key file.
For example, the openssl application with the genpkey command creates PEM files with the aforementioned labels.
Also the openssl req command with the -newkey rsa:2048 option creates this kind of label.
According to the man page, the openssl genrsa command is superseded by genpkey for the generation of RSA Private Keys.
According to RFC 7468 PKIX Textual Encodings (Chapter 10/11) the Textual Encoding of Private Key Info use the "PRIVATE KEY" label. Encrypted Private Key Info use the "ENCRYPTED PRIVATE KEY" label.
So the key file can also start/end with the following lines
or
depending on the application, which creates the key file.
For example, the
openssl
application with thegenpkey
command creates PEM files with the aforementioned labels.Also the
openssl req
command with the-newkey rsa:2048
option creates this kind of label.According to the man page, the
openssl genrsa
command is superseded bygenpkey
for the generation of RSA Private Keys.Therefore, it might be a good idea to replace
by
in the README.rst
pretix-passbook/pretix_passbook/forms.py
Line 18 in 28bd14e
pretix-passbook/README.rst
Line 45 in 28bd14e
The text was updated successfully, but these errors were encountered: