On 07/14/2014 12:50 PM, Dave Quigley wrote: > On 7/14/2014 8:58 AM, Stephen Smalley wrote: >> On 07/14/2014 05:25 AM, Dominick Grift wrote: >>> On Mon, 2014-07-14 at 02:49 -0400, Dave Quigley wrote: >>>> I am working on some slides for my workshop at oscon and I tried to >>>> find >>>> the context of a port a process is listening on. If I do netstat -lZ I >>>> see all the listening ports and a security context. However, it seems >>>> the security context is the context of the process that is listening on >>>> that port not the context of the port itself. Is there a way to see the >>>> context of the port itself? I don't see any other option that might >>>> give >>>> that information. Is there a way to get that information from proc? Or >>>> are the only components that know the context of a port the kernel and >>>> the policy store? >>> >>> It is probably not the answer you were looking for but i suppose I would >>> use seinfo --portcon >> >> sepolicy network -p <portnumber> >> >> > > I was hoping there was a way to get it without probing the policy store. > I have this and the seinfo tools already listed. I could be wrong, but I thought sepolicy (and maybe even seinfo these days) are directly reading policy from the kernel via /sys/fs/selinux/policy and not via the policy store. _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
