From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: vapier@chromium.org
Subject: Re: [vapier@gmail.com: man-pages-website: crush logo]
Date: Thu, 20 Aug 2026 21:22:31 +0200 [thread overview]
Message-ID: <aodTg9n__Xq_0BXg@debian> (raw)
In-Reply-To: <aockPc7I9x7E2DXk@debian>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Hi Mike,
I just learnt you had a gmail account (first email I receive from that
address), and also just learnt you don't have a @gentoo address anymore.
Could you confirm whether that mail from you is authentic? (And if
possible, it would be ideal if it were done in a signed email.)
Have a lovely night!
Alex
> Date: 2026-08-20 18:02:25+0200
> From: Alejandro Colomar <alx@kernel.org>
>
> Hi!
>
> I'd like to note that I've received a phishing attempt (or so I suspect;
> if it's a real message, please confirm, Mike) from someone claiming to
> be a usual contributor.
>
> The message contained a compressed file, which for obvious reasons
> I won't open (I can forward it if anyone wants to see it).
>
> This is a reminder to be aware that people are doing these things, and
> that I'd very much prefer to see PGP-signed email, especially from
> frequent contributors.
>
>
> Have a lovely day!
> Alex
>
> ----- Forwarded message from Mike Frysinger <vapier@gmail.com> -----
>
> Date: Thu, 20 Aug 2026 22:36:17 +0700
> From: Mike Frysinger <vapier@gmail.com>
> To: alx@kernel.org
> Subject: man-pages-website: crush logo
> Message-ID: <CAL+h-jCujsyaHq+7V3D-M0PVqbHakp=+Z-Ag4nT_7xsESotocg@mail.gmail.com>
>
>
>
>
>
> ----- End forwarded message -----
>
> --
> <https://www.alejandro-colomar.es>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-08-20 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 16:02 [vapier@gmail.com: man-pages-website: crush logo] Alejandro Colomar
2026-08-20 19:22 ` Alejandro Colomar [this message]
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=aodTg9n__Xq_0BXg@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=vapier@chromium.org \
/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