Hello,
On the Linux platform, OpenSSL generating an S/MIME clearsigned mail
introduces spurious CRs at the end of some lines of the output.
Depending on mail transport conditions, those CRs can break signature
verification in MSOE on MS-Windows.
Example: I want to clearsign some text.
On 10/01/2006 17:19, Tim Rice wrote:
On Sun, 1 Oct 2006, Roger Cornelius wrote:
On 09/30/2006 12:05, Tim Rice wrote:
On Fri, 29 Sep 2006, Roger Cornelius wrote:
Native compiler works here (w/ the HACK mentioned above) but you
I just tried gcc. (don't need no-sha512 w/ gcc)
All
On 10/01/2006 13:42, Brad House wrote:
Also, please check to make sure that gcc is properly installed. Other
platforms seem to have the same type of problem when the system
headers aren't properly fixed up by the installation process.
SCO provides gcc as part of a package of precompiled
I need help... if my
spelling it's wrong, you'll understand, I'm from Argentina.
I'm using SSL to
create certificates and I've created my own CA, by stunneling connections
between the server and the users we want to ensure safety and
credibility.
I used to have a
problem with my
I build OpenSSL 0.9.8d on x86 GNU/Linux with gcc-4.1, and on SPARC
Solaris with Sun Studio 11 cc.
I get the following. On GNU/Linux:
brs% ./openssl aes-128-cbc -in pca-cert.srl -k secret -a
U2FsdGVkX1/4wyyZncUl/+DrVpt/HzuHZcO+reAKB/w=
On Solaris:
edmund% ./openssl aes-128-cbc -in
Bruce Stephens [EMAIL PROTECTED] writes:
[...]
Ah, I see a problem.
The SPARC one fails the AES-128-ECB(encrypt) test:
OK, on another box (with more up to date compiler and OS patches) it
passes, so it's probably a toolchain problem.
[...]
On Mon, 2 Oct 2006, Bruce Stephens wrote:
Bruce Stephens [EMAIL PROTECTED] writes:
[...]
Ah, I see a problem.
The SPARC one fails the AES-128-ECB(encrypt) test:
OK, on another box (with more up to date compiler and OS patches) it
passes, so it's probably a toolchain problem.
The
Bruno Kozlowski via RT wrote:
[SNIP]
The resulting mailfile has mixed EOLs: Most lines end in LF, but
3 lines end in CRLF:
| $ cat -A mailfile | grep \^M
| Content-Type: text/plain^M$
| ^M$
| some text^M$
I think that this is correct - EOL for emails(headers, empty line, body) is
CRLF,
Roumen Petrov wrote:
Bruno Kozlowski via RT wrote:
[SNIP]
The resulting mailfile has mixed EOLs: Most lines end in LF, but
3 lines end in CRLF:
| $ cat -A mailfile | grep \^M
| Content-Type: text/plain^M$
| ^M$
| some text^M$
I think that this is correct - EOL for emails(headers,
