Hello,
I have a CryptoSwift PCI card that I am attempting to use under windows
2000 advanced server with OpenSSL. I am unable to get the drivers for the
card. I contacted rainbow and was redirected to sales. The sales hasn't
returned phone calls in over 2 weeks. Any help or suggestions would be
ap
Title: Message
The
code for using OpenSSL on the Pocket PC should be the same as the code for using
it on other platforms. Try the openssl apps directory for examples of how
to use various OpenSSL features.
Regards,
Steven
-Original Message-From:
[EMAIL PROTECTED] [mailt
On Sat, Sep 27, 2003, Dann Daggett wrote:
> > I still need to keep this short as long emails still a problem.
> > Tried setting MTU to 1450, still hangs on emails over 800 bytes.
> > Last lines in maillog is (DebugLevel 99):
> > Sep 27 22:11:38 ns1 sm-mta[2513]: h8S5BKkL002513: <-- DATA
> > Se
> something) I've realized that there is actually nothing in a
> certificate that tells anyone exactly where to go to get the issuer's
> certificate (i.e. walk the chain).
Right. That's pretty much why all PKI protocols are client-push.
/r$
--
Rich Salz Chief Security Arc
Hi again,
I recompiled openssl, mod_ssl and my Apache again. This time I used
'shared' as flag for OpenSSL 'config'. This was necessary to compile
shared libraries (dylib on Mac OS X).
I tried to access my server again using SSL. The result is the same.
Here is whar ssldump writes:
using open
Ok, thanks.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Dr. Stephen Henson
> Sent: Sunday, September 28, 2003 8:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 3-DES size
>
>
> On Sun, Sep 28, 2003, Pierre De Boeck wrote:
>
> > I would like to know
On Sun, Sep 28, 2003, Pierre De Boeck wrote:
> I would like to know the overhead in size when encrypting
> a message of n bytes with 3DES.
>
> A simple rule of thumb says that it will be n bytes plus
> the padding needed for n to be a multiple of 64 bits (8 bytes).
>
> Is it correct? and how the
> About .0's
>
> The symbolic link names come from
> X509_subject_name_hash()
> {
> X509_NAME_hash(x->cert_info->subject)
> }
>
> The integer in the end is useful if you have multiple
> certificates with same subject name.
>
> /Gaurav
Thank you very muc
> My Issue:
> I have 2 certificates: a self signed server certificate and a
> purchased domain specific certificate. When I connect to the
> domain with https://mydomain.com it works fine, but if I try
> to connect to another port (https://mydomain.com:2020), the
> self signed certificate is th
I would like to know the overhead in size when encrypting
a message of n bytes with 3DES.
A simple rule of thumb says that it will be n bytes plus
the padding needed for n to be a multiple of 64 bits (8 bytes).
Is it correct? and how the different modes (CBC,..)+ initialization
vector influences
My Issue:
I have 2 certificates: a self signed server certificate and a purchased domain
specific certificate. When I connect to the domain with https://mydomain.com it works
fine, but if I try to connect to another port (https://mydomain.com:2020), the self
signed certificate is the one that is
hi,
how can i get a basic openssl client source
code for pocket pc 2002 (openssl 0.9.7b) ?
Thanks in advance
About .0's
The symbolic link names come from
X509_subject_name_hash()
{
X509_NAME_hash(x->cert_info->subject)
}
The integer in the end is useful if you have multiple certificates with same
subject name.
/Gaurav
-Original Message-
From: Da
13 matches
Mail list logo