| To: | linux-os@xxxxxxxxxxxx |
|---|---|
| Subject: | Re: [Coverity] Untrusted user data in kernel |
| From: | Oliver Neukum <oliver@xxxxxxxxxx> |
| Date: | Fri, 17 Dec 2004 17:31:05 +0100 |
| Cc: | Bill Davidsen <davidsen@xxxxxxx>, James Morris <jmorris@xxxxxxxxxx>, Patrick McHardy <kaber@xxxxxxxxx>, Bryan Fulton <bryan@xxxxxxxxxxxx>, netdev@xxxxxxxxxxx, netfilter-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.61.0412171108340.4216@xxxxxxxxxxxxxxxxxx> |
| References: | <41C26DD1.7070006@xxxxxxxxx> <41C2FF99.3020908@xxxxxxx> <Pine.LNX.4.61.0412171108340.4216@xxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.6.2 |
> > Are you saying that processes with capability don't make mistakes? This
> > isn't
> > a bug related to untrusted users doing privileged operations, it's a case
> > of
> > using unchecked user data.
> >
>
> But isn't there always the possibility of "unchecked user data"?
> I can, as root, do `cp /dev/zero /dev/mem` and have the most
> spectacular crask you've evet seen. I can even make my file-
> systems unrecoverable.
Only if you have the capability for raw hardware access.
The same is true for the firmware interface. What other subsystems might
be dangerous?
Regards
Oliver
|
| Previous by Date: | Re: [Coverity] Untrusted user data in kernel, linux-os |
|---|---|
| Next by Date: | Re: primary and secondary ip addresses, Henrik Nordstrom |
| Previous by Thread: | Re: [Coverity] Untrusted user data in kernel, linux-os |
| Next by Thread: | Re: [Coverity] Untrusted user data in kernel, Bill Davidsen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |