linux-kernel - Re: [AppArmor 01/41] Pass struct vfsmount to the inode

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 1 Jun 2007 11:00:50 -0700 (PDT)
From:	david@...g.hm
To:	Valdis.Kletnieks@...edu
cc:	Pavel Machek <pavel@....cz>,
	David Wagner <daw-usenet@...erner.cs.berkeley.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM
 hook

On Fri, 1 Jun 2007, Valdis.Kletnieks@...edu wrote:

> On Thu, 24 May 2007 14:47:27 -0000, Pavel Machek said:
>> Yes, if there's significantly more remote bad guys than local bad
>> guys, and if remote bad guys can't just get some local user first, AA
>> still has some value.
>
> Experience over on the Windows side of the fence indicates that "remote bad
> guys get some local user first" is a *MAJOR* part of the current real-world
> threat model - the vast majority of successful attacks on end-user boxes these
> days start off with either "Get user to (click on link|open attachment)" or
> "Subvert the path to a website (either by hacking the real site or hijacking
> the DNS) and deliver a drive-by fruiting when the user visits the page".

and if your local non-root user can create a hard link to /etc/shadow and 
access it they own your box anyway (they can just set the root password to 
anything they want). since I don't hear about this happening there are 
other restrictions that prevent this anyway.

everyone recognises that AA has limits, but the way people are 
emphisising these acknowledged limits is beginning to sound a bit shrill.

David Lang

-
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/