key-renewing! obscure?

2008-11-12 Thread Sascha Kiefer
Hello, this is not really an openssl question but a general concern. I'm developing software for an public/private key driven environement (X.509). There are tools to create and manage public/private keys and so on. So, my sponsor asked my for the possibility to renew expired keys. My first th

RE: PKCS12 - Can't read Password

2008-07-21 Thread Sascha Kiefer
as far as i know its 32 characters. hth, sascha kiefer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Renato Araújo Ferreira Sent: Montag, 21. Juli 2008 19:24 To: openssl-users@openssl.org Subject: PKCS12 - Can't read Password Why PKCS12 pas

RE: DES3: Windows CryptoAPI and OpenSSL

2007-10-25 Thread Sascha Kiefer
if you use the unsimplefied version of the cryptoapi you have to reverse the bytes auf your results before using them. > >Hi! > >I am trying to convert my code of 3DES encoding from Windows CryptoAPI to >OpenSSL. Could you verify the code attached and may be point me to >appropriate OpenSSL funct

AW: Hide the client certificate in the application

2006-10-24 Thread Sascha Kiefer
best way to do it: on firsttime client run: - client generates a private key - client sends its public key to your server - server can decide wether or not to sign this key - server stores the public key - server sends signed key back to client - client stores his private key along with the signed

AW: Transfer Encoding : Chunked

2006-10-03 Thread Sascha Kiefer
Well, the best idea is to make it right by really checking how many bytes are missing by implementing a special case when transder encodnd is chunked. You should have a look at the RFC to check how to handle chunked data. HTH, ..sk >Hi All, > >I am implementing an HTTP 1.1 client in C++ using

PFX to PEM

2006-09-06 Thread Sascha Kiefer
Hi, how is PFX to PEM converting done? I know of the command openssl --pkcs12 --in foo.pfx --out foo.pem but what is done internally? Just converting to base64? Thanks for hints. --sk __ OpenSSL Project

RE: extending a PKCS12 certificate

2006-08-04 Thread Sascha Kiefer
] On Behalf Of Sascha Kiefer > Sent: Friday, August 04, 2006 2:11 PM > To: openssl-users@openssl.org > Subject: RE: extending a PKCS12 certificate > > As far as i know, PKCS12 is just a combination of your private key and > the public certificate. So, it should be possible to extr

RE: extending a PKCS12 certificate

2006-08-04 Thread Sascha Kiefer
As far as i know, PKCS12 is just a combination of your private key and the public certificate. So, it should be possible to extract the certificate, make the changes and pack it together with the private key again. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On B

Re: OCSP, Nonce and the requestExtensions

2005-09-08 Thread Sascha Kiefer
ASN.1 Editor (at http://lipingshare.com/Asn1Editor/) does a pretty good job regrarding decoding without knowledge of the format. Regards, Sascha Steven Reddie schrieb: I understand you're point. I can imagine some interesting things done with XSLT. I guess I just haven't come across a case

Re: OCSP, Nonce and the requestExtensions

2005-09-07 Thread Sascha Kiefer
equestList SEQUENCE OF Request, requestExtensions [2] EXPLICIT Extensions OPTIONAL } 2 being the explicit context-specific tag for requestExtensions. Regards, Steven -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sascha Kiefer Sent: Wednesday, 7

Re: OCSP, Nonce and the requestExtensions

2005-09-07 Thread Sascha Kiefer
well, i do not see the CONTEXT SPECIFIC part in the spec!!! Sascha. Dr. Stephen Henson schrieb: On Wed, Sep 07, 2005, Sascha Kiefer wrote: no, that's misunderstanding (well, my english is not that great); here is the complete ocsp request generated by openssl (i'm not sure

Re: OCSP, Nonce and the requestExtensions

2005-09-07 Thread Sascha Kiefer
OCTET STRING : | | | 9DB6697F527D504B82AC93070847A13C Thanks. Sascha Dr. Stephen Henson schrieb: On Wed, Sep 07, 2005, Sascha Kiefer wrote: Hi list, openssl makes - for example: OCSP request with nonce - the requestExtensions a "context specific" integer. Why does it do this? I mean, it w

OCSP, Nonce and the requestExtensions

2005-09-07 Thread Sascha Kiefer
Hi list, openssl makes - for example: OCSP request with nonce - the requestExtensions a "context specific" integer. Why does it do this? I mean, it works, but is it mandatory? Here the openssl output. Offset| Len |LenByte| ==+==+===+===