Skip to content

Delete OpenSourceInsecurity.pdf #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sigaloid
Copy link

😠

@ethanzh
Copy link

ethanzh commented Apr 21, 2021

😠

@kyuridenamida
Copy link

Deleting OpenSourceInsecurity.pdf itself doesn't solve any problem tho

@stheid
Copy link

stheid commented Apr 22, 2021

The goal of the paper is definitely interesting however they seem to have failed to communicate properly and misused voluntary work.

@gonace
Copy link

gonace commented Apr 22, 2021

This is a pure case of how to try understanding something with a good cause but to do so in the most evil of ways.

@sigaloid
Copy link
Author

sigaloid commented Apr 22, 2021

Fellas, you are reading too much into a joke PR. The paper would have been a great venture into OSS vulnerabilities. had it not been in the stable branch of the largest OS in the world that billions of people rely on. Obviously the insights gained are very interesting and I would have liked if it had taken place legitimately w/o wasting days of volunteer time to look at patches and afterwards reverse the damage.

@CDAGaming
Copy link

Fellas, you are reading too much into a joke PR. The paper would have been a great venture into OSS vulnerabilities. had it not been in the stable branch of the largest OS in the world that billions of people rely on. Obviously the insights gained are very interesting and I would have liked if it had taken place legitimately w/o wasting days of volunteer time to look at patches and afterwards reverse the damage.

Agreed on this point. I'm just a person who uses a distro of Linux (Not at all experienced in the Kernel), but to see how close this was to breaching so many users, I feel it is justified that this paper is removed (Or at least re-drafted in a more ethical sense, IF the University ever gets a chance again after this debacle)

@h1z1
Copy link

h1z1 commented Apr 29, 2021

Horseshit.

This should be left as a tombstone to future employers. How much money did the UMN and/or CCP pay the Linux Foundation to make this "go away"?

You're literally sorry you got CAUGHT, nothing more.

Greg KH is a fool.

@sigaloid
Copy link
Author

This should be left as a tombstone to future employers. How much money did the UMN and/or CCP pay the Linux Foundation to make this "go away"?

Huh? what are you talking about ? it hasn't "gone away", they still cannot contribute to Linux...

@sigaloid
Copy link
Author

You know what, after going through your profile, it explains a lot.

@h1z1
Copy link

h1z1 commented Apr 29, 2021

What are YOU talking about? -- https://lwn.net/Articles/854064/

You know what, after going through your profile, it explains a lot.

Not sure what that is supposed to mean but OK. Have fun I guess.

@sigaloid
Copy link
Author

That is the kernel maintainers going through old commits- what implies that it is letting them back in at all?

@eebssk1
Copy link

eebssk1 commented Mar 31, 2024

This time, time repeated itself in another way on xz-utils. Look like the paper does nothing at all LOL.

@hiroki-chen
Copy link

This time, time repeated itself in another way on xz-utils. Look like the paper does nothing at all LOL.

"The only thing that we learn from history is that we learn nothing from history." lol

@omduggineni
Copy link

By the way, did UMN ever get let back into the Linux kernel?
(also came here from xz-utils)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.