From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Marc Plumb <lkml.mplumb@gmail.com>, Willy Tarreau <w@1wt.eu>,
Amit Klein <aksecurity@gmail.com>, George Spelvin <lkml@sdf.org>,
Eric Dumazet <edumazet@google.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Andy Lutomirski <luto@kernel.org>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>, Florian Westphal <fw@strlen.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] prandom32 changes for v5.10
Date: Wed, 21 Oct 2020 14:35:21 -0700 [thread overview]
Message-ID: <CAHk-=wi9Oe=NCG_S1X-rSFwkWe=vK7GYUHp22PFWa2W47WnzKA@mail.gmail.com> (raw)
In-Reply-To: <432132f9c678dc5093fd85055e5b708584018a0d.camel@perches.com>
On Wed, Oct 21, 2020 at 2:20 PM Joe Perches <joe@perches.com> wrote:
>
> While secure solutions are useful, I really wonder if
> "George Spelvin" is a real person.
It's not his real name, no, but he's a real person.
I do have his real name from years ago when I needed to confirm his
identity for sign-offs (I forget what for, I think it was some dcache
name hashing thing).
So I can confirm he's a real person who just wants to keep private,
and is competent when it comes to hashing and security.
Linus
next prev parent reply other threads:[~2020-10-21 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:32 [GIT PULL] prandom32 changes for v5.10 Willy Tarreau
[not found] ` <CANEQ_+Jyf-MZEsvT5iMu0a=waJCiAKdLaOfLHe_py6AXOt-hjQ@mail.gmail.com>
2020-10-20 23:08 ` Linus Torvalds
2020-10-21 3:27 ` Willy Tarreau
2020-10-21 20:52 ` Marc Plumb
2020-10-21 21:20 ` Joe Perches
2020-10-21 21:35 ` Linus Torvalds [this message]
2020-10-21 21:41 ` Joe Perches
2020-10-22 2:12 ` Willy Tarreau
2020-10-24 19:34 Willy Tarreau
2020-10-25 18:35 ` pr-tracker-bot
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='CAHk-=wi9Oe=NCG_S1X-rSFwkWe=vK7GYUHp22PFWa2W47WnzKA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=Jason@zx2c4.com \
--cc=aksecurity@gmail.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.mplumb@gmail.com \
--cc=lkml@sdf.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
/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).