Re: Why is the crlNumber an OCTET STRING?

Ernst G Giessmann <[email protected]> writes:

>nevertheless it could happen, that you got two different CRLs, e.g. from two
>different CRL distribution points, both valid (current time inside thisUpdate
>and NextUpdate). How you decide which is the "current"? Comparing the
>corresponding thisUpdate information? And if they are the same due to lousy
>accuracy?

If you have to bend over backwards to manufacture an artificial case where
something is needed then it's probably not actually needed... 

Peter.