From: Kees Cook <keescook@chromium.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.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>,
Benjamin LaHaise <bcrl@kvack.org>,
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 14:02:00 -0800 [thread overview]
Message-ID: <CAGXu5jL3AZii611qGbVyOCaK-Ua1+3H7i2KAV3zfT0hGRUiAZQ@mail.gmail.com> (raw)
In-Reply-To: <20161104184505.GA21320@redhat.com>
On Fri, Nov 4, 2016 at 11:45 AM, Oleg Nesterov <oleg@redhat.com> wrote:
> Eric, I hope you see my emails, I got the "Undelivered Mail Returned to Sender"
> ...
> This is the mail system at host mail.kernel.org.
> ...
> <ebiederm@xmission.com> (expanded from <security@kernel.org>): host
> mx.xmission.com[166.70.12.20] said: 550-XM-RJCT16: SPF Failure
> (ip=198.145.29.136, frm=oleg@redhat.com, 550 result=fail) (in reply to RCPT
> TO command)
>
> right now I have no idea what does this mean.
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...
-Kees
--
Kees Cook
Nexus Security
next prev parent reply other threads:[~2016-11-08 22:02 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 [this message]
2016-11-08 22:46 ` Eric W. Biederman
2016-11-08 22:56 ` Benjamin LaHaise
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=CAGXu5jL3AZii611qGbVyOCaK-Ua1+3H7i2KAV3zfT0hGRUiAZQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=aul@paul-moore.com \
--cc=bcrl@kvack.org \
--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=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).