> HI ALL,
> I have a binary format of a public key which is in
> "BASE64-encoded public key in RSA PKCS#1 format".
> How could I convert that to a PEM format?
>
Here is another data set:
TO get the binary format I ran the following command:
openssl asn1parse -inform d -in key.bin
0:d=0
HI ALL,
I have a binary format of a public key which is in "BASE64-encoded
public key in RSA PKCS#1 format".
How could I convert that to a PEM format?
Many thanks in advance,
Bizhan
__
OpenSSL Project
> > Hi All,
> > In our development environment we have an image signing
> system. Through
> > some configuration we can create a pair of rsa
> public/private key by
> > the system.
> >
> > The private key are kept by the system and never are
> release, however,
> > through some HTTPS API
On Tue, Jul 28, 2009, Bizhan Gholikhamseh (bgholikh) wrote:
> Hi All,
> In our development enviroment we have an image signing system. Through
> some configuration we can create a pair of rsa public/private key by the
> system.
>
> The private key are kept by the system and never are release, ho
On Tue, Jul 28, 2009, Randy Turner wrote:
> Is the OCSP response verification algorithm described below implemented
> exclusively by OpenSSL, or is the algorithm an implementation
> of a particular RFC algorithm?
>
It is follows the rules in RFC2560. The CA signing and delegate signing are
taked
Hi All,
In our development enviroment we have an image signing system. Through
some configuration we can create a pair of rsa public/private key by the
system.
The private key are kept by the system and never are release, however,
through some HTTPS API we are able to recieve public key in binary
Is the OCSP response verification algorithm described below
implemented exclusively by OpenSSL, or is the algorithm an
implementation
of a particular RFC algorithm?
Thanks!
Randy
On Jul 28, 2009, at 9:41 AM, Dr. Stephen Henson wrote:
On Tue, Jul 28, 2009, Natanael Mignon - michael-wessel.
Hello Steve,
thanks for the quick and enlightening reply - I was wondering about the ocsp
signer cert being issued by a different CA as unusual, but the idea of global
responders was not familiar. We will check this with the provider/trustcenter.
Mit besten Grüßen
- Natanael Mignon
Blackberry
On Tue, Jul 28, 2009, Natanael Mignon - michael-wessel.de wrote:
> Dear list,
>
> another problem with the OCSP-handling in Apache/mod_ssl:
>
> [Tue Jul 28 14:27:12 2009] [error] SSL Library Error: error:27069070:OCSP
> routines:OCSP_basic_verify:root ca not trusted
> [Tue Jul 28 14:27:12 2009]
Dear list,
another problem with the OCSP-handling in Apache/mod_ssl:
[Tue Jul 28 14:27:12 2009] [error] SSL Library Error: error:27069070:OCSP
routines:OCSP_basic_verify:root ca not trusted
[Tue Jul 28 14:27:12 2009] [error] failed to verify the OCSP response!
Now, of course this could be just
I'm getting almost everything I want but can't figure out how to get
the X509 signature algorithm so I can check for md5 badness. Any help?
Here's my test php:
$result = stream_context_set_option($context, $mode, 'cafile',
$ca_roots);
$result = stream_context_set_option($context, $mode, 've
11 matches
Mail list logo