Re: procfs + chmod = no go

From: Dag-Erling Smørgrav (des_at_des.no)
Date: 03/01/04

  • Next message: Andy Gilligan: "Re: procfs + chmod = no go" 
    To: "Jimmy Scott" <admin@inet-solutions.be>
Date: Mon, 01 Mar 2004 13:27:33 +0100

    "Jimmy Scott" <admin@inet-solutions.be> writes:
    > Is this possible on FreeBSD 4.9 ? Can't find anything about it in the
    > manual pages. Just want to prevent lusers from running:
    >
    > for file in /proc/*/cmdline; do cat $file; echo; done

    Why? They can get the same information from ps(1) or the kern.proc
    sysctl tree.

    (in 5.2, you can set security.bsd.see_other_uid to 0 to prevent users
    from seeing other users' processes)

    DES 

    -- 
Dag-Erling Smørgrav - des@des.no
_______________________________________________
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
  • Next message: Andy Gilligan: "Re: procfs + chmod = no go"

    Relevant Pages

    • Re: Building custom kernel - make fails in FreeBSD 5.3
      ... Oops, meant to say "99% of users are lusers".. ... darn, guess I am one of them ... To unsubscribe, ...
      (freebsd-questions)
    • Re: procfs + chmod = no go
      ... On Mon, 1 Mar 2004 at 12:27, Dag-Erling Smørgrav wrote: ... > sysctl tree. ... Surely kern.ps_showallprocs would accomplish the same thing in 4.x? ... To unsubscribe, ...
      (FreeBSD-Security)