Dr S N Henson wrote:
Extensions are also used for security purposes, for example to indicate
whether a certificate is a valid CA certificate and to prevent end user
certificates being able to masquerade as CAs.
I would definitely consider the ability to constrain issued certificates
through
In fact, ASN1 routines have access to X509_EXTENSION structure while
executing parsing routines. But I free that information after it.
We know about security constraints envolving removing X509v3 but code size is
really a important matter for us.
Gleison
Dr S N Henson wrote:
Gleison Santos
Gleison Santos wrote:
In fact, ASN1 routines have access to X509_EXTENSION structure while
executing parsing routines. But I free that information after it.
Can you be more specific about that? Do you free the information after
the ASN1 code has parsed the structure? If so then when the
Hi, all.
In a project I'm working now we don't want to use any X509 extensions,
basically due to binary size limitation. I've commented a lot a source
code, removing any reference to X509_EXTENSION structure.
But during server certificate validation I get a error while validating
the second
Gleison Santos wrote:
Hi, all.
In a project I'm working now we don't want to use any X509 extensions,
basically due to binary size limitation. I've commented a lot a source
code, removing any reference to X509_EXTENSION structure.
But during server certificate validation I get a error
