URL: <https://savannah.nongnu.org/support/?111331>
Summary: received GPG-encrypted spam as new Savannah ticket
Group: Savannah Administration
Submitter: gbranden
Submitted: Tue 28 Oct 2025 12:10:18 AM UTC
Category: Savannah trackers - bugs, tasks, etc.
Priority: 5 - Normal
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Operating System: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Tue 28 Oct 2025 12:10:18 AM UTC By: G. Branden Robinson <gbranden>
This is more of a heads-up to Savannah administrators than anything. Off the
top of my head I'm not sure what countermeasures can be implemented that
wouldn't foreclose potentially legitimate attempts to discreetly report a
security vulnerability in a Savannah project.
See _groff_ bug #67640 and bug #67641.
If the only action to resolve this is for the admins to take note of it (and
maybe check the inbound IP addresses of the web session(s) that produced it
for any remarkable properties), I'm fine with that.
I guess this message can also serve as part of an audit trail in the event
this/these was/were (a) legitimate attempt at (a) report(s), recording that I
erroneously categorized the message.
I note that usually people misspell my name as "Brandon". Misspelling it as
"Bertrand Garrigues" sets a new Levenshtein distance record in this domain.
Gold medal!
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/support/?111331>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
signature.asc
Description: PGP signature
