From: Greg KH <greg@kroah.com>
To: Valdis.Kletnieks@vt.edu
Cc: Jiri Kosina <jkosina@suse.cz>, Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: virtualbox tainting.
Date: Fri, 7 Oct 2011 10:01:23 -0700 [thread overview]
Message-ID: <20111007170123.GA2121@kroah.com> (raw)
In-Reply-To: <14168.1318003445@turing-police.cc.vt.edu>
On Fri, Oct 07, 2011 at 12:04:05PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 07 Oct 2011 10:01:32 +0200, Jiri Kosina said:
> > On Thu, 6 Oct 2011, Dave Jones wrote:
>
> > > what stops an out of tree module from setting that flag ?
> >
> > What stops virtualbox developers from renaming the module in every
> > release? That's the same story.
> >
> > The only fool-proof way of doing is indeed is the GPG-signing thing.
>
> It would also be a second in-tree user for the kernel MPI library code that
> somebody posted recently... Just sayin' ;)
Ah, that is a good idea as some systems do want to gpg sign kernel
modules, I would love it if someone dug up the Red Hat patches, ported
it to the in-kernel mpi library (which I think will be in 3.2) and got
it merged.
Actually, anyone have any pointers to the Red Hat patch, I might
consider doing this myself as I wrote the first gpg signed kernel code
years ago and I would like to see this finally merged.
greg k-h
next prev parent reply other threads:[~2011-10-07 17:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 19:05 RFC: virtualbox tainting Dave Jones
2011-10-06 19:44 ` Greg KH
2011-10-06 19:50 ` Dave Jones
2011-10-06 19:53 ` Valdis.Kletnieks
2011-10-06 20:03 ` Dave Jones
2011-10-06 20:06 ` Greg KH
2011-10-06 19:58 ` Greg KH
2011-10-06 20:04 ` Dave Jones
2011-10-06 20:30 ` Greg KH
2011-10-07 8:01 ` Jiri Kosina
2011-10-07 10:02 ` Alan Cox
2011-10-07 16:04 ` Valdis.Kletnieks
2011-10-07 17:01 ` Greg KH [this message]
2011-10-07 17:46 ` Dave Jones
2011-10-07 7:03 ` Bastian Blank
2011-10-07 14:40 ` Frank Mehnert
2011-10-07 15:10 ` Dave Jones
2011-10-09 20:12 ` Frank Mehnert
2011-10-07 15:16 ` Josh Boyer
2011-10-07 16:22 ` Valdis.Kletnieks
2011-10-07 18:10 ` Josh Boyer
2011-10-07 18:33 ` Valdis.Kletnieks
2011-10-10 7:58 ` Pekka Enberg
2011-10-10 8:25 ` Dave Airlie
2011-10-10 14:24 ` Greg KH
2011-10-10 16:35 ` Pekka Enberg
2011-10-10 16:49 ` Dave Airlie
2011-10-10 16:51 ` Pekka Enberg
2011-10-10 8:41 ` Maarten Lankhorst
2011-10-10 11:42 ` Josh Boyer
2011-10-12 0:57 ` Parag Warudkar
2011-10-12 7:55 ` Alex Riesen
2011-10-12 14:08 ` Parag Warudkar
2011-10-12 14:18 ` Alex Riesen
2011-10-12 15:00 ` Parag Warudkar
2011-10-12 19:55 ` Zan Lynx
2011-10-12 20:54 ` Parag Warudkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111007170123.GA2121@kroah.com \
--to=greg@kroah.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davej@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.