Bug#327813: fuser fails silently when run as non-root

2005-09-13 Thread Robert Millan
On Tue, Sep 13, 2005 at 08:36:32AM +1000, Craig Small wrote:
 [...] The kernel wants those fd subdirectories not publically
 inaccesable for a reason. I don't know what the reason is, but 
 I'm not going against it.

Good point.  Also, it might be unportable if other kernels chose to make them
available.

-- 
Robert Millan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#327813: fuser fails silently when run as non-root

2005-09-12 Thread Robert Millan
Package: psmisc
Version: 21.6-1
Severity: normal

[EMAIL PROTECTED]:~$ fuser 43141/tcp
[EMAIL PROTECTED]:~$ sudo fuser 43141/tcp
43141/tcp:6089
[EMAIL PROTECTED]:~$

It seems it's not capable of detecting open ports whose processes aren't owned
by the same user that runs fuser.  It should print a warning when this happens.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL 
set to C)

Versions of packages psmisc depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libncurses5   5.4-9  Shared libraries for terminal hand

psmisc recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#327813: fuser fails silently when run as non-root

2005-09-12 Thread Craig Small
On Mon, Sep 12, 2005 at 01:04:03PM +0200, Robert Millan wrote:
 It seems it's not capable of detecting open ports whose processes aren't owned
 by the same user that runs fuser.  It should print a warning when this 
 happens.

It's not capable of knowing about any access from any process it cannot
read /proc/pid/fd  It is not tcp or socket specific.

# fuser /var/log/syslog
/var/log/syslog:  4245
# exit
$ fuser /var/log/syslog
$

Now, the problem here is that if it knew a process had access, then it
could print it. But if it cannot know that, it cannot know it missed it.

However a note in the man page would probably help.

-- 
Craig Small  GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.enc.com.au/   MIEE Debian developer
csmall at : enc.com.au  ieee.org   debian.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#327813: fuser fails silently when run as non-root

2005-09-12 Thread Robert Millan
On Mon, Sep 12, 2005 at 09:25:21PM +1000, Craig Small wrote:
 On Mon, Sep 12, 2005 at 01:04:03PM +0200, Robert Millan wrote:
  It seems it's not capable of detecting open ports whose processes aren't 
  owned
  by the same user that runs fuser.  It should print a warning when this 
  happens.
 
 It's not capable of knowing about any access from any process it cannot
 read /proc/pid/fd  It is not tcp or socket specific.
 
 # fuser /var/log/syslog
 /var/log/syslog:  4245
 # exit
 $ fuser /var/log/syslog
 $
 
 Now, the problem here is that if it knew a process had access, then it
 could print it. But if it cannot know that, it cannot know it missed it.
 
 However a note in the man page would probably help.

Perhaps printing a message when running as non-root would help.  Or even
consider making it SUID (are there any security implications in providing
this information to a mallicious user?).

-- 
Robert Millan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#327813: fuser fails silently when run as non-root

2005-09-12 Thread Craig Small
On Mon, Sep 12, 2005 at 05:49:56PM +0200, Robert Millan wrote:
 Perhaps printing a message when running as non-root would help.  Or even
 consider making it SUID (are there any security implications in providing
 this information to a mallicious user?).
I think that would be annoying.  Making it suid by default would also be
a bad idea. The kernel wants those fd subdirectories not publically
inaccesable for a reason. I don't know what the reason is, but 
I'm not going against it.

Users can make it suid themselves.  I've put a warning into the manual 
page which will be available in the next upstream release.

 - Craig
-- 
Craig Small  GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.enc.com.au/   MIEE Debian developer
csmall at : enc.com.au  ieee.org   debian.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]