I was hoping that either via kernel capabilities or SE Linux that
we
could avoid this. Both seem to offer exactly the feature we want,
opening raw sockets from unprivileged accounts. But it's really
unclear from all the doc's online how these two interact. Best we
could do was try all the
On Fri, 2008-03-07 at 16:48 -0500, S Roderick wrote:
I was hoping that either via kernel capabilities or SE Linux that we
could avoid this. Both seem to offer exactly the feature we want,
opening raw sockets from unprivileged accounts. But it's really
unclear from all the doc's online
I was hoping that either via kernel capabilities or SE Linux that we
could avoid this. Both seem to offer exactly the feature we want,
opening raw sockets from unprivileged accounts. But it's really
unclear from all the doc's online how these two interact. Best we
could do was try all the
On Sat, Mar 08, 2008 at 08:44:10AM -0500, S Roderick enlightened us:
I was hoping that either via kernel capabilities or SE Linux that we
could avoid this. Both seem to offer exactly the feature we want,
opening raw sockets from unprivileged accounts. But it's really
unclear from all the doc's
PROTECTED] On Behalf Of S Roderick
Sent: Friday, March 07, 2008 4:40 PM
To: CentOS mailing list
Subject: Re: [CentOS] Unable open raw socket in CentOS 5 - SE
Linux andkernelcapability interaction?
It runs fine under root and with sudo.
S
On Mar 7, 2008, at 15:33 , Ross S. W. Walker wrote
: Friday, March 07, 2008 4:40 PM
To: CentOS mailing list
Subject: Re: [CentOS] Unable open raw socket in CentOS 5 - SE
Linux andkernelcapability interaction?
It runs fine under root and with sudo.
S
On Mar 7, 2008, at 15:33 , Ross S. W. Walker wrote:
Does it run as 'root'?
-Ross
6 matches
Mail list logo
