Skip to content

output for unwrapping text-mode literal data packets on UNIX systems?

RFC 9580's description of a Literal Data Packet says:

Text data MUST be encoded with UTF-8 (see [RFC3629]) and stored with text endings (that is, network-normal line endings). These should be converted to native line endings by the receiving implementation.

sop decrypt and sop inline-verify both convert OpenPGP Literal Data Packets into a stream of decrypted information.

I don't think the sop spec currently says what should be produced on standard out if the literal data packet is in "text mode" (format = t or u) and the system's "native" line endings are something other than CRLF. Most UNIX systems have a "native" line ending of just LF, for example.

Should the sop spec be more explicit?