Hello everyone,
I have been writing code to secure my client-server application. It has been
almost a year now, since I entered the world of OpenSSL. I have been reading
about key exchange, symmetric ciphers, certificates etc. and for that matter I
have used all this in the code through the API
On Mon, Jul 23, 2007, nobody wrote:
> On Mon, 23 Jul 2007 15:21:09 +0200
> "Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Jul 23, 2007, nobody wrote:
> >
> > >
> > > That isn't happening. I did create a password-protected private key
> > > and none of the email clients ask for th
You are in a place where theory and practice converge. The security model
assumes you don't trust a CA (in the technical sense) if you don't trust the
CA (in the normal sense). It is built around the assumption that a client's
list of trusted CAs will be intelligentally managed to include only
> Perhaps wandering a bit off-topic, but in practice many CAs which are
> trusted by most browsers will issue certificates to whomever controls
> a domain at the time the cert is issued, and so there's very little
> difference between trusting DNS and trusting DNS+SSL for site
> authentication (th
> The pkcs12 export command seems to want both the certificate and the
> private key to be able to create a certificate containing the private
> key which the key owner can use to verify signatures and decrypt mail
> signed and encrypted using his public key.
Decrypting mail requires the private
So, I was given the mission of creating a small internal pki to
authenticate SSL apaches and maybe some other little stuff. We have an
Active Directory service already working, but not using the Certificate
Services and etcetera.
We choose to use openssl to generate the CA and certificates usi
I am receiving the following error message:
4488:error:060650664:digital envelope routines:EVP_DecryptFinal_ex:bad
decrypt:.\crypto\evp\evp_enc.c:461:
I found some postings referring to a bad passphrase and others referring to
cross-platfom issues, but neither of these seem to be the case here.
On Mon, 23 Jul 2007 15:21:09 +0200
"Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 23, 2007, nobody wrote:
>
> >
> > That isn't happening. I did create a password-protected private key
> > and none of the email clients ask for the password when using it.
> >
>
> Clients typically
On Mon, Jul 23, 2007, nobody wrote:
>
> That isn't happening. I did create a password-protected private key and
> none of the email clients ask for the password when using it.
>
Clients typically ask you for the password when they import the PKCS#12 file.
They use that to decrypt the key and st
On Sun, 22 Jul 2007 17:32:04 +0200
Goetz Babin-Ebell <[EMAIL PROTECTED]> wrote:
> Hello,
>
> --On Juli 22, 2007 14:22:42 + nobody <[EMAIL PROTECTED]> wrote:
>
> > On Fri, 20 Jul 2007 21:38:47 +0200
> > Goetz Babin-Ebell <[EMAIL PROTECTED]> wrote:
> >
> >> --On Freitag, Juli 20, 2007 14:49:54
On Sun, 22 Jul 2007 14:08:31 -0700
"David Schwartz" <[EMAIL PROTECTED]> wrote:
>
> > Hi, I see this option when I import but I don't understand something
> > more fundamental. Why doesn't the cert itself have any password
> > protection? Is it because when I created it I specified the key
> > pas
Hello,
> i meet a problem.when i plant the DES to my voip gateway for the
> purpose of snmpv3 support, it shows decryption error.
> My gateway is running on vxworks and processor is mips32.
> i guess it should be something wrong with architecture concerned
> choice, such as big(little)endian?
>
Hello,
I find some sample for openssl client application which connect to server
via ssl-proxy.
Could i have some information?
Thanks,
ST. Hermawan
13 matches
Mail list logo
