It is quite bad idea to use assert here. You are analyzing
certificate.
External data which are passed to you by some other party, and you at
this moment cannot be sure that this party is trusted, because you've
not completed validation procedure yet.
I agree completely. This is a code snip
On 2009.10.25 at 19:18:15 -0400, Carl Harris wrote:
> True enough, this reduces the code snippet appreciably by eliminating
> the rather tedious extension lookup fragment. My issue, of course, was
> simply not knowing (and not being able to find any reference that
> documents) the data type
On Oct 25, 2009, at 5:59 PM, Dr. Stephen Henson wrote:
It is rather simpler than that. You can get the decoded structure
for any
certificate extension using X509_get_ext_d2i(). You get additional
checks that
way such as seeing if the extension occurs more than once.
True enough, this redu
On Sun, Oct 25, 2009, Carl Harris wrote:
> On Oct 25, 2009, at 2:57 PM, Carl Harris wrote:
>
>> I'm looking for an example of decoding the crlDistributionPoints
>> extension; e.g. obtaining the specified URI (assuming that the value
>> specifies a URI, that is). This seems like it should be eas
On Oct 25, 2009, at 2:57 PM, Carl Harris wrote:
I'm looking for an example of decoding the crlDistributionPoints
extension; e.g. obtaining the specified URI (assuming that the value
specifies a URI, that is). This seems like it should be easy. By
digging around in the archives of this lis
I've looking for an example of decoding the crlDistributionPoints
extension; e.g. obtaining the specified URI (assuming that the value
specifies a URI, that is). This seems like it should be easy. By
digging around in the archives of this list, I've been able to figure
out I can get the A
