From: Benjamin LaHaise <bcrl@kvack.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Kees Cook <keescook@chromium.org>,
Oleg Nesterov <oleg@redhat.com>, Jann Horn <jann@thejh.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Roland McGrath <roland@hack.frob.com>,
John Johansen <john.johansen@canonical.com>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Paul Moore <aul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
Casey Schaufler <casey@schaufler-ca.com>,
Andrew Morton <akpm@linux-foundation.org>,
Janis Danisevskis <jdanis@google.com>,
Seth Forshee <seth.forshee@canonical.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ben Hutchings <ben@decadent.org.uk>,
Andy Lutomirski <luto@amacapital.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Krister Johansen <kjlx@templeofstupid.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
"security@kernel.org" <security@kernel.org>
Subject: Re: [PATCH v3 1/8] exec: introduce cred_guard_light
Date: Tue, 8 Nov 2016 17:56:51 -0500 [thread overview]
Message-ID: <20161108225651.GJ16345@kvack.org> (raw)
In-Reply-To: <87bmxptwrv.fsf@xmission.com>
On Tue, Nov 08, 2016 at 04:46:44PM -0600, Eric W. Biederman wrote:
> Kees Cook <keescook@chromium.org> writes:
...
> > This is a problem for Google folks too sometimes. This is saying that
> > xmission.com is checking redhat.com's SPF records and refusing to let
> > kernel.org deliver email as if it were redhat.com (due to
> > security@kernel.org being an alias not a mailing list). There aren't
> > good solutions for this, but best I've found is to have my
> > security@kernel.org alias be a @kernel.org address instead of an
> > @google.com address...
>
> Ugh. Is even redhat configuring the redhat email to do that?
> I will have to look.
>
> Last I looked xmission.com was just enforcing the policy that the other
> mail domains were asking to be enforced on themselves. But those are
> policies that are incompatible with mailing lists in general. Although
> I do get confused about which part SPF and DKIM play in this mess.
>
> I just remember that the last several ``enhancements'' to email were
> busily breaking mailing lists and I thought they were completely insane.
> I can even find evidence that it is (or at least was) so bad that email
> standards comittee member's can't comminicate with each other via email
> lists.
>
> vger.kernel.org appears to rewrite the envelope sender to avoid
> problems.
Envelope sender rewriting is insufficient, the From: lines need to be
rewritten to be compliant. This is a pain in the ass for the @kvack.org
mailing lists as well -- people with @google.com addresses don't see the
mailing list postings of users from @google.com and other domains using
"enhanced" email header "validation" techniques.
-ben
> If xmission is doing any more than just performing what the domain of
> the senders of email asked them to do I will be happy to see if I can
> to sort it out.
>
> Eric
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2016-11-08 22:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 21:46 [PATCH v3 0/8] Various fixes related to ptrace_may_access() Jann Horn
2016-10-30 21:46 ` [PATCH v3 1/8] exec: introduce cred_guard_light Jann Horn
2016-11-02 18:18 ` Oleg Nesterov
2016-11-02 20:50 ` Jann Horn
2016-11-02 21:38 ` Ben Hutchings
2016-11-02 21:54 ` Jann Horn
2016-11-03 18:12 ` Oleg Nesterov
2016-11-03 21:17 ` Jann Horn
2016-11-04 13:26 ` Eric W. Biederman
2016-11-04 15:00 ` Eric W. Biederman
2016-11-04 18:04 ` Oleg Nesterov
2016-11-04 18:45 ` Oleg Nesterov
2016-11-05 14:56 ` Oleg Nesterov
2016-11-09 0:34 ` Eric W. Biederman
2016-11-16 20:03 ` Eric W. Biederman
2016-11-08 22:02 ` Kees Cook
2016-11-08 22:46 ` Eric W. Biederman
2016-11-08 22:56 ` Benjamin LaHaise [this message]
2016-11-08 23:33 ` Eric W. Biederman
2016-10-30 21:46 ` [PATCH v3 2/8] exec: add privunit to task_struct Jann Horn
2016-10-30 21:46 ` [PATCH v3 3/8] proc: use open()-time creds for ptrace checks Jann Horn
2016-10-30 21:46 ` [PATCH v3 4/8] futex: don't leak robust_list pointer Jann Horn
2016-10-30 21:46 ` [PATCH v3 5/8] proc: lock properly in ptrace_may_access callers Jann Horn
2016-10-30 21:46 ` [PATCH v3 6/8] fs/proc: fix attr access check Jann Horn
2016-10-30 21:46 ` [PATCH v3 7/8] proc: fix timerslack_ns handling Jann Horn
2016-10-30 21:46 ` [PATCH v3 8/8] Documentation: add security/ptrace_checks.txt Jann Horn
2016-11-01 23:57 ` [PATCH v3 0/8] Various fixes related to ptrace_may_access() Linus Torvalds
2016-11-02 18:38 ` Oleg Nesterov
2016-11-02 21:40 ` Jann Horn
2016-11-03 19:09 ` Andrew Morton
2016-11-03 20:01 ` Jann Horn
2016-11-04 0:57 ` James Morris
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=20161108225651.GJ16345@kvack.org \
--to=bcrl@kvack.org \
--cc=akpm@linux-foundation.org \
--cc=aul@paul-moore.com \
--cc=ben@decadent.org.uk \
--cc=casey@schaufler-ca.com \
--cc=ebiederm@xmission.com \
--cc=eparis@parisplace.org \
--cc=james.l.morris@oracle.com \
--cc=jann@thejh.net \
--cc=jdanis@google.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=kjlx@templeofstupid.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=roland@hack.frob.com \
--cc=sds@tycho.nsa.gov \
--cc=security@kernel.org \
--cc=serge@hallyn.com \
--cc=seth.forshee@canonical.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).