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

Date:   Tue, 11 Dec 2018 11:08:30 -0800
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     bp@...e.de, richard@....at
Cc:     bp@...en8.de, 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 10:06 AM Borislav Petkov <bp@...e.de> wrote:
>
> On Tue, Dec 11, 2018 at 09:53:49AM -0800, Nick Desaulniers wrote:
> > Indeed it was.  I'm forced to use Gmail's clients for this work
> > account and all that implies (no plain text responses when mobile).
>
> Can't you access it over imap?

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.  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).

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

>
> > Maybe I can file a bug about this internally...
>
> FWIW, people have looked for ways to report such issues in the past...
>
> But in this particular case, DKIM is pretty good spam protection
> mechanism so enabling it is a good idea.

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.  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.

-- 
Thanks,
~Nick Desaulniers