> From: owner-openssl-us...@openssl.org On Behalf Of Carlos Saldaña
> Sent: Friday, 09 July, 2010 12:48
> Thanks for answer Dave,
> Actually what I'm trying to do is encode messages using the public
key
> presumably encoded in a .pem file. I checked the contents of this
On Fri July 9 2010, Victor Duchovni wrote:
> On Fri, Jul 09, 2010 at 12:26:46PM -0500, Michael S. Zick wrote:
>
> > On Fri July 9 2010, Suryya Kumar Jana wrote:
> > > Hello,
>
> > Would any one please let me know whether the following ciphers are supported
> > > in 0.9.8m?
> > >
> > > 1. EXP1024
On Fri, Jul 09, 2010 at 12:26:46PM -0500, Michael S. Zick wrote:
> On Fri July 9 2010, Suryya Kumar Jana wrote:
> > Hello,
> Would any one please let me know whether the following ciphers are supported
> > in 0.9.8m?
> >
> > 1. EXP1024-DHE-DSS-DES-CBC-SHA
> > 2. EXP1024-RC4-SHA
> > 3. DHE-DSS-RC
On 7/9/2010 9:05 AM, Steve Marquess wrote:
> Mark Parr wrote:
>> Use of the FIPS OpenSSL is a mandated thing and not just something that we
>> are looking to do for the fun of it. In fact, the base OpenSSL was working
>> fine using the "FIPS AES 256 encryption" in a non "FIPS Certified" mode.
>>
>
On Fri July 9 2010, Suryya Kumar Jana wrote:
> Hello,
> Would any one please let me know whether the following ciphers are supported
> in 0.9.8m?
>
> 1. EXP1024-DHE-DSS-DES-CBC-SHA
> 2. EXP1024-RC4-SHA
> 3. DHE-DSS-RC4-SHA
> 4. EXP1024-DES-CBC-SHA
>
> I just compiled the version and run the utili
Mark Parr wrote:
> Use of the FIPS OpenSSL is a mandated thing and not just something that we
> are looking to do for the fun of it. In fact, the base OpenSSL was working
> fine using the "FIPS AES 256 encryption" in a non "FIPS Certified" mode.
>
> ...
Yes, that was my assumption and the point I
Hello,
Would any one please let me know whether the following ciphers are supported
in 0.9.8m?
1. EXP1024-DHE-DSS-DES-CBC-SHA
2. EXP1024-RC4-SHA
3. DHE-DSS-RC4-SHA
4. EXP1024-DES-CBC-SHA
I just compiled the version and run the utility ./openssl ciphers -v
'EXP1024-DHE-DSS-RC4-SHA' but it is showi
Thanks for answer Dave,
Actually what I'm trying to do is encode messages using
the public key presumably encoded in a .pem file. I checked the contents of
this .pem file and ir has the -BEGIN PUBLIC KEY- and -END PUBLIC
KEY- headers. I fixed my code to take away this headers and t
Dear all,
I found some type misses in openssl-1.0.0a source code.
To take care of usability, I think these should be revised.
Below script is used at my checking.
$ cat grep.sh
cd /tmp
wget
tar xzf openssl-1.0.0a.tar.gz
cd openssl-1.0.0a
find . -name "*.[ch]" -exec grep -rnH appened {} \; | gre
Hi all,
I'm writing a program to check a certificate with OCSP in C++.
I'm doing all in the same way as in ocsp.c from the OpenSSL-App, but I get no
useful return from
OCSP_RESPONSE* pOCSPResponse = NULL;
nRet = OCSP_sendreq_nbio( &pOCSPResponse, pOCSPContext );
nRet is 0 and pO
Use of the FIPS OpenSSL is a mandated thing and not just something that we
are looking to do for the fun of it. In fact, the base OpenSSL was working
fine using the "FIPS AES 256 encryption" in a non "FIPS Certified" mode.
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:o
Hi Team,
I am creating a root CA and 2 sub CA. Each sub CA is issuing certificates to
its user. Now i want to authenticate
user's of 2 sub CAs.
Topology:
CA
/ \
subCA1 subCA2
/ \
user1 user2
Details
On 09-07-2010 03:31, Chuck Pareto wrote:
My group is using RSA with a key thats 2048 in size. We want to encrypt
strings that are longer then this key size gives.
If we switch to a key that is 4096 what is the max string length we can
encrypt? is it double?
You normally don't encrypt data direc
Hi,
Of course the randomly-generated symmetric key is not public! Otherwise,
everyone can decrypt your data.
The only thing that is public is the RSA public key.
For decryption, you only need the RSA private key. It will be used to
decrypt the symmetric key and then with the later you will decrypt
Hi,
I've generated certificates based on the secp256r1 curve and a connection to
the server can be established not only with FireFox, but also Internet
Explorer and Chrome. It must be that secp160r2 is not supported by the
browsers. Do you think it would be possible to add a more descriptive error
Mark Parr wrote:
First, let me say that this is my first attempt to install any version
of the OpenSSL other than what gets distributed w/ the Linux OS and
any updates that are provided via subscription thereafter. It is also
my first attempt at enabling the FIPS option.
On a SUSE 10 SP
16 matches
Mail list logo
