From MSIE5, exported Certificate in PKCS#12 (*.pfx) format. Successfully
exported Private Key from the Certificate file using "openssl pkcs12". When
I use the key with "openssl smime" to sign a plain text message, I get the
following error:
**
unable to
I have compiled the s_client application and tested it to a SSL 3.0 server. I am now
trying to move the code into a DLL. Apparently the s_client performs some type of
initialization that I am not doing with the RAND functions. Can anyone tell me what I
have to initialize before calling the
I have compiled the s_client application and tested it to a SSL 3.0
server. I am now trying to move the code into a DLL. Apparently
the s_client performs some type of initialization that I am not
doing with the RAND functions. Can anyone tell me what I have to
initialize before calling
I am unable to decode an authority key identifier extension containing a
directory name choice in a Microsoft-Certificate-Server-generated
certificate using OpenSSL's d2i_AUTHORITY_KEYID when d2i_GENERAL_NAMES is
asked to expect the class universal (i.e., V_ASN1_UNIVERSAL):
Hi,
Any thoughts around implementing Rijndael in OpenSSL? I assume it's something
that's going to get done at some point in time, but have anyone thought about
who will do it, when it will be done, and how soon it'll be considered stable
code?
Just wondering...
Terje Elde
Frank Balluffi wrote:
I am unable to decode an authority key identifier extension containing a
directory name choice in a Microsoft-Certificate-Server-generated
certificate using OpenSSL's d2i_AUTHORITY_KEYID when d2i_GENERAL_NAMES is
asked to expect the class universal (i.e.,
On Tue, Oct 03, 2000, Terje Elde wrote:
Any thoughts around implementing Rijndael in OpenSSL? I assume it's something
that's going to get done at some point in time, but have anyone thought about
who will do it, when it will be done, and how soon it'll be considered stable
code?
Did you
On Tue, Oct 03, 2000, Robert Wilson wrote:
I am very new to openssl and other Open Source stuff. Successfully compiled openssl
using GNU C (Mingw32) on Win2k Prof. When I try to compile /demo/bio, I get about 100
lines of "Undefined Reference" error. First 5 lines are:
Try adding the
* Ulf Moeller ([EMAIL PROTECTED]) [001003 18:01]:
On Tue, Oct 03, 2000, Terje Elde wrote:
Any thoughts around implementing Rijndael in OpenSSL? I assume it's something
that's going to get done at some point in time, but have anyone thought about
who will do it, when it will be done, and
Hi!
Some manual pages about SSL_CTX_load_verify_locations() and friends.
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel.
Steve,
Attached are:
1. cert.pem: sample certificate (PEM format)
2. cert.der: sample certificate (DER encoded)
3. cert.html: dump of cert.der (in HTML)
4. aki.der: AuthorityKeyIdentifier from sample certificate (DER encoded)
5. aki.html: dump of aki.der (in HTML)
Note that 4 and 5 only
Frank Balluffi wrote:
Steve,
Attached are:
1. cert.pem: sample certificate (PEM format)
2. cert.der: sample certificate (DER encoded)
3. cert.html: dump of cert.der (in HTML)
4. aki.der: AuthorityKeyIdentifier from sample certificate (DER encoded)
5. aki.html: dump of aki.der
Steve,
Thanks. It sounds like I need to go back and do the rest of my homework.
Sorry for the trouble.
Frank
-Original Message-
From: Dr S N Henson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 03, 2000 2:21 PM
To: [EMAIL PROTECTED]
Subject: Re: d2i_GENERAL_NAMES
Frank
One can see definitions like this:
{ iso standard 8571 abstract-syntax (2) }
The names aren't flat. To find out the number for "standard", you
ask iso. To find out the number of abstract-syntax, you ask the entity
that maintains "8571" (you might have to ask "standard" who that is).
please help
I am trying to make a third party shared object using OpenSSL and some
software that I have written using OpenSSL. I need to combine my libraries
and OpenSSL libraries into a shared object so I can use an EXPORT file
to conform to US export regulation.
- I have no trouble
I added the switch but no healing. Any other thought?
Robert
- Original Message -
From: "Ulf Moeller" [EMAIL PROTECTED]
To: "Robert Wilson" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 03, 2000 8:00 PM
Subject: Re: Problem Compiling bio
On Tue, Oct 03, 2000, Robert
Richard Levitte - VMS Whacker wrote:
I'm trying to make a simple perl script that is capable of parsing
through an ASN.1 module embedded in any document an extracting the
OIDs from it. When I'm done with that, I'll extend it to be able to
parse LDAP schemas entries as in RFC2256. Then
Terje Elde wrote:
* Ulf Moeller ([EMAIL PROTECTED]) [001003 18:01]:
On Tue, Oct 03, 2000, Terje Elde wrote:
Any thoughts around implementing Rijndael in OpenSSL? I assume it's something
that's going to get done at some point in time, but have anyone thought about
who will do it,
Hello developers:
I am involved in helping spec a hardware accelerator.
My job is to make sure it works from a software POV,
as I am the software developer on the team.
(Actually this hardware is going to be *much* more amazing
than that - but there's an NDA, so unfortunately I cannot
shout it
Richard Levitte - VMS Whacker wrote:
From: Rich Salz [EMAIL PROTECTED]
Subject: Re: Object identifiers and ASN.1 syntax
Date: Tue, 03 Oct 2000 14:43:05 -0400
Message-ID: [EMAIL PROTECTED]
rsalz One can see definitions like this:
rsalz
rsalz { iso standard 8571
Ben Laurie wrote:
What I'm trying to figure out is how I will best get together all the
information from reading a number of ASN.1 modules. I'm wondering for
example how "standard" is defined. Is it something like this?
standard OBJECT IDENTIFIER ::= { iso 0 }
Or is it:
Rich Salz wrote:
One can see definitions like this:
{ iso standard 8571 abstract-syntax (2) }
The names aren't flat. To find out the number for "standard", you
ask iso. To find out the number of abstract-syntax, you ask the entity
that maintains "8571" (you might have to ask
From: Ben Laurie [EMAIL PROTECTED]
ben BTW, if I'm understanding correctly, what you write is:
ben
ben iso.standard OBJECT IDENTIFIER ::= { 0 }
ben
ben or something to that effect...
OK, that starts to make sense. Now to figure out the most efficient
way to parse a OID value...
--
From: Ben Laurie [EMAIL PROTECTED]
ben BTW, are the ways of asking "standard", "iso" and "8571" about
ben each other known? Or is that all part of the game?
If I understand correctly, it's "all part of the game"...
ben Can we write a daemon that does this (I have this vision of one
ben of its
On Tue, Oct 03, 2000, Tom Biggs wrote:
I have so many questions, but this one is most pressing -
Is there a reasonable upper limit on the size in bits of a BN?
For various HW reasons we were hoping we could cap BNs
at 4096 bits for ModExp functions and the like. Is this possible?
Or is
From: Dr S N Henson [EMAIL PROTECTED]
Subject: Re: Object identifiers and ASN.1 syntax
Date: Tue, 03 Oct 2000 21:31:40 +0100
Message-ID: [EMAIL PROTECTED]
drh Richard Levitte - VMS Whacker wrote:
drh
drh
drh I'm trying to make a simple perl script that is capable of parsing
drh through an
Ulf Moeller wrote:
On Tue, Oct 03, 2000, Tom Biggs wrote:
I have so many questions, but this one is most pressing -
Is there a reasonable upper limit on the size in bits of a BN?
For various HW reasons we were hoping we could cap BNs
at 4096 bits for ModExp functions and the like.
At 01:10 PM 9/29/00 -0400, someone wrote:
... The documentation on the Openssl web site only lists the prototypes
for each api call.
I was taught a long time ago that a product without documentation is
worthless.
If we have no documentation, we have nothing !
OK, get writing then!
;-)
Yesterday, I had a quick look at the optimized code (for fst24) at the
official Rijndael site and it states as follows:
"This code is placed in the public domain."
with no other limitations.
Steve wrote:
Is there any ASN1 stuff with this to allow its use in (say) S/MIME?
There's already a
I've appended the PKCS#7 request generated by IIS to the end of this
email. IIS creates the header "BEGIN NEW CERTIFICATE REQUEST", which
is interpreted as an old X509 request (see pem.h).
Changing the header to "BEGIN PKCS7" makes things work. It's not obvious
what the solution should be since
nagendra [EMAIL PROTECTED] writes:
I've appended the PKCS#7 request generated by IIS to the end of this email.
IIS creates the header "BEGIN NEW CERTIFICATE REQUEST", which is interpreted
as an old X509 request (see pem.h).
Ohgodohgod what a mess! That's PKCS #7 signed data containing a data
I've come across four race conditions in the following functions in
rsa_eay.c:
RSA_public_encrypt
RSA_public_decrypt
RSA_eay_mod_exp (x2)
These can cause unexpected failure of the RSA_eay_ encryption/decryption
functions for both public and private key operations. The
BTW, are the ways of asking "standard", "iso" and "8571" about each
other known? Or is that all part of the game?
you have to go to each registrar (arc owner) in turn.
the means of getting name/numbers can be very formal, or wildly
informal.
/r$
33 matches
Mail list logo
