From: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Louvian Lyndal <louvianlyndal@gmail.com>
Cc: "GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: CF ticketing system vulnerability 2025
Date: Mon, 5 May 2025 22:27:19 +0700 [thread overview]
Message-ID: <CAOG64qNe1PjQU61BS8ihgbWVEd9EUJXa1Py50uh00ZhC79aZ4A@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qO7oqoZk1HMeY2gqUGUJRFHdg--ca3q-2BkVLqacgAvBw@mail.gmail.com>
(( resend with signature ))
FYI for LL, chief ammar told me on Telegram that he has a new key, i
also have a new cv25519, trusted sources to import both of our keys:
https://github.com/ammarfaizi2.gpg
https://github.com/alviroiskandar.gpg
It should be good now.
@LL this may be the last plain text msg in this thread, the next
communication will be fully secure. Please confirm if you have key
issues.
--
Software Engineer & ITPM Officer
Alviro Iskandar Setiawan
next prev parent reply other threads:[~2025-05-05 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 14:35 CF ticketing system vulnerability 2025 Alviro Iskandar Setiawan
2025-05-05 15:27 ` Alviro Iskandar Setiawan [this message]
2025-05-05 15:35 ` Ammar Faizi
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=CAOG64qNe1PjQU61BS8ihgbWVEd9EUJXa1Py50uh00ZhC79aZ4A@mail.gmail.com \
--to=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=louvianlyndal@gmail.com \
/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