mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Myrddin Ambrosius <imipak@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Drivers, Hardware, and their relationship to Bagels.
Date: Tue, 18 Jun 2002 08:06:28 -0700 (PDT)	[thread overview]
Message-ID: <20020618150628.12694.qmail@web12305.mail.yahoo.com> (raw)
In-Reply-To: <1022276970.4174.153.camel@bip>

[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]

Hi all,

With the discussion on kernel crypto a while back,
there was one very important recurring element that I
would like someone to clarify for me.

The issue is this. My understanding is that -all-
hardware access should be through the kernel, partly
so that similar hardware can have a similar API, but
also so that kernel security code (eg: capabilities)
applies to ALL hardware and ALL lower-level
operations.

However, there were a number of mentions of userland
hardware drivers, which did NOT operate through the
kernel. (This was in reference to why it wouldn't be
necessary to have a kernel-level driver for the
Motorola M190 crypto chip.)

If you can blithely ignore restrictions placed by the
kernel on some piece of hardware, and access it
directly, then surely this would apply to any
hardware. Including disk drives, RAM, etc.

I could be wrong (and I hope, very much, that I am),
but if my understanding is correct, then that's a hole
you could drive a truck through, and have room to
spare.

This isn't intended as a critisism of anyone, or of
any decisions made regarding the way the kernel
operates. (I know my phrasing leaves a lot to be
desired. Sometimes I think my best chance of a long
life would be to take a vow of silence and become a
monk.)

I'd really appreciate it if someone could clarify this
for me, especially the security aspect of non-kernel
drivers.


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[-- Attachment #2: ks.txt --]
[-- Type: text/plain, Size: 489 bytes --]

(Tune of "Running Free", by Iron Maiden)

Kernel bug, core runs wild,
Space/time twists and gets compiled.
Wormholes open and bring to me,
Linux Kernel Version 3!

I'm running 3, yeah, I'm running 3!
I'm running 3, yeah, I'm running 3!

Got support for Tbyte RAM,
The newest arch is leg of lamb.
Max cpus, one thousand now,
Neg latency gives quite a pow.

Men in Black zap my brains,
Melt the hard-disk, and what remains.
There's nothing left for you to see
That my machine was running 3!

  parent reply	other threads:[~2002-06-18 15:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22 18:03 Linux crypto? Myrddin Ambrosius
2002-05-22 18:38 ` Alan Cox
2002-05-23  8:45   ` Trond Myklebust
2002-05-23 21:46   ` Tobias Ringstrom
2002-05-24 14:58     ` Alan Cox
2002-05-24 17:32       ` Thomas 'Dent' Mirlacher
2002-05-24 17:21         ` David S. Miller
2002-05-24 17:42           ` Thomas 'Dent' Mirlacher
2002-05-24 17:31             ` David S. Miller
2002-05-24 17:57               ` Thomas 'Dent' Mirlacher
2002-05-24 19:18                 ` Myrddin Ambrosius
2002-05-25  4:01                   ` Henrique de Moraes Holschuh
2002-05-24 18:41             ` Alan Cox
2002-05-24 18:30               ` Thomas 'Dent' Mirlacher
2002-05-24 18:55                 ` Alan Cox
2002-05-24 18:50                   ` Sandy Harris
2002-05-29  0:24                   ` Petro
2002-05-24 20:17                 ` Myrddin Ambrosius
2002-05-24 21:25                   ` Thomas 'Dent' Mirlacher
2002-05-24 18:45               ` Herman Oosthuysen
2002-05-24 21:49           ` Xavier Bestel
2002-05-24 21:43             ` David S. Miller
2002-05-26 10:06               ` Jakob Østergaard
2002-06-18 15:06             ` Myrddin Ambrosius [this message]
2002-06-18 15:01               ` Drivers, Hardware, and their relationship to Bagels Zwane Mwaikambo
2002-06-18 15:26               ` Richard B. Johnson
2002-06-18 18:35                 ` Myrddin Ambrosius
2002-06-18 19:13                   ` Richard B. Johnson
2002-06-19  2:11                   ` Stevie O
2002-06-18 16:01               ` Xavier Bestel
2002-06-18 18:23                 ` Myrddin Ambrosius

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=20020618150628.12694.qmail@web12305.mail.yahoo.com \
    --to=imipak@yahoo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®