Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

github.com

Post reply on HN
Print view View original

11–20 of 27 posts

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#11

Post by wertik12 »

taukanda wrote: post #10
wertik12 wrote: post #8

Earlier quoted context omitted.

The main question is not about IPs, but about cloud providers configs. See more details here: https://github.com/opentofu/registry/pull/824

Not a lawyer, but isn't this under the same guidelines as decided by the TSC? no Russian use or access? Again heavy emphasis on "TSC" as the role.

In TSC I see IP block is mentioned? What do you mean by "Russian" access? From Russia? By people with Russian passport? By employees of Russian company? What if I live in Kazahstan and want to use Yandex.Cloud datacenter located there: https://yandex.cloud/en/docs/troubleshooting/business/how-to...?

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#13

Post by taukanda »

wertik12 wrote: post #11
taukanda wrote: post #10

Earlier quoted context omitted.

Not a lawyer, but isn't this under the same guidelines as decided by the TSC? no Russian use or access? Again heavy emphasis on "TSC" as the role.

In TSC I see IP block is mentioned? What do you mean by "Russian" access? From Russia? By people with Russian passport? By employees of Russian company? What if I live in Kazahstan and want to use Yandex.Cloud datacenter located there: https://yandex.cloud/en/docs/troubleshooting/business/how-to... ?

It's not that complex, unless you want it to be.

Russian geological access or businesses with strong ties to Russia or suspected strong ties to Russia. Every other detail is to be decided by the governing body of the project, which in this case has happened.

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#14

Post by wertik12 »

taukanda wrote: post #13
wertik12 wrote: post #11

Earlier quoted context omitted.

In TSC I see IP block is mentioned? What do you mean by "Russian" access? From Russia? By people with Russian passport? By employees of Russian company? What if I live in Kazahstan and want to use Yandex.Cloud datacenter located there: https://yandex.cloud/en/docs/troubleshooting/business/how-to... ?

It's not that complex, unless you want it to be. Russian geological access or businesses with strong ties to Russia or suspected strong ties to Russia. Every other detail is to be decided by the governing body of the project, which in this case has happened.

Sorry, but I still don't see a point in your message, how it is related to cloud config files that are in the repo. Open-source projects are not even covered by export control: https://www.linuxfoundation.org/resources/publications/under... If it is some voluntary decision by "governing body of the project" to remove config files that have nothing to do with IP-filtering to access, than it is exactly what I mention as "unreasonably explain by sanctions".

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#15

Post by egamirorrim »

ShakataGaNai wrote: post #2

IANAL but this change doesn't seem to make sense from any sort of "sanctions" perspective. Sure, block sanctioned countries from accessing your website or registry, etc - that makes sense. But removing providers? That doesn't seem to be related. The thing that makes this *super* f'd up is the fact that #1 - There is no commentary from the group members explaining this or what the policy change is (the few linked TSC…

> Super scummy.

Kind of like what Russia's doing to Ukraine eh?

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#18

Post by taukanda »

milliams wrote: post #16

I am amazed at how quickly that issue gathered all those comments, all with more thumbs up than I've even seen for one of these GitHub dramas.

and I'll bet most of them are like "TotallyJoeMcNuggets" with .ru emails and <10 repositories that are either scraping or CTF tasks or anti-malware tools.

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#19

Post by ebcode »

egamirorrim wrote: post #15
ShakataGaNai wrote: post #2

IANAL but this change doesn't seem to make sense from any sort of "sanctions" perspective. Sure, block sanctioned countries from accessing your website or registry, etc - that makes sense. But removing providers? That doesn't seem to be related. The thing that makes this *super* f'd up is the fact that #1 - There is no commentary from the group members explaining this or what the policy change is (the few linked TSC…

> Super scummy. Kind of like what Russia's doing to Ukraine eh?

"An eye for an eye makes the whole world blind." -- Mahatma Gandhi

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#20

Post by ebcode »

As a new user of OpenTofu, I find this disheartening. But if I try to put myself in the shoes of "the Ukranian dev", I can understand it.

Then I think about the United States' past (and present) wars of aggression overseas, and I can only imagine what a bad reputation american citizens must have all over the world. I'm sure many strangers must hate my guts without knowing me at all, and they have good reason for it.

But ultimately I think that pull/817 is discriminatory against a group of people, and therefor in violation of Github's TOS.

I hope OpenTofu's core devs can have a change of heart. And as hard as it might be, I hope "the Ukrainian dev" can have one too.

And who knows, maybe even Putin himself will be capable of a change of heart.

Post reply on HN