On Sun, May 09, 2004 at 11:49:38AM +0100, Matthew Seaman wrote:
> On Sun, May 09, 2004 at 11:57:05AM +1000, Edwin Groothuis wrote:
>
> > I've been playing with signed emails (S/MIME, OpenSSL etc) but am
> > running into an annoying problem: "openssl smime -sign" signs the
> > text, but it adds ^M'
On Sun, May 09, 2004 at 11:57:05AM +1000, Edwin Groothuis wrote:
> I've been playing with signed emails (S/MIME, OpenSSL etc) but am
> running into an annoying problem: "openssl smime -sign" signs the
> text, but it adds ^M's at the end of the lines of the original text.
> When piping it through t
Giorgos Keramidas said on Sunday, 09 May 2004 03:34 UTC:
> Try base64-encoding the signed message, instead of
> piping it through as text/plain.
That would mean that only S/MIME capable mail clients could read the resulting
email, wouldn't it? When I S/MIME sign an email (such as this one) even
On 2004-05-09 11:57, Edwin Groothuis <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> I've been playing with signed emails (S/MIME, OpenSSL etc) but am
> running into an annoying problem: "openssl smime -sign" signs the
> text, but it adds ^M's at the end of the lines of the original text.
> When piping
Greetings,
I've been playing with signed emails (S/MIME, OpenSSL etc) but am
running into an annoying problem: "openssl smime -sign" signs the
text, but it adds ^M's at the end of the lines of the original text.
When piping it through to the MTA, somewhere the ^M's are lost and
the signature of th
