On 11/22/06, Victor Duchovni <[EMAIL PROTECTED]> wrote:
On Wed, Nov 22, 2006 at 09:31:35PM -0500, Chris Covington wrote:
> I am most likely using the wrong terms (but I may be completely
> confused, I admit). When one distributes client certificates to take
> the place of usernames/passwords fo
On 11/22/06, Chris Covington <[EMAIL PROTECTED]> wrote:
On 11/22/06, Chris Covington <[EMAIL PROTECTED]> wrote:
> On 11/22/06, David Schwartz <[EMAIL PROTECTED]> wrote:
> > > OK, perhaps I need to explain this more. I have a client cert
> > > scenario where in order to verify the client's identi
On Wed, Nov 22, 2006 at 09:31:35PM -0500, Chris Covington wrote:
> I am most likely using the wrong terms (but I may be completely
> confused, I admit). When one distributes client certificates to take
> the place of usernames/passwords for authentication, how is that commonly
> referred to?
One
On 11/22/06, Chris Covington <[EMAIL PROTECTED]> wrote:
On 11/22/06, David Schwartz <[EMAIL PROTECTED]> wrote:
> > OK, perhaps I need to explain this more. I have a client cert
> > scenario where in order to verify the client's identity a certificate
> > is used instead of a username / password.
On 11/22/06, David Schwartz <[EMAIL PROTECTED]> wrote:
> OK, perhaps I need to explain this more. I have a client cert
> scenario where in order to verify the client's identity a certificate
> is used instead of a username / password. I would not like for anyone
> to be able to just grab the cl
> OK, perhaps I need to explain this more. I have a client cert
> scenario where in order to verify the client's identity a certificate
> is used instead of a username / password. I would not like for anyone
> to be able to just grab the client certificate and impersonate, so I
> would like to a
Hello,
> OK, perhaps I need to explain this more. I have a client cert
> scenario where in order to verify the client's identity a certificate
> is used instead of a username / password. I would not like for anyone
> to be able to just grab the client certificate and impersonate, so I
> would lik
On 11/22/06, Marek Marcola <[EMAIL PROTECTED]> wrote:
Hello,
> openssl.exe rsa -des -in certnew.cer -out passcert.cer
>
> unable to load Private Key
> 3752:error:0906D06C:PEM routines:PEM_read_bio:no start
> line:.\crypto\pem\pem_lib.c:644:Expecting: ANY PRIVATE KEY
Are you trying to encrypt X509
Hello,
> openssl.exe rsa -des -in certnew.cer -out passcert.cer
>
> unable to load Private Key
> 3752:error:0906D06C:PEM routines:PEM_read_bio:no start
> line:.\crypto\pem\pem_lib.c:644:Expecting: ANY PRIVATE KEY
Are you trying to encrypt X509 certificate ?
Why ?
Certificate are public, RSA keys a
Hello,
> hmm, tried that:
>
> openssl.exe rsa -des -in certnew.cer -out passcert.cer
>
> unable to load Private Key
> 3752:error:0906D06C:PEM routines:PEM_read_bio:no start
> line:.\crypto\pem\pem_lib.c:644:Expecting: ANY PRIVATE KEY
Probably your RSA key has DER format (not PEM), add option
"-in
On 11/22/06, Marek Marcola <[EMAIL PROTECTED]> wrote:
Hello,
> How can I simply take an existing unencrypted client certificate and
> add a password to it? In other words, do the opposite of:
>
> openssl rsa -in pass.pem -out nopass.pem
openssl rsa -des -in nopass.pem -out pass.pem
hmm, tried
Hello,
> How can I simply take an existing unencrypted client certificate and
> add a password to it? In other words, do the opposite of:
>
> openssl rsa -in pass.pem -out nopass.pem
openssl rsa -des -in nopass.pem -out pass.pem
Best regards,
--
Marek Marcola <[EMAIL PROTECTED]>
__
Hi all,
How can I simply take an existing unencrypted client certificate and
add a password to it? In other words, do the opposite of:
openssl rsa -in pass.pem -out nopass.pem
thanks
Chris
__
OpenSSL Project
13 matches
Mail list logo
