I wish to try SSL using blowfish as cipher!
What kind of modification I have to introduce in OpenSSL?
There is a simple ad fast way to achive my goal?
Thank you.
Best regards,
Emanuele La Cognata
Software Engineer
Tel. +41 91 611 52 74
The Fantastic Corporation(tm)
First in Broadband
Hi,
I don't get to compile the snapshots (2214 ...2220, the oldest I
didn't try)
using the option alpha-cc. The program ~ /crypto/sha/sha_dsgt.c stop the
compiler sending the
following the message:
Fatal: Insufficient virtual memory to continue compilation.
During the compilation I
Carew I am trying to port L0phtCrack to Linux and found that you already
Carew support most of the encryption schemes needed to support this package.
Carew The one you seem to be missing is MD4. If this is true, I could send
Carew along a diff to fix this. If indeed you do support the MD4 scheme
FYI: in apps:
"passwd.c", line 326: operands have incompatible types:
pointer to const char ":" pointer to uchar
"passwd.c", line 332: operands have incompatible types:
pointer to uchar ":" pointer to const char
./config -t
WARNING! Detected WorkShop C 5.0. Do make sure you
Hi!
I tried to compile the Openssl under a SUSE Linux 6.2 on an Intel
P-100. The make got an error. After I tried to use the no-asm
option, but then the make test failed.
Info:
OpenSSL 0.9.4
make: Error 1
./config -t:
perating system: i586-whatever-linux2
Configuring for linux-elf
Hello, openssl.org
Following line is my bug-report.
Please help me to solution. thanks.
ps. My OS is Red hat 6.1 pre0.9 .
OpenSSL 0.9.4 09 Aug 1999
built on: Mon Oct 18 23:22:17 CST 1999
platform: linux-elf
options:
Running ./config -t results in:
"Operating system: i386 - whatever - Unixware
This system (UnixWare) is not supported. See file INSTALL for details"
Spotting the 'cc works on almost any box' comment, I perhaps naively
executed the command 'perl Configure cc'.
The system produced Makefile.ssl
Hi, there,
I tried to install openssl-0.9.4 on Solaris 7(Sparc)
(./config -t
Operating system: sun4u-sun-solaris2
Configuring for solaris-sparcv9-gcc
/usr/local/bin/perl ./Configure solaris-sparcv9-gcc)
but after "config", when I use "make" command, there
is one error messeage:
make[1]:
Greg, I'm not sure about the state of PKCS#11 support in relation to the
latest snapshot, however I can give you some answers in relation to the
latest release, OpenSSL 0.9.4.
Firstly, I work for a US company and I am unsure about the current state of
the export restrictions, and therefore
We have an application for which we are using SSL enabled clients and
servers(our own server not a web server). I have been trying to get the
session key reuse going for the past several days. It appears that the
session key reuse and timeouts work just fine if I hang on to the SSL
structure on
On Thu, Feb 24, 2000 at 12:42:47PM -0500, Jeffrey Altman wrote:
It seems to me that a function is needed to provide
this number to the application.
CRYPTO_num_locks() is available since version 0.9.4 (see
http://www.openssl.org/docs/crypto/threads.html).
That's great. Perhaps
Hi,
I try to compile (make) OpenSSL for my x86 Solaris platform. Unfortunately
without success: -- make fails
OpenSSL Details
- Version: 0.9.3 (as well as 0.9.4)
Operating System Details
- Output of './config -t':
Operating system: i86pc-sun-solaris2
Configuring for solaris-x86-gcc
We are looking for Unix, PC and Mac PKI and encryption programming experts
to join us in a new internet startup that will be delivering feature
length videos over the Internet. Positions are located in New York City.
You'll get a competitive salary and generous equity and stock option
package.
Dr Stephen Henson wrote:
#define DECLARE_STACK_OF(type) \
#define IMPLEMENT_STACK_OF(type) \
There's a problem with this solution. If you need another ASN1_STRING
equivalent STACK_OF such as ASN1_IA5STRING you get a conflict because
the structure STACK_ASN1_STRING gets declared twice.
Dr Stephen Henson wrote:
Jean-Marc Desperrier wrote:
There's a problem with this solution. If you need another ASN1_STRING
equivalent STACK_OF such as ASN1_IA5STRING you get a conflict because
the structure STACK_ASN1_STRING gets declared twice.
If IA5STRING used a typedef instead of a
On Wed, Feb 23, 2000 at 01:00:27PM -0800, Yoram Meroz wrote:
So what's the matter with www.apache-ssl.org
("openssl s_client -debug -state -connect www.apache-ssl.org:443")?
The error is returned by ssl3_read_bytes (s3_pkt.c, line 912). The comment
says, "In the case where we try to read
Ben Laurie wrote:
Dr Stephen Henson wrote:
Jean-Marc Desperrier wrote:
There's a problem with this solution. If you need another ASN1_STRING
equivalent STACK_OF such as ASN1_IA5STRING you get a conflict because
the structure STACK_ASN1_STRING gets declared twice.
If IA5STRING used
Hi,
based on information posted by "anonymous" (hopefully with new regulations
we don't need this anymore in the future), I do build and run shared
libraries on HP-UX 10.20.
To get the best possible optimization I use a "+O4" target, that could be
included into the normal Configure file:
[FILE]
root/crypto/bio/b_sock.c, line 283ff
j=strlen(a-h_name)+1;
if ((ret-h_name=Malloc(j)) == NULL) goto err;
memcpy((char *)ret-h_name, a-h_name , j+1);
[BUG]
memory overrun (one byte at the end of ret-h_name)
allocating "j" bytes but memcpy "j+1" bytes next line
Serious problem. Program
Hi, everybody ...
I am using openssl in an environment which suggests to keep the private
rsa key not on the host on which the application is running which uses
openssl. In this aspect my situation is much like using a smart card.
I tried the following:
On the host I keep the real certificate
ralf [BUG]
ralf memory overrun (one byte at the end of ret-h_name)
ralf allocating "j" bytes but memcpy "j+1" bytes next line
ralf Serious problem. Program can crash.
Those bugs were fixed in cvs revision 1.16 of b_sock.c, timestamp
1999/08/11 13:31:03. From what I can see, that was right after
Does any one know if any of the proposed cipher TSL suites will be added
to openssl?
I would really like to see a RSA+Blowfish+SHA1 cipher added with 256-448
bit blowfish session keys. In fact I would be happy to have any decent
TLS session symmetric cipher with 256 bit or higher key size.
My
Bodo Moeller wrote:
Chris Bamford [EMAIL PROTECTED]:
Do you provide mutexes to the library? For multi-threaded applications,
the following calls are required in initialization:
CRYPTO_set_id_callback(id_callback);
CRYPTO_set_locking_callback(locking_callback);
[FILE]
root/crypto/bio/b_sock.c, line 288ff
j=strlen(a-h_name)+1;
if ((ret-h_name=Malloc(j)) == NULL) goto
err;
memcpy((char *)ret-h_name, a-h_name ,
j+1);
[BUG]
memory overrun (one byte at the end of
ret-h_name)
allocating "j" bytes but memcpy "j+1" bytes
next line
[FIX]
dont add one byte,
Dear sir,
I had problems when making openssl-0.9.4. My system suddenly crashes!
As you asked I have attached to output of 'config -t'. The openssl version
I was tring to use was 'OpenSSL-0.9.4'.
I am runnig a 'Red Hat Linux release 6.0 (Hedwig)' and my kernel is
2.2.5-15.
What shall I
Sorry, [BUG] [rk1] has line number 283ff
There are two identical bugs ;-)
next bug [BUG] [rk2] is in line 288ff
[FILE]
root/crypto/bio/b_sock.c, line 288ff
j=strlen(a-h_aliases[i])+1;
if ((ret-h_aliases[i]=Malloc(j)) == NULL)
goto err;
memcpy(ret-h_aliases[i],a-h_aliases[i] ,
j+1);
Do you provide mutexes to the library? For multi-threaded applications,
the following calls are required in initialization:
CRYPTO_set_id_callback(id_callback);
CRYPTO_set_locking_callback(locking_callback);
I have a question that seem obvious to me but is not
On Sun, 20 Feb 2000, Eugene Levy wrote:
Yes I know that even a 1024 bit RSA key and 128 bit symmetric cipher has
no chance of being broken within the next 20 years. (Gee, if a 1024 bit
RSA key could be broken, a lot of us would be issuing our own Versign/
Thawte certificates with their
Openssl,
I am trying to port L0phtCrack to Linux and found that you already
support most of the encryption schemes needed to support this package.
The one you seem to be missing is MD4. If this is true, I could send
along a diff to fix this. If indeed you do support the MD4 scheme under
a
On Wed, Feb 23, 2000 at 08:32:05PM -0800, Will wrote:
I've looked through the documentation, but I can't seem to
find how to build an exportable (40 bit) version of OpenSSL?
You can't, but the new regulations don't have that limit anyway.
How can I add a new cipher suite?
I wish to test blowfish as SSL cipher: SSL_DH_WITH_BLOWFISH_CBC_SHA
Best regards,
Emanuele La Cognata
Software Engineer
Tel. +41 91 611 52 74
The Fantastic Corporation(tm)
First in Broadband Multimedia
Via Cantonale
CH-6928 Manno, Switzerland
Tel. +41 91 611
On Thu, Feb 24, 2000 at 12:42:47PM -0500, Jeffrey Altman wrote:
It seems to me that a function is needed to provide
this number to the application.
CRYPTO_num_locks() is available since version 0.9.4 (see
http://www.openssl.org/docs/crypto/threads.html).
Hi All,
Can anyone suggest me for the following error urgently.
I am using the stunnel source using threads for servicing the clients.
Some time for more than one client it does the correct data transfer.
But at some times when first thread closes, and the second thread is on the
verge of
33 matches
Mail list logo
