Quick question: does string.h in Unixware define strcasecmp()?
strings.h is non-standard while string.h is standard, as far as I
know. We should change that in any case, unless someone has a
different opinion.
[[EMAIL PROTECTED] - Mon Jul 15 09:33:16 2002]:
This patch seems to have been
Hi all,
There are a number of new protocols in the proposal/early adoption phases that
will probably require the support of a new public library function in
openssl.
These protocols (more below) are used for authenticating roaming access for
802.1x wireless access. They generally use TLS
The OpenSSL S/MIME implementation doesn't follow the MIME
specification when writing out messages in that format. As a result,
messages created with this library will choke when passed through
strictly compliant SMTP libraries.
A patch is below, against today's mid-afternoon CVS tree (EST).
What version of OpenSSL are you talking about? check_pem() appeared
in OpenSSL 0.9.5, and has been entirely unchanged since. It
currently contains the following lines:
/* Allow normal certs to be read as trusted certs */
if(!strcmp(nm,PEM_STRING_X509)
Sorry, you're right, I misread your proposal...
I think Steve can answer a little better about the difference in the
default read and write functions. However, in the mean time,
there's nothing stopping you from using PEM_read
[[EMAIL PROTECTED] - Tue Jul 16 10:05:13 2002]:
Im using
Sorry, you're right, I misread your proposal...
I think Steve can answer a little better about the difference in the
default read and write functions.
In the mean time, did you notice that you mention the implementation
of X509 for reading, but X509_AUX for writing. How about using
Please ignore this one. I pushed the wrong button at the wrong
moment...
[levitte - Tue Jul 16 10:21:19 2002]:
Sorry, you're right, I misread your proposal...
I think Steve can answer a little better about the difference in
the
default read and write functions. However, in the mean
In message [EMAIL PROTECTED] on Tue, 16 Jul 2002 10:53:26
+0200 (MET DST), [EMAIL PROTECTED] said:
levitte Log:
levitte For those wanting to build for several platforms with the same source
levitte directory, making a separate directory tree with lots of symbolic links
levitte seems to
Note that Apple delivers OpenSSL 0.9.6b, so it may be that the
differences are few enough not to trigger much problems, apparently
with RC4 being the great exception. Actually, even this shouldn't
be a problem, if it weren't for some binary incompatibilities
between (I think) 0.9.6c and
In the 0.9.6-stable branch, the Darwin entry has information on how to
build with threading enabled, and has a much simpler set of arguments
than the corresponding enty in 0.9.7-stable and HEAD.
It seems to me like the entry in HEAD comes from previous experiments
and should be simplified
Test complete, 0.9.6e-dev went through without any problems.
I'll see if I can find the delivered libraries again and try to
reinstall them and see what effect that has on it all.
[levitte - Tue Jul 16 12:31:37 2002]:
Note that Apple delivers OpenSSL 0.9.6b, so it may be that the
[EMAIL PROTECTED] schrieb:
levitte 16-Jul-2002 08:51:56
Hello Richard,
Modified:apps Tag: OpenSSL_0_9_7-stable s_client.c s_server.c
Log:
Set up the engine before doing anything random-related, since engine randomness
is only used for seeding and doing it in the wrong
On Tue, 16 Jul 2002, Richard Levitte - VMS Whacker wrote:
In message [EMAIL PROTECTED] on Tue, 16 Jul 2002
10:53:26 +0200 (MET DST), [EMAIL PROTECTED] said:
levitte Log:
levitte For those wanting to build for several platforms with the same source
levitte directory, making a separate
At 7:55 AM -0700 15/7/02, Doug Kaufman wrote:
I don't have a Mac, but I took the liberty of forwarding the trouble
report to Chris Roberts, who compiles and packages openssl for the
OSXGNU project. I am appending the reply. Does adding the linker
option -flatnamespace fix the problem for those
Im using OpenSSL Version 0.9.6.d. The lines which are allready in
check_pem() returns 1 if you are Loading a CERTIFICATE (PEM_STRING_X509)
for TRUSTED CERTIFICATE.
In the normal pem_read funktion the requested type is set to CERTIFICATE
in file pem_all.c
IMPLEMENT_PEM_rw(X509, X509,
We have some proprietary changes to OpenSSL (including a new engine
module) which is required to gain any acceleration with the card. Compiling
stock *OpenSSL* will not help, because the Sun modifications to OpenSSL
are not present in your build, and have not been contributed to the
OpenSSL
Some API mechanism is needed to allow Warning alerts to be sent. This
is most obviously needed to allow the verify callback to send a warning
to the peer. Calling ssl3_send_alert() directly works, but apparently
is frowned upon since it is a private function.
-- Howard Chu
Chief Architect,
On Tue, 16 Jul 2002, Richard Levitte via RT wrote:
Quick question: does string.h in Unixware define strcasecmp()?
It's not defined in string.h but that wouldn't really matter.
strcasecmp() returns an int
I just tested changing to string.h and it works fine.
Hmm loking at the apps/apps.c and
On Tue, 16 Jul 2002, Richard Levitte via RT wrote:
Quick question: does string.h in Unixware define strcasecmp()?
It's not defined in string.h but that wouldn't really matter.
strcasecmp() returns an int
I just tested changing to string.h and it works fine.
Hmm loking at the apps/apps.c
Hi friends,
I am trying to compile bss_log.c in crypto/bio folder and read_pwd.c in
crypto/des folder and it's giving me error syslog.h and sgtty.h not found.
I tried to search those files in openssl-engine-0.9.6d directory but
couldn't find it. Let me know if anybody knows where to include those
[EMAIL PROTECTED] wrote:
Thanks for the tip. Now, how do we get this fix into an official codebase?
I have a patch queued that fixes this.
Cheers,
Ben.
Yuval
-Original Message-
From: Harald Koch [mailto:[EMAIL PROTECTED]]
Sent: Mon, July 15, 2002 17:33
To: [EMAIL PROTECTED]
21 matches
Mail list logo
