Conversation
|
Not sure. But if we can safely assume that ignoring it does no harm and that it really is not touched anywhere else, it could be a solution. Maybe a command line switch or environment variable to enable or disable the behaviour would be even better. |
What other software did you try? |
This feels excessive. The RFC is clear that malformed data should be tollerated and the rest of the PEM data results in a valid chain that can be used like normal.
I know these have some overlap in implementation but: curl, XRootD, davix, gfal2 (except for srm which fails due to gct), DIRAC, openssl |
|
Hi all, That is not going to open the door further for anything: the PEM blob still has to be valid. |
|
Hi @chrisburr all, |
I have a PEM file which contains a section denoted by a custom section. All other software I've tried happily ignores this section however GCT fails with:
RFC 7468, Section 2 doesn't explicitly state that parsers should ignore custom labels in PEM files, it does imply a level of flexibility in handling unrecognized or non-standard data, suggesting that well-designed parsers may indeed ignore custom labels and proceed with processing the rest of the file.
What do you think of removing this check so that unknown labels are ignored?