Vulnerability Development mailing list archives
Re: /dev/urandom | logger "issue"
From: Alfonso De Gregorio <dira () SPEEDCOM IT>
Date: Thu, 24 Aug 2000 00:04:10 +0200
On Wed, 23 Aug 2000, Larry D'Anna wrote:
Is it possible to get the uid of the process at the other end of a unix domain socket? If so then why not have syslogd get the uid and record who logged each message?
Yes, to find the effective uid that called connect() the daemon can call getpeereuid(). However getpeereuid() is not portable. In Linux it can be implemented using getsockopt() and SO_PEERCRED. In NetBSD the LOCAL_CREDS feature does not returns infos until the caller write some data; this lead to DoS attacks. And so on. fhex
Current thread:
- /dev/urandom | logger "issue" Vitaly McLain (Aug 21)
- Re: /dev/urandom | logger "issue" Bluefish (P.Magnusson) (Aug 22)
- Re: /dev/urandom | logger "issue" Eilert Brinkmann (Aug 22)
- Re: /dev/urandom | logger "issue" Michal Zalewski (Aug 22)
- Re: /dev/urandom | logger "issue" Matt Wilson (Aug 22)
- Re: /dev/urandom | logger "issue" Bill Pennington (Aug 22)
- <Possible follow-ups>
- Re: /dev/urandom | logger "issue" Larry D'Anna (Aug 23)
- Re: /dev/urandom | logger "issue" Sarel J. Botha (Aug 23)
- Re: /dev/urandom | logger "issue" Alfonso De Gregorio (Aug 23)
- Re: /dev/urandom | logger "issue" Matt Wilson (Aug 23)
- Re: /dev/urandom | logger "issue" H D Moore (Aug 27)
- Re: /dev/urandom | logger "issue" Sarel J. Botha (Aug 27)
- Re: /dev/urandom | logger "issue" M ixter (Aug 28)
- Re: /dev/urandom | logger "issue" Kev (Aug 28)
