GitHub incident 2022-03-23

Re:GitHub incident 2022-03-23 by Jiejeing on Wednesday March 23, 2022 @11:22AM (#30779391)

If you are a closed org, that is. Running your own gitea or gitlab with registration enabled and having to deal with spam is a real hurdle.

[ Parent | on HN ]

Re:GitHub incident 2022-03-23 by julianlam on Wednesday March 23, 2022 @11:27AM (#30779449)

Is it not possible to restrict access to the git server from a VPN server only?

Just off the top of my head, that's one thing you can do.

[ Parent | on HN ]

Re:GitHub incident 2022-03-23 by mlyle on Wednesday March 23, 2022 @11:39AM (#30779606)

Yah, that's a "closed org". When you need to deal with the public at large, you need to deal with user registration issues and spam.

[ Parent | on HN ]

Re:GitHub incident 2022-03-23 by Dobbs on Wednesday March 23, 2022 @11:40AM (#30779611)

So now every person who wants to contribute to your open source project has to setup a VPN client?

The parent comment was explicitly about non-closed (e.g. private) orgs.

[ Parent | on HN ]