On 05/23/2012 11:22 PM, JD wrote:
On 05/23/2012 07:51 PM, Ed Greshko wrote:
The /proc file system is not a real file system. It is a
"pseudo-file system", see
"man proc". AFAIK, it is under the control of the kernel and doesn't
or may not act
as one may expect.
So, the /proc file system all
On 23May2012 19:37, JD wrote:
| So what there are entries there that are root owned,
| and some of them have root only access perms:
| -r 1 root root 0 May 23 11:48 auxv
| --w--- 1 root root 0 May 23 11:48 clear_refs
| -r 1 root root 0 May 23 11:48 environ
| dr-x-- 2 root r
On 05/23/2012 07:51 PM, Ed Greshko wrote:
The /proc file system is not a real file system. It is a "pseudo-file system",
see
"man proc". AFAIK, it is under the control of the kernel and doesn't or may
not act
as one may expect.
I'm not into kernel development. So, the what is and wherefores
On 05/24/2012 10:40 AM, JD wrote:
> Yes Ed, I do see this behavior.
> But I am puzzled as to how such resources were
> somehow accessed by a process that has no root privs?
The /proc file system is not a real file system. It is a "pseudo-file system",
see
"man proc". AFAIK, it is under the con
On 05/23/2012 07:28 PM, Ed Greshko wrote:
On 05/24/2012 10:02 AM, Cameron Simpson wrote:
Sigh. Which is why I asked you to run some ls commands, to _inspect_ the
permissions. What do they show?
I don't know about you, but I'm not sure that things involving the /proc file
system
act in quite th
his is a bug.
|> |
|> | To wit:
|> | COMMAND PID TIDUSER FD TYPE DEVICE SIZE/OFF
|> | NODE NAME
|> | gnome-key 1707jd cwd unknown
|> | /proc/1707/cwd (readlink: Permission denied)
|>
|> What do:
|>
|> ls -ld /proc/1707
|> l
On 05/24/2012 10:02 AM, Cameron Simpson wrote:
> Sigh. Which is why I asked you to run some ls commands, to _inspect_ the
> permissions. What do they show?
I don't know about you, but I'm not sure that things involving the /proc file
system
act in quite the same manner as a real file system.
Tak
ID TIDUSER FD TYPE DEVICE SIZE/OFF
| > | NODE NAME
| > | gnome-key 1707jd cwd unknown
| > | /proc/1707/cwd (readlink: Permission denied)
| >
| > What do:
| >
| >ls -ld /proc/1707
| >ls -la /proc/1707
| >
| > show? Adjust for
jd cwd unknown
| /proc/1707/cwd (readlink: Permission denied)
What do:
ls -ld /proc/1707
ls -la /proc/1707
show? Adjust for your running system, of course.
Maybe /proc itself has exciting new permissions.
Maybe lsof has exciting new setgidness or something.
Or SELinux hates
| /proc/1707/cwd (readlink: Permission denied)
What do:
ls -ld /proc/1707
ls -la /proc/1707
show? Adjust for your running system, of course.
Maybe /proc itself has exciting new permissions.
Maybe lsof has exciting new setgidness or something.
Or SELinux hates you.
BTW
g
> with my uid?
because /proc/ are not normal files?
> This is a bug
not all you do not understand is a bug!
> To wit:
> COMMAND PID TIDUSER FD TYPE DEVICE SIZE/OFF NODE
> NAME
> gnome-key 1707 jd cwd unknown
On 05/23/2012 11:43 AM, Reindl Harald wrote:
Am 23.05.2012 20:38, schrieb JD:
fc16 - with latest updates.
Running lsof, I see a plethora of output like:
systemd 1 root cwd unknown/proc/1/cwd (readlink:
Permission denied)
systemd 1 root rtd unknown
Am 23.05.2012 20:38, schrieb JD:
> fc16 - with latest updates.
>
> Running lsof, I see a plethora of output like:
>
> systemd 1 root cwd unknown /proc/1/cwd (readlink:
> Permission denied)
> systemd 1 root rtd unknown/
fc16 - with latest updates.
Running lsof, I see a plethora of output like:
systemd 1 root cwd unknown/proc/1/cwd (readlink:
Permission denied)
systemd 1 root rtd unknown/proc/1/root (readlink:
Permission denied)
systemd 1 root txt
14 matches
Mail list logo
