--
Peter Gutmann wrote:
> > How does [GPG] handle the NULL vs.optional
> > parameters ambiguity?

David Shaw:
> GPG generates a new structure for each comparison, so
> just doesn't include any extra parameters on it.  Any
> optional parameters on a signature would cause that
> signature to fail validation.
>
> RFC-2440 actually gives the exact bytes to use for the
> ASN.1 stuff, which nicely cuts down on ambiguity.

This amounts to *not* using ASN.1 - treating the ASN.1
data as mere arbitrary padding bits, devoid of
information content.

    --digsig
         James A. Donald
     6YeGpsZR+nOTh/cGwvITnSR3TdzclVpR0+pr3YYQdkG
     KBZXRF1divvJGZ6Zm3lHv3qjnS9Bwhl22NfSlYK3
     4zPRSIE0Q6qUaTtmKPPoKOsPNzAtcdWuthGi5nNTi

---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to [EMAIL PROTECTED]

Reply via email to