Re: [Slightly OT] - Socket Security
From: Kevin Collins (spamtotrash_at_toomuchfiction.com)
Date: 05/14/04
- Next message: Ed Morton: "Re: AWK does a proper replace but whipes out other characters"
- Previous message: Kevin Collins: "Re: Simple sed replacement tool"
- In reply to: Barry Margolin: "Re: [Slightly OT] - Socket Security"
- Next in thread: Barry Margolin: "Re: [Slightly OT] - Socket Security"
- Reply: Barry Margolin: "Re: [Slightly OT] - Socket Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 13 May 2004 23:57:45 GMT
In article <barmar-C9D9E3.19424513052004@comcast.dca.giganews.com>, Barry
Margolin wrote:
> In article <slrnca7vjr.9gp.spamtotrash@doom.unix-guy.com>,
> spamtotrash@toomuchfiction.com (Kevin Collins) wrote:
>
>> I know this is not necessarily the best forum for this, but I trust the
>> knowledge of most of the folks here :)
>
> We're better than the folks in comp.unix.questions, comp.unix.admin, and
> comp.unix.internals? I suspect it's mostly the same people, so why do
> you trust us more in this group? And it makes it harder for others who
> might want to search for answers in the future -- they're unlikely to
> search this group for this topic.
Well, because I read and post to THIS group, of course :) so I know the people
here, such as yourself.
And to be honest, it was partly out of laziness. Since I don't peruse those
groups regularly (I probably should), I didn't want to go find a security
forum, lurk for a few weeks reading posts and then pose a question.
>>
>> I am working on a security project identifying, tracking and reporting on
>> world-writable files on all of our systems. I have a fairly sophisticated
>> filtering system which can ignore (for example) files in a directory with the
>> sticky-bit set, temp directories (/tmp, /var/tmp), etc.
>>
>> My trouble comes in where sockets are concerned - do I need to worry about
>> what
>> the security bits are on a socket? What are the issues if a socket is
>> world-writable? I suspect there is some security issue because there are
>> applications that have a special, sticky-bit directory where all sockets are
>> written.
>
> I think most versions of Unix ignore the permissions on Unix domain
> sockets.
See, and now I feel warm and fuzzy, because I have a trust-level of your
knowlegde :)
Anyway, thanks for reading, posting and (mildly) slapping my hand.
Kevin
- Next message: Ed Morton: "Re: AWK does a proper replace but whipes out other characters"
- Previous message: Kevin Collins: "Re: Simple sed replacement tool"
- In reply to: Barry Margolin: "Re: [Slightly OT] - Socket Security"
- Next in thread: Barry Margolin: "Re: [Slightly OT] - Socket Security"
- Reply: Barry Margolin: "Re: [Slightly OT] - Socket Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|