The issues reported on the sectxt validator have been processed, most were related to adding validation checks on the pgp message. For this I used the PGPy python module, which checks for issues with the pgp message conform the OpenPGP specification per RFC 4880.
The request for the security.txt url has also been given an user agent to mock a regular web browser
The byte content is checked for a utf-8 BOM which is removed if found
53: Canonical "Error: Field value must be a URI (e.g. beginning with 'mailto:')"
Message is simplified to avoid confusion
54: PGP Dash-Escaped Text is still parsed for pgp
A pgp format validator is added to find issues within the message
55: Improve on missing newline in a file by adding line number
The line number is added for the missing newline error. And the error message is improved
56: Singed message is not enforcing signature
A pgp format validator is added
57: Improve parser error for Byte order mark (BOM)
I validated that the issue with the BOM could occur, but it has no meaning in utf-8. If it occurs it is removed and handled validated without it.
The issues reported on the sectxt validator have been processed, most were related to adding validation checks on the pgp message. For this I used the PGPy python module, which checks for issues with the pgp message conform the OpenPGP specification per RFC 4880. The request for the security.txt url has also been given an user agent to mock a regular web browser The byte content is checked for a utf-8 BOM which is removed if found
53: Canonical "Error: Field value must be a URI (e.g. beginning with 'mailto:')"
54: PGP Dash-Escaped Text is still parsed for pgp
55: Improve on missing newline in a file by adding line number
56: Singed message is not enforcing signature
57: Improve parser error for Byte order mark (BOM)
58: If signed, pass data to gpg validate