Blizard of mail from GitLab-Abuse-Automation
Matt Selsky
Matthew.Selsky at twosigma.com
Thu Dec 17 03:28:22 UTC 2020
The project audit settings in the GitLab UI show:
Author Object Action Target IP Address Date
GitLab-Abuse-Automation<https://gitlab.com/GitLab-Abuse-Automation>
NTPsec/ntpsec<https://gitlab.com/NTPsec/ntpsec>
Changed visibility from Public to Private
NTPsec/ntpsec
35.223.150.201
2020-12-16 11:16:40?
This smells like a bot gone awry.
@rlaager, do you have a ticket number handy that I can join? (off-list if you want)
Thanks,
-Matt
________________________________________
From: devel <devel-bounces at ntpsec.org> on behalf of Eric S. Raymond via devel <devel at ntpsec.org>
Sent: Wednesday, December 16, 2020 10:17 PM
To: Sanjeev Gupta
Cc: devel at ntpsec
Subject: Re: Blizard of mail from GitLab-Abuse-Automation
Sanjeev Gupta via devel <devel at ntpsec.org>:
> Ah, so not my fault.
>
> I tried updating my fork about 11 hours ago, and was to authenticate to
> pull from the NTPsec git repo. I tried with another repo, it worked, so I
> assumed one of us was modifying the security settings of the repo.
Somwething either very specific o very random is going on. All of the
dozen or so of my personal projects Ive had time to check are fine -
not taken private and it looks like the config button for public/private
would still work.
Mark Atwood has been briefed. I think he knows a phone number at Gif:ab.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
_______________________________________________
devel mailing list
devel at ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
More information about the devel
mailing list