lkml.org 
[lkml]   [1998]   [Jul]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] New phys_addr() syscall
Raul Miller <rdm@test.legislate.com> wrote:
> > But the question is: is the physical address information, or is
> > protecting it security through obscurity?

H. Peter Anvin <hpa@transmeta.com> wrote:
> It is information -- you can't obtain this information though any
> other means. "Security through obscurity" implies the information is
> available, just buried.

I meant information as in information vs. noise.

Why is the physical address of memory owned by a process considered
information rather than noise? Why is this information more valuable
than, say, being able to observe various characteristics of the networking
subsystem?

With the current implementation you can make this "information"
unaccessible by leaving /proc unmounted. [If you're concerned about
people having information you'd certainly want to leave /proc unmounted.]

That said, I think that it would be interesting to be able to mount /proc
on enough real storage that you could set the permissions (ownership, ...)
on /proc files (directories, ...).

--
Raul

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.046 / U:0.668 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site