On Thu, Mar 11, 2004, Bommareddy, Satish (Satish) wrote:
> the oid is declared in the config file as
>
> [ new_oid ]
> avayaCPS=10.1.1
>
That is not a valid OID and it certainly doesn't belong to your organization.
Steve.
--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSS
the oid is declared in the config file as
[ new_oid ]
avayaCPS=10.1.1
satish
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dr. Stephen Henson
Sent: Thursday, March 11, 2004 6:38 AM
To: [EMAIL PROTECTED]
Subject: Re: your mail
On Wed, Mar 10, 2004
On Wed, Mar 10, 2004, Bommareddy, Satish (Satish) wrote:
> Here is what i am trying to do...
>
> Config file has these lines:
> [ CA_default ]
> ..
> x509_extensions = usr_cert
>
> [ usr_cert ]
>
> basicConstraints=CA:FALSE
>
> keyUsage = digitalSignature, keyEncipherment
> subjectKeyIdent
Ok, thanks a lot.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Dr. Stephen Henson
> Sent: Thursday, October 23, 2003 10:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: your mail
>
>
> On Thu, Oct 23, 2003, Pierre De Bo
On Thu, Oct 23, 2003, Pierre De Boeck wrote:
> Hi all,
>
> I just try to recompile my openssl applications with
> the 0.9.7c and the PKCS12_decrypt_d2i function no longer
> exist.
>
> I can use my own decrypt/d2i function but I would prefer
> to use what OpenSSL provides as a replacement
On Mon, Oct 14, 2002 at 04:14:17PM +0900, Maya wrote:
> Hello!
>
> I am using smime-tool for creating SMIME messages. I found and option which I can
>use to extract signer's certificate when verifying the message.
> How I can extract encryption Certificates used to encrypt the message?
"PKCS7 E
... just a developer trying to get along ...
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Rich Salz
Sent: Thursday, May 30, 2002 1:38 PM
To: David Smith
Cc: [EMAIL PROTECTED]
Subject: Re: US Export (was RE: your mail)
This is verging off-topi
Lutz Jaenicke wrote:
>There are three things to take care of:
>*Legality of using encryption:
> you can build and use any kind of cryptographic software in the US.
> If you ship sources to the world outside the USA, you have to inform
> the government of this fact (it does not require a permit, y
On Fri, May 24, 2002 at 03:28:44PM -0700, john traenky wrote:
> OpenSSL is the cornerstone for Open Source projects
> using encryption. Has anyone done an analysis of what
> legalities need doing to use it legally in the United
> States? I have several charities and the like who'd
> love to use
I'll make an orthoganal comment. IANAL but it is so sad when ppl become afraid to do
anything because of the percived threats from the lawyers.
I read "Free as in Freedom" today, a biography of Richard Stallman. First I've always
been impressed with Stallman from a number of standpoints. Seco
The first part of David's suggestion is correct: your best bet is to get
your own legal counsel.
If the charities want to deploy it for their own use, e.g., with Apache
so they can take donations over the net :), then disregard the license
exemption. Here, your primary concern is: does my u
On Fri, 24 May 2002 15:28:44 -0700 (PDT), john traenky wrote:
>OpenSSL is the cornerstone for Open Source projects
>using encryption. Has anyone done an analysis of what
>legalities need doing to use it legally in the United
>States? I have several charities and the like who'd
>love to use it b
On Thu, 4 Apr 2002, yves daignaux wrote:
> a fatal error return happens :
>
>
> making all in crypto/sha...
> cc -I.. -I../../include -DTHREADS -pthread -DDSO_DLFCN -DHAVE_DLFCN_H -std1 -tune
>host -fast -readonly_strings -c sha_dgst.c
> Fatal: Insufficient virtual memory to continue compilatio
On Mon, 9 Jul 2001, Tomek Samcik wrote:
> While making openssl I get "Inconsistency between crypto.h and
> cryptlib.c" error message.
I have seen this when symbolic linking fails. You didn't say what
platform you are on or which version of openssl you are trying to
compile. Check to see if c
On Tue, Mar 27, 2001 at 02:16:51PM +0200, [EMAIL PROTECTED] wrote:
> ok since u have answered me so kindly (and so fast) I will ask u several
> more questions hoping u will clarify the fog:
> when I create a request and a private key (using req -keyout ...) I get a
> req and an encrypted private k
remove pass phrase) do I have an un encrypted key
and if so will another rsa command will encrypt it again ?
thanx
Dana Lupu
-Original Message-
From: Lutz Jaenicke [mailto:[EMAIL PROTECTED]]
Sent: þâ 27 îøõ 2001 14:06þ
To: [EMAIL PROTECTED]
Subject: Re: your mail
On Tue, Mar 27
On Tue, Mar 27, 2001 at 01:56:03PM +0200, [EMAIL PROTECTED] wrote:
> while creating a new private key , i give a password, and later i create a
> request and a certificate according to it.
> is there a way for me to change the passowrd without recreating the ca or
> the privatekey?
Provided you k
On Thu, 15 Feb 2001, scintilla wrote:
> hi,i have encoutered a problem when i installed the openssl in SCO_SV ibm5600
>3.2 5.0.5 i386:
>
> make
> making all in crypto...
> ar r ../libcrypto.a cryptlib.o mem.o mem_dbg.o cversion.o ex_data.o tmdi
> ff.o cpt_err.o ebcdic.o
> /us
I was looking for the same thing for a while. Give up. It hasn't been
written. There's a first timers SSL tute building a https client at
http://www.darkspell.com/gadgets/ssl/ It gives some insight into the
philosophy behind it. Then check out the maurice and ssl directories in
the demos dir. Th
On Tue, Mar 28, 2000 at 04:45:56PM +0800, zhangyz wrote:
> When I run "make test",an error was reported, the message is
> "Failed! bc: 1 is unimplemented
The error does not mean that there are problems with OpenSSL. It might
be a bug in "bc" on SCO (which is used in the test only). We've
On Wed, Nov 24, 1999 at 11:56:53AM -, Paul Akehurst wrote:
> Make fails on my system.
> ERROR File = /usr/include/math.h, Line = 731
> Declaration is incompatible with "char *inistate(unsigned int,char *,
> int)"
> (declared at line 207 of "/usr/include/stdlib.h").
Broken system header
Anonymous writes:
> I am using SSLeay 0.6.6b targeting 8086 MS-DOS 5.0. The development platform
> is TurboC running in Linux/DOSEMU.
Amazing.
> I would like to upgrade to the latest
> OpenSSL but I thought that 16-bit support had already been dropped.
16-bit support has not been dropped, but
22 matches
Mail list logo
