linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Automatic download and installation of drivers.
Date: Tue, 16 Oct 2001 05:29:23 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100321083428863@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100319421829170@msgid-missing>

On Tue, Oct 16, 2001 at 01:02:37AM +0100, Stamatis Mitrofanis wrote:
> Automatic download and installation of drivers. That is definately a 
> good thing to have (in general). 

Wow, the security implementations and other complexities involved here
are huge.  Let try a few examples:
	- installing a module requires root permissions.  You generally
	  do not want to run a compiler as root.
	- Running anything as root isn't a good idea, unless the program
	  has been audited for security problems.
	- Who is going to sign/verify the driver you just downloaded
	  to prevent a trojan from being installed?
	- Lots of user machines do not have compilers installed.  What
	  then?
	- Where are you going to find the .config file that the
	  currently running kernel was built against?  Without that, you
	  will not be able to successfully build that module.
	- What is the guarantee that older kernels will be able to load
	  newer modules?  Inter-kernel apis constantly change.  The odds
	  that this would work are quite slim.
	- Distros test their kernels as one package, drivers included.
	  Then they ship with those drivers.  Any new drivers fall under
	  the above problem.

And there are more problems that I can't think of right now.

But the main question I have is:
	What is the real problem that you are trying to solve?
and
	Why does the current kernel/driver situation not work for you?

thanks,

greg k-h

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2001-10-16  5:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16  0:02 Automatic download and installation of drivers Stamatis Mitrofanis
2001-10-16  5:29 ` Greg KH [this message]
2001-10-16  7:35 ` David Brownell
2001-10-16  7:58 ` Tim Jansen
2001-10-16 11:38 ` Keith Owens
2001-10-16 16:52 ` Greg KH
2001-10-16 18:44 ` Tim Jansen
2001-10-16 18:58 ` Tim Jansen
2001-10-16 19:19 ` Greg KH
2001-10-17  2:01 ` David Brownell
2001-10-17  2:03 ` David Brownell
2001-10-17 18:47 ` Tim Jansen
2001-10-17 19:24 ` David Brownell
2001-10-17 23:31 ` Tim Jansen
2001-10-17 23:32 ` Greg KH
2001-10-18  0:07 ` Dmitri
2001-10-18  0:19 ` Stamatis Mitrofanis
2001-10-18  0:47 ` Tim Jansen
2001-10-18  2:17 ` Keith Owens
2001-10-18  2:35 ` Dmitri
2001-10-29 21:53 ` Greg KH
2001-10-30  8:26 ` Tim Jansen
2001-10-30 17:21 ` Greg KH
2001-10-30 21:24 ` Tim Jansen
2001-10-30 21:51 ` Dmitri
2001-10-31 12:36 ` Keith Owens
2001-10-31 20:49 ` Greg KH

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=marc-linux-hotplug-100321083428863@msgid-missing \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).