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
opensslapplication with thegenpkeycommand creates PEM files with the aforementioned labels. Also theopenssl reqcommand with the-newkey rsa:2048option creates this kind of label. According to the man page, theopenssl genrsacommand is superseded bygenpkeyfor the generation of RSA Private Keys.Therefore, it might be a good idea to replace
by
in the README.rst
https://github.com/pretix/pretix-passbook/blob/28bd14e54e987a78b81af14f6cef51a9e72c800e/pretix_passbook/forms.py#L18
https://github.com/pretix/pretix-passbook/blob/28bd14e54e987a78b81af14f6cef51a9e72c800e/README.rst#L45