From: Casey Schaufler <casey@schaufler-ca.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: john.johansen@canonical.com, apparmor@lists.ubuntu.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
draht@suse.com, LSM <linux-security-module@vger.kernel.org>
Subject: Re: security_path hooks for xattr
Date: Thu, 26 Jan 2012 08:04:28 -0800 [thread overview]
Message-ID: <4F21798C.5040205@schaufler-ca.com> (raw)
In-Reply-To: <87fwf2y6mw.fsf@tucsk.pomaz.szeredi.hu>
On 1/26/2012 4:45 AM, Miklos Szeredi wrote:
> Forwarding from an internal bug report:
>
> "AppArmor does not mediate the xattr system calls for confined processes.
>
> As a consequence, a confined process can cross the confinement privilege
> boundary by reading or writing to extended attributes that the confined
> task should not have access to. The restrictions for security and user
> attributes read and write still apply according to DAC; however, this
> does not comply with the claim of AppArmor to mediate fipe
> operations. The use of extended attributes is very flexible, so that the
> effect of a missing mediation can lead to false assumptions in
> subsequent policy decisions (eCryptfs)."
>
> AFAIU this boils down to missing security hooks in *xattr().
>
> Would it be possible to add these hooks?
Please post proposed patches to linux-security-module@vger.kernel.org
>
> Thanks,
> Miklos
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2012-01-26 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 12:45 Miklos Szeredi
2012-01-26 16:04 ` Casey Schaufler [this message]
2012-01-26 21:57 ` John Johansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F21798C.5040205@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=apparmor@lists.ubuntu.com \
--cc=draht@suse.com \
--cc=john.johansen@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome