When one creates a message with
(
echo Content-Type: text/plain; name="$file"
echo Content-Transfer-Encoding: base64
echo
echo Hello World | base64
) > msg.txt
cat msg.txt | openssl smime -sign -signer foo.crt -inkey foo.key >
msg.mime
on ‚unix’ - ensuring that msg.txt is entirely \\n or LF terminated - then the
resulting file is *mostly* LF terminated - except for
the msg.txt - it gets CRLF substitutions.
See below - lines that got changed marked with a -CRLF at the end - the rest is
all LF terminated.
Passing the -crlfeol flag does make them all CRLF as one would expect.
So I guess that for consistency - if no -crlfeol flag is passed - openssl
should not really add/subtitute the payload - and keep
those as is (i.e. LF as in above example).
Secondly, from rfc2046 I guess that making the crlfeol flag the default may be
better practice; leaving a -lfeol flag to trigger legacy behaviour.
Or am I missing something crucial ?
Dw
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
micalg="sha1"; boundary="----52B94B8FA281627355210BB13CFD00D1"
This is an S/MIME signed message
------52B94B8FA281627355210BB13CFD00D1
Content-Type: text/plain
-CRLF
Content-Transfer-Encoding: base64
-CRLF
-CRLF
SGVsbG8gV29ybGQK
-CRLF
------52B94B8FA281627355210BB13CFD00D1
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
MIIDVAYJKoZIhvcNAQcCoIIDRTCCA0ECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3
DQEHAaCCAYowggGGMIHwAgEBMA0GCSqGSIb3DQEBBQUAMAwxCjAIBgNVBAMMAUMw
HhcNMTQwNTAyMTAwMDEwWhcNMTQwNjAxMTAwMDEwWjAMMQowCAYDVQQDDAFEMIGf
MA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1Ra+KYVo4X5suo/j9IpHzi1QwIWyo
iAZOQjKGW45lsge0hf/kuI1ow72+eH/+hQNWwU3YljmLCTh7gPPOYRNEXVqiUFKa
QnjaPdDOY3lkj+rx+EiGKjoh1mPiXhKXmCroRRXOqof3lUH5KVE/zjqKYXc5lViH
MgX3PFs0WT3hvwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAEhoR4hQLpSAKAlZ6Sx+
MZmI+cgFZjPUeOqcGvXQkhNM1+T67YAhFQ7coCN9AKTIJ9bzlT5VMmAtDI1ZtUV1
fDQ+FpQgp/4sXRtAq68kwlip9w097OwU9Q/WYGcib23auBIRj+IHRtmDDpodcS8t
zRhGl++JpWUIm61r8Qy6Lo1OMYIBkjCCAY4CAQEwETAMMQowCAYDVQQDDAFDAgEB
MAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMTQwNTAyMTAwMDExWjAjBgkqhkiG9w0BCQQxFgQU1v1LyFzXxZUl
3PNQr2qU4zYmHfsweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZI
AWUDBAEWMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw
DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEgYAP45BHcXB+QJxPVgMFrC1tcotpadUpzsN+Y6hlZtV2x0ZFscV6nhVw
rdntAKsDdHznE1AN2/H4/q2j1ZfEcPKlMrL+EctHrFHfjKr4nwWbfPD4LkoCVLyR
6KtkIsaqwqlEljoBTEtsqib/fvWPJqlhcN4ImXAZXu+BhfmryI6CeQ==
------52B94B8FA281627355210BB13CFD00D1———
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
