On 15/07/14 15:05, Dr. Stephen Henson wrote:
On Mon, Jul 14, 2014, Martin Basti wrote:
Hi list,
I have RSA encrypted private key as byte sequence, and I need to
export it as ASN.1 type EncryptedPrivateKeyInfo (RFC5958 section 3.)
Currently I use the following code (shortened):
unsigned char
On Mon, Jul 14, 2014, Martin Basti wrote:
> Hi list,
>
> I have RSA encrypted private key as byte sequence, and I need to
> export it as ASN.1 type EncryptedPrivateKeyInfo (RFC5958 section 3.)
>
> Currently I use the following code (shortened):
>
> unsigned char *pk
Hi list,
I have RSA encrypted private key as byte sequence, and I need to export
it as ASN.1 type EncryptedPrivateKeyInfo (RFC5958 section 3.)
Currently I use the following code (shortened):
unsigned char *pkey; //assigned encrypted primary key
priv_key_info = PKCS8_PRIV_KEY_INFO_new();
aobj
Hi list,
I have RSA encrypted private key as byte sequence, and I need to export
it as ASN.1 type EncryptedPrivateKeyInfo (RFC5958 section 3.)
Currently I use the following code (shortened):
unsigned char *pkey; //assigned encrypted primary key
priv_key_info = PKCS8_PRIV_KEY_INFO_new();
aobj
g the underscore.
> -Original Message-
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 27, 2001 5:14 PM
> To: [EMAIL PROTECTED]
> Subject: Illegal characters ASN.1 type
>
>
>
>
> I'm using Java keytool to generate my certific
re illegal for the ASN.1 type."
Is there a way to avoid this ?? Some of the machines I want to sign certs for
have a " _ " in the name . I'm not able to sign certs for these ??
Thanx in advance
Shobhit
Antonio Ruiz Martínez wrote:
>
> Hello!
> I've got the next code like the x_val.c, and but when I introduce
> the sequence in the asn.1 type I get an error.
> What's the problem?
>
If you want to use a SEQUENCE in an ASN1_TYPE structure then you first
need
Hello!
I've got the next code like the x_val.c, and but
when I introduce the sequence in the asn.1 type I get an error.
What's the problem?
Thanks in advance,
Regards,
Antonio.
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include &
Dr Stephen Henson wrote:
> Also speaking personally, I'm not short of things to do :-(
I understand, talk is cheap. Anyway, thank you, you have addressed
my concerns.
Julio
__
OpenSSL Project
Julio Sánchez Fernández wrote:
>
> Now a question to developers. Why the call to ASN1_PRINTABLE_type
> and the subsequent check if in a world with BMPString, UniversalString
> and UTFString (that seems the future according to RFC2459), the
> function ASN1_PRINTABLE_type is essentially a broken c
wjun wrote:
> The Subjects Distinguished Name is as follows
> countryName :PRINTABLE:'CN'
> organizationName :ASN.1 30:'
> The string contains characters that are illegal for the ASN.1 type
Type 30 is a BMP string, that is a string in the Basic Mult
the signature
Signature ok
The Subjects Distinguished Name is as follows
countryName :PRINTABLE:'CN'
organizationName :ASN.1 30:'
The string contains characters that are illegal for the ASN.1 type
Who knows
12 matches
Mail list logo
