Date: Sun, 9 May 2004 22:10:41 +1000 From: Edwin Groothuis <edwin@mavetju.org> To: Matthew Seaman <m.seaman@infracaninophile.co.uk>, freebsd-questions@freebsd.org Subject: Re: Problem transporting signed emails Message-ID: <20040509121041.GE2165@k7.mavetju> In-Reply-To: <20040509104938.GA106@happy-idiot-talk.infracaninophile.co.uk> References: <20040509015705.GA48222@k7.mavetju> <20040509104938.GA106@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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'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 the file including becomes invalid. > > % openssl smime -sign -binary ... I got it. When feeding it to sendmail, it added an empty line after the content-type line, mostly likely because it was saw the ^M and didn't interpret it as an empty line. Running the output of openssl through "tr -d '\r'" and then feeding into sendmail resulted in a valid signature. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040509121041.GE2165>