Hi,
Few questions on OpenSSL.
1. Cipher Selection:
If the Client sends a weaker cipher (export), followed
by a stronger cipher, then openssl selects the first
(weaker) cipher as preferred by the client (as per the
RFC).
Note in the above case, an attacker can influence the
order of client's
On Mon, 7 Jan 2002 13:50:26 + (GMT), Tushar wrote:
1. Cipher Selection: If the Client sends a weaker cipher (export), followed
by a stronger cipher, then openssl selects the first (weaker) cipher as
preferred by the client (as per the RFC).
Note in the above case, an attacker can influence
Hello developers,
I'd like to join the OpenSSL team to work on an official OS/2 version.
Who is responsible for accepting/declining such requests? Is there already someone
working on OS/2 support?
Kind regards,
Jan M. Danielsson
Use subject 'pgpkey' to receive my public PGP key.
PGP
Does OS/2 still exist ?
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Hello developers,
I'd like to join the OpenSSL team to work on an official OS/2 version.
Who is responsible for accepting/declining such requests? Is there already someone
working on OS/2 support?
First you would need to re-port 0.9.7-dev to OS/2. The last time
I did this was for
On Mon, 7 Jan 2002 10:27:03 EST, Jeffrey Altman wrote:
Hello developers,
I'd like to join the OpenSSL team to work on an official OS/2 version.
Who is responsible for accepting/declining such requests? Is there already someone
working on OS/2 support?
First you would need to re-port
Does OS/2 still exist ?
No.
Kind regards,
Jan M. Danielsson
Use subject 'pgpkey' to receive my public PGP key.
PGP Public Key Fingerprint= 43C8 4C46 18C3 2366 7B5B D72D 6818 D0FA CB96 5667
__
OpenSSL Project
ld is trying to link against the lib that Apple ships. Before building
openssl (which will replace Apple's libs), you need to move/rename/unlink
/usr/lib/libcrypto.dylib and /usr/lib/libssl.dylib. Then you *might* be
able to build them.
Now, there's another issue from another email on the list
Ok. I figured out what I did wrong - I didn't follow my own advice: seems
/usr/lib/libssl.dyld and /usr/lib/libcrypt.dyld got reinstalled by one of
the upgrades and I linked against the wrong lib. Re-removing them fixed
it.
So here's what works:
rm /usr/lib/libssl.dyld
Probably because you're not using an ebcdic computer and ebcdic.o has no
symbols. You might be comforted by the line that precedes it:
You may get an error following this line. Please ignore.
- sq
On Thu, 3 Jan 2002, Jay States wrote:
why does /usr/bin/ranlib: file:
A request for some additional hashes I would submit some
patches myself, but this stuff is so simple it would probably
take longer to verify my patches than to code them directly. :-)
The hashes are mentioned in draft-ietf-pkix-certstore-http-00.txt,
available at
Here is a patch for Cygwin32 builds against current 0.9.6-stable snapshots.
The first patch adds two simple shell scripts and changes to the makefile to allow the
objects.pl and obj_dat.pl perl scripts to work correctly in a CR/LF environment.
All diffs were made with diff -Naur format
Hi all,
I use openssl-0.9.6 on a RedHat
Linux 7.0 system as well as LynxOS system, both on i386 machines.
I use the crypt() function
defined in (ssldir)/crypt/des/fcrypt.c
The output of crypt remains same
for passwords with the same first 8 characters.
I would like to know the
On Tue, 08 Jan 2002 02:54:36 +1000 (EST), Brian Havard wrote:
I'd like to join the OpenSSL team to work on an official OS/2 version.
Who is responsible for accepting/declining such requests? Is there already someone
working on OS/2 support?
First you would need to re-port 0.9.7-dev to
On Sun, 6 Jan 2002, Pier Fumagalli wrote:
My hint - or solution :( is to remove the /usr/lib/libcrypto.* and
/usr/lib/libssl.* _BEFORE_ compiling OpenSSL
Removing libssl.* and libcrypt.* is a BAD idea - you'll break some
important stuff that's linked against them. E.g. Mail's Message
Steve Quirk [EMAIL PROTECTED] wrote:
Ok. I figured out what I did wrong - I didn't follow my own advice: seems
/usr/lib/libssl.dyld and /usr/lib/libcrypt.dyld got reinstalled by one of
the upgrades and I linked against the wrong lib. Re-removing them fixed
it.
So here's what works:
rm
Hello,
This isn't a bug report, but i don't want to sign up to mailing list just to
say 1 question.
If i compile OpenSSL, with just ./configure, make, make install, archive
that, then send it to somewhere in the U.S, can the site/ftp in the U.S
legally distribute it internationally? What about
I am trying to compile openssl to VC 6.0 (SP5) on W2000 the test fails
on
cl /Fotmp32dll\ec_mult.obj -Iinc32 -Itmp32dll /MD /W3 /WX /G5 /Ox /O2 /
Ob2 /Gs0 /GF /Gy
/nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN -DL_ENDIA
N -DDSO_WIN32 -DBN_ASM -DMD5_ASM -DSHA1_ASM -DRMD160_ASM
Thus spake Michael Trebilcock:
If i compile OpenSSL, with just ./configure, make, make install, archive
that, then send it to somewhere in the U.S, can the site/ftp in the U.S
legally distribute it internationally? What about other countries?
A yes or no answer would be nice, or an i'm not
Steve Quirk [EMAIL PROTECTED] wrote:
On Sun, 6 Jan 2002, Pier Fumagalli wrote:
My hint - or solution :( is to remove the /usr/lib/libcrypto.* and
/usr/lib/libssl.* _BEFORE_ compiling OpenSSL
Removing libssl.* and libcrypt.* is a BAD idea - you'll break some
important stuff
20 matches
Mail list logo
