Messages in this thread | | | From | "Luis R. Rodriguez" <> | Date | Thu, 21 May 2015 14:59:27 -0700 | Subject | Re: [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures [ver #4] |
| |
On Thu, May 21, 2015 at 2:44 PM, Andy Lutomirski <luto@amacapital.net> wrote: > > One option would be to add another type of verifiable thing. We can > verify modules, and we should add firmware to the types of things that > can be signed. We could add signing keys, too. IOW, you could ask > the kernel to load a signing key with certain rights, and, if they key > is validly signed by some other key that has the same rights and has a > bit set saying that it can delegate those rights, then the kernel will > add that signing key to the keyring. > > If the general infrastructure were there, this would be very little > additional code.
I really like this idea, but I've heard of many great ideas before followed by nothing but vaporware. So is it a direct requirement to implicate blocking a change for current module signature checking strategy to a new one given the concerns you raise, or can we enable those who wish to want additional better solutions as the one you propose to opt-in to develop those solutions? I like the idea of the later given that it seems those using the current module signing infrastructure would prefer the change and enabling what you say does not seem to be a not possible based on allowing that to be advanced.
Luis
| |