It would be advantageous if the processing of these additional fields were supported by the PEMDocument, as otherwise some PEM files cannot be processed properly.
Yeah this is totally an existing limitation. I believe we designed the type such that extending it for this use-case was possible, but the core feature set didn’t require it. We’d welcome a PR to add the function.
The PEM parsing and generation implemented in
PEMDocument
doesn't fully support the PEM format as defined in RFC1421.In particular, fields such as
Proc-Type
andDEK-INFO
are not supported, which means that formats as defined in RFC5915 cannot be processed:It would be advantageous if the processing of these additional fields were supported by the
PEMDocument
, as otherwise some PEM files cannot be processed properly.