linux-kernel - Re: [PATCH] Version 7 (2.6.23) Smack: Simplified Mandatory Access Control Kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200710151112.47248.paul.moore@hp.com>
Date:	Mon, 15 Oct 2007 11:12:47 -0400
From:	Paul Moore <paul.moore@...com>
To:	casey@...aufler-ca.com
Cc:	"Ahmed S. Darwish" <darwish.07@...il.com>, torvalds@...l.org,
	akpm@...l.org, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Version 7 (2.6.23) Smack: Simplified Mandatory Access Control Kernel

On Sunday 14 October 2007 11:30:53 pm Casey Schaufler wrote:
> --- "Ahmed S. Darwish" <darwish.07@...il.com> wrote:
> > Hi Casey,
> >
> > On Sun, Oct 14, 2007 at 10:15:42AM -0700, Casey Schaufler wrote:
> > > +
> > > +CIPSO Configuration
> > > +
> > > +It is normally unnecessary to specify the CIPSO configuration. The
> > > default +values used by the system handle all internal cases. Smack
> > > will compose
> >
> > CIPSO
> >
> > > +label values to match the Smack labels being used without
> > > administrative +intervention.
> >
> > I have two issues with CIPSO and Smack:
> >
> > 1-
> >
> > Using default configuration (system startup script + smacfs fstab line),
> > system
> > can't access any service outside the Lan. "ICMP parameter problem
> > message" always
> > appear from the first Wan router (traceroute + tcpdump at [1]).
> >
> > Services inside the LAN can be accessed normally. System can connect to a
> > Lan Windows share. It also connects to the gateway HTTP server easily.
> >
> > After some tweaking, I discovered that using CIPSOv6 solves all above
> > problems:
> > $ echo -n "NLBL_CIPSOv6" > /smack/nltype
> >
> > Is this a normal behaviour ?
>
> Well ... sort of. CIPSOv6 isn't actually implemented in the
> labeled networking code. What you're seeing is unlabeled packets.
>
> As far as CIPSOv4 and your WAN router, It is possible that it is
> configured either to reject CIPSO packets or to allow only CIPSO
> packets in a particular DOI or to enforce a CIPSO policy of its
> own.

The how/why of the packet rejection probably isn't all that important, but the 
most likely scenario based on the ICMP error code is that the router simply 
does not know about the CIPSO IP option type and is dropping the packet as a 
result.  I'd be very surprised to see a standard router in general use which 
has policy to perform packet level access control using CIPSO options/labels.

-- 
paul moore
linux security @ hp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/