Hi
I just installed a new ssl cert under apache 2.0.52 on FC3 and openssl
0.9.7e
now with debug on the logging seems a lot less and the last few lines of
failed server read as
[Sat Apr 23 09:06:21 2005] [info] Connection: Client IP: 11.22.33.44,
Protocol: SSLv3, Cipher: RC4-MD5 (128/128 bits)
And where do i set that ?
hi,
BF_set_key is marked as defined in libcrypto.so or libeay32.dll(for windows)
check if this openssl library is in your library path.
sravan
Pól Ó Riain wrote:
Hey, yes it does exist. Is there anything wrong with the code ?
If BF_set_key
And where do i set that ?
hi,
BF_set_key is marked as defined in libcrypto.so or libeay32.dll(for windows)
check if this openssl library is in your library path.
It depends on Operating-System you are using. Please set
PATH (Windows) or LD_LIBRARY_PATH (at least Linux, Solaris)
environment
Here is the ChangeLog entry:
Version 4.10, 2005.04.23, urgency: LOW/EXPERIMENTAL:
* DLLs for OpenSSL 0.9.7g.
* Bugfixes
- Missing locking on Win32 platform was added (thx to Yi Lin
[EMAIL PROTECTED])
- Some problems with closing SSL fixed.
* New features
- New UCONTEXT user-level
Ok well thats not the problem so, its definately in /usr/lib/. I am
having this problem not only on OpenSSL crypto libraries but a very
similiar problem at work with some c crypto libraries we are using. Its
more likely my jni interface thats misbehaving then. (although i did
check it several
Ok well thats not the problem so, its definately in /usr/lib/. I am
having this problem not only on OpenSSL crypto libraries but a very
similiar problem at work with some c crypto libraries we are using. Its
more likely my jni interface thats misbehaving then. (although i did
check it several
Did you run the C or the Java ? I can compile and run the C code myself
too, and if i take out the C code and just put in a printf method it
works but it WON'T encrypt for me :(
Did you run the Java interface ? or just the C ?
On Sun, 2005-04-24 at 00:41 +0900, Takaaki Ishii wrote:
Ok well
Oh wait nevermind i see.
On Sun, 2005-04-24 at 00:41 +0900, Takaaki Ishii wrote:
Ok well thats not the problem so, its definately in /usr/lib/. I am
having this problem not only on OpenSSL crypto libraries but a very
similiar problem at work with some c crypto libraries we are using. Its
more
make
gcc -c -g -c -fPIC -I/usr/include -I/usr/j2sdk1.4.2_08/include
-I/usr/j2sdk1.4.2_
08/include/linux jni.c -o jni.o
gcc -shared -Wl,-soname,libnativebf.so -o libnativebf.so jni.o -g -L/usr/lib -
lcrypto
It tells me -c -g etc are invalid options
On Sun, 2005-04-24 at 00:41 +0900,
I've been trying the options u gave me but gcc keeps giving me errors.
$ gcc -c -g -c -fPIC -I/usr/include -I/usr/j2sdk1.4.2_08/include
-I/usr/j2sdk1.4.2_08/include/linux nativeCrypto.c -o nativeCrypto.o gcc
-shared -Wl,-soname,libnativeCrypto.so -o libnativeCrypto.so
nativeCrypto.o -g
10 matches
Mail list logo