Re: [PATCH] Differentiate between Unix Stream Socket and Sequential Packet Socket

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Aug 20, 2016 at 3:09 PM, Guido Trentalancia
<guido@xxxxxxxxxxxxxxxx> wrote:
> Hello Paul!
>
> The message subject used in the Reference Policy mailing list is: "Update the lvm module" and it's one of the most recent posting.
>
> I haven't tried yet reproducing the problem outside of the system bootup.
>
> I believe it happens when cryptsetup uses the user-space interface to the kernel Crypto API.
>
> Do you have any idea on the reason why the class is being marked as "socket" instead of "unix_stream_socket" (for sequential packet socket)?

Thanks for the pointer to the thread; that helped.

As far as the socket class is concerned, I wonder if cryptsetup is
using an AF_ALG socket?  Some quick Googling of the cryptsetup source
repo indicates this may be the case.  We don't currently have a
specific object class for the AF_ALG socket family so it would appear
as the generic socket class.

-- 
paul moore
www.paul-moore.com
_______________________________________________
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.



[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux