linux-kernel - Re: [tip:x86/build] x86/um/vdso: Drop implicit common-page-size linker flag

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

Message-ID: <20181211205353.GR27375@zn.tnic>
Date:   Tue, 11 Dec 2018 21:53:53 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
Cc:     bp@...e.de, richard@....at,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        mingo@...hat.com, LKML <linux-kernel@...r.kernel.org>,
        x86@...nel.org, hpa@...or.com, jdike@...toit.com,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...nel.org>,
        linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/build] x86/um/vdso: Drop implicit common-page-size
 linker flag

On Tue, Dec 11, 2018 at 11:08:30AM -0800, Nick Desaulniers wrote:
> Personal gmail account, yes. Corporate gmail, no, IIUC.  There was a
> pretty big internal thread where all of our kernel contributors got
> cut off one day and were scrambling to figure out how to send/review
> patches as their workflows were interrupted.

Gotta love all those stories of kernel people and corporate mail
systems... And every company has its own strange idiosyncrasies...

> Something is still not configured right when I send patches
> (maintainers have merged patches with my email address but no name, I
> assume from working with mbox files).

Yeah, had to fix that up today too. For some reason your git setup

 X-Mailer: git-send-email 2.20.0.rc2.403.gdbc3b29805-goog

doesn't do names in From:

https://lkml.kernel.org/r/20181210222718.19926-1-ndesaulniers@google.com

> We have some internal tool that's smtp based but does the two factor
> authentication.

So some people send from !corporate mail servers but put their company's
name in brackets to keep attribution:

Signed-off-by: <First name> <Last name> (<Company>) <email@...ress.com>

For example. Dunno if that's something that would make sense for your
case though.

> Internal Gmail developers were able to help me verify that SPF was
> setup correctly, but indeed there's no DKIM.  This article has more
> info: https://support.google.com/mail/answer/81126?hl=en.

I know that one from my very recent past. :)

> Richard, I don't know if that's a lot of work on your end, but other
> folks using gmail might have the same issue repeatedly with receiving
> emails from your domain otherwise.

We had to do that too for our domain.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.