I'm using OpenSSL 0.9.2
I use PEM_read_PrivateKey() / PEM_write_PrivateKey() to read/write my
private key from/to a diskette. I would like encrypt/decrypt the key when
writing/reading to/from the diskette.
I'm only looking for a "simple" encryption with a key hardcoded in to my
application.
On Mon, Jul 12, 1999 at 10:16:50PM -0400, Timothy Canfield wrote:
I'm trying to find out the proper thing to do, when either SSL_read or
SSL_write return SSL_ERROR_WANT_READ.
See the archives of this mailing list of about a week ago,
thread "SSL_ERROR_*".
Mickey Baker wrote:
Folks,
Am I the only one getting double messages or has someone already complained?
The headers for the first of a given double look similar to the following:
Return-Path: [EMAIL PROTECTED]
Received: from opensource-01.ee.ethz.ch by hq.ljl.COM. with
Dr Stephen Henson wrote:
Historically OpenSSL has used the MASM ("ml") assembler for Win32 which
is rather expensive and tricky to obtain: I don't have it for example.
The easiest way to get it, should anyone care, is to get the DDK for
Win32 (any flavour).
Cheers,
Ben.
--
As I mentioned earlier, MASM is available in the DDK. What I hadn't
realised, but have been told by a kind informant, is that the DDK is
free.
http://www.microsoft.com/ddk/ddk40.htm
So, MASM really should not be a problem.
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html
"My grandfather
I need to implement a poor man's SSL client which ignores the server
certificate. I want to get rid of everythimg x509-related in the
sources. Can someone please give me some directions as to where do I
apply the scalpel first?
Thanx,
begin:vcard
n:Castro;Juan
tel;work:540-9100 Ramal 46
Ben Laurie wrote:
As I mentioned earlier, MASM is available in the DDK. What I hadn't
realised, but have been told by a kind informant, is that the DDK is
free.
http://www.microsoft.com/ddk/ddk40.htm
So, MASM really should not be a problem.
Erk. Thats weird. I've read a page
Peter Gutmann wrote:
Dr Stephen Henson [EMAIL PROTECTED] writes:
Historically OpenSSL has used the MASM ("ml") assembler for Win32 which
is rather expensive and tricky to obtain: I don't have it for example.
Actually you already have it, and it's free (well, free if you have the Win95
Peter Gutmann schrieb:
Dr Stephen Henson [EMAIL PROTECTED] writes:
Historically OpenSSL has used the MASM ("ml") assembler for Win32 which
is rather expensive and tricky to obtain: I don't have it for example.
Actually you already have it, and it's free (well, free if you have the Win95
make error:
gcc -DMONOLITH -I../include -DTHREADS -D_REENTRANT -DRSAref -DL_ENDIAN
-DTERMIO -O3 -fomit-frame-pointer -m486 -Wall -DSHA1_ASM -DMD5_ASM
-DRMD160_ASM -c openssl.c -o openssl.o
rm -f openssl
gcc -o openssl -DMONOLITH -I../include -DTHREADS -D_REENTRANT -DRSAref
-DL_ENDIAN
Dear Technical Experts,
I would like to install the OpenSSL to our Apache Server.
However, when I tried to build the OpenSSL by "make", I
faced the follow problem :
-
gcc -I ..
cryptlib.c:0: unterminated string or character constant
cryptlib.c:0: possible real
I have just compiled opensll on HP-UX 10.20.
$ openssl version -a
OpenSSL 0.9.3a 29 May 1999
built on: Mon Jul 12 12:39:20 BST 1999
platform: hpux10-cc
options: bn(64,32) md2(int) rc4(ptr,int) des(ptr,risc1,16,long)
blowfish(idx)
compiler: cc -DTHREADS -D_REENTRANT -DNO_IDEA +Z
PEM_read_bio_PrivateKey(BIO *KeyFile ,NULL,yourcallback)
where yourcallback is :
static int MS_CALLBACK yourcallback(char *buf, int num, int verify)
{
strncpy(buf,yourhardcodedpassword,num-1);
return(strlen(buf));
}
;
I'm using OpenSSL 0.9.2
I use
This was copied by hand. The same source compiled fine on a custom i486
kernel running the same linux release. Only difference is this servers
kernel
was compiled as i586 SMP, and the i486 server is running perl5.00503. Is
the SMP kernel compatible with openssl?
Thanks,
Steve Kinkaid
making
14 matches
Mail list logo
