Reopening, Wouter Hanegraaff from OpenOfficeNL is complaining about it.
Citation: "Yesterday, I tried searching /proc/kcore when a crashed application
didn't save it's data before crashing. Although this has worked many times
before, it didn't right now: all I got was a tiny bit of data, followed
That's what I wrote in the top post:
> only that I lost data which I could have recovered if only I could have
> read /proc/kcore.
It's just like grepping /dev/hda? if you deleted a file in error: I
wrote a text and I couldn't get back to it (it was in a web browser text
field and the browser didn
> What defines the need? I had a need for /proc/kcore yesterday and I
> had the need before.
It might help if you say what you need it for. Ubuntu kernel developers
aren't monsters and will listen to reasonable arguments :)
--
/proc/kcore not openable
https://launchpad.net/bugs/55804
--
ubuntu
> in general, this does not need to be available
What defines the need? I had a need for /proc/kcore yesterday and I had
the need before.
> exposes memory that could contain very sensitive data
Yes it does. But it's only exposed to the root user. And the root user
can do anything to the system.
Yep, the specific reason was that in general, this does not need to be
available, and only exposes memory that could contain very sensitive
data.
Only certain portions of /proc/kcore are readable, and that is just to
allow things like Xorg to work.
** Changed in: linux-source-2.6.15 (Ubuntu)
