Live data from Hacker News

Spoiling Linux Kernel with "sanctioned" code

printserver.ink

31–40 of 72 posts

Re: Spoiling Linux Kernel with "sanctioned" code

#32
post #15

Earlier quoted context omitted.

This is a great thing for innovation though? Nations/blocs protecting their tech interests will result in more jobs to go round in the industry, more unique ideas, and less centalisation, surely? The globalised, hyper-centralised world is a bit boring, tbh.

I forecast that you will not be bored, and may have other, stronger feelings. Ask Ukrainians

I spent like 20% of my adult life in Ukraine and Russia. They overwhelmingly don't like the globalosed world.

Ukraine might be a fashion symbol in the west, but when I was volunteering out there in the first year, the points of view where mainly wanting to be like Poland; not absorbing the values of the wider west.

Re: Spoiling Linux Kernel with "sanctioned" code

#33
FTA: "The code can't be merged into Linux kernel unless the contributor can verify they're not working in a sanctioned company of said country (guilty until proven innocent)"

That's explicitly not true, according to the Linux foundation. OFAC sanctions restrict providing a service, so here the violation would be two-way collaboration, not the receipt of information.

The kernel could review & merge the patch without running afoul of sanctions. What they cannot do is have dialogue with the sanctioned contributor.

Logic is not subject to sanctions, and anyone also may look at the submission and implement a matching fix.

https://www.linuxfoundation.org/blog/navigating-global-regul...

Re: Spoiling Linux Kernel with "sanctioned" code

#34
post #28

So here’s the thing. The author thinks that Greg K-H is under some sort of obligation to respond to the patch they submitted. But that’s just not how free software works. Greg K-H is a fully autonomous human being and he doesn’t work for the author of tfa. It sucks that we live in a world where nation states try to put exploits into the linux kernel and other foss projects but we very much do live in that world. It s…

> So here’s the thing ... That was very much not the thing. He's raising an interesting point, if true. Namely that sanctioned countries could severely damage the progress of Linux by supplying good patches.

> damage the progress of Linux by supplying good patches

Suffering from success

Re: Spoiling Linux Kernel with "sanctioned" code

#38
post #37

[flagged]

A person is not responsible for the actions of their government. All governments wage war and cause suffering.

I have many close friends who are Russian by nationality. Russian by crime of accident of birth. So many of my friends in this situation abhor the actions of their government.

The Mentor stated it best. Phrack 7, 1986:

"We exist without skin color, without nationality, without religious bias... and you call us criminals. You build atomic bombs, you wage wars, you murder, cheat, and lie to us and try to make us believe it's for our own good, yet we're the criminals."

Re: Spoiling Linux Kernel with "sanctioned" code

#40
post #21
post #5

I've been thinking lately that what underpinned the FOSS golden age was not actually decentralized VCS and high-quality forges, nor even ZIRP, but rather peacetime. After a period of branches and patchsets, full national hard forks are going to become de rigeur, and linux-derived OSes across the world are going to bloom necessarily, as we no longer have the kind of ambient trust required to collaborate across borders…

It's even worse: the same logic is already starting to fracture the internet at large.

I mean the capabilities of the internet aren't something you really want to have aimed AT you when you're fighting in a war. The internet grew after the cold war ended and it will change as another cold/hot war starts.
Post reply on HN