Re: [RFC][PATCH 00/16] Crypto keys and module signing [ver #2]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


H. Peter Anvin <h.peter.anvin@xxxxxxxxx> wrote:

> Do we really need the complexity of a full OpenPGP parser?  Parsers are
> notorious security problems.

Actually, I don't have a full PGP parser.  I only handle the minimum I need.
It can parse the packet stream, public key packets and signature packets.
That's it.  I cannot guarantee that GPG is always going to put packets in the
stream in the same order, and dealing with the possible variation should be
simple enough.

Note that it might be possible to share the parser with other things like
eCryptFS.

> Furthermore, using DSA in anything but a hard legacy application is not
> something you want to encourage, so why support DSA?

Because DSA is what Red Hat currently uses in its module signing.  So the first
thing to do was to get that working again and then work on getting RSA working.
If I just jumped straight into the RSA parser, I would have a lot more stuff
that might be wrong; doing DSA first at least validated the common stuff.

However, we don't have to include the DSA stuff in the kernel; I can always
discard that patch from the upstream-aimed patchset.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

Add to Google