Add PKCS#8 identifier. (ESPTOOL-584) #819
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
Add extra condition to allow the serialization of PKCS#8 format.
This change fixes the following bug(s):
The documentation suggests to use the following command:
openssl genrsa -out my_secure_boot_signing_key.pem 3072
This generates a PKCS#8 pem file starting with
-----BEGIN PRIVATE KEY-----
which is different to the expected---BEGIN RSA PRIVATE KEY---
.Since
cryptography
uses OpenSSL in the background this change should not be dangerous. I have testedespsecure.py
locally and it works as expected.Before:
After:
I have tested this change with the following hardware & software combinations:
Operating system: Arch Linux x86_64
Kernel: 6.1.1-arch1-1
Chip name: ESP32-S3
IDF version: 4.4.3
OpenSSL version: OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)