News for hackers. Stuff that matters.
Re:Alpine Linux 3.4.0 Released by striking on Tuesday May 31, 2016 @08:11PM (#11811266)
If you release the content to people who shouldn't have it, the next set will not be distributed to you. Your contract will not be renewed.

https://archive.is/qt0n2

Re:Alpine Linux 3.4.0 Released by techdragon on Tuesday May 31, 2016 @09:17PM (#11811500)
Wait ... That's actually working? I had heaps of things I shitcanned as not even remotely profitable to do because all common sense told me that this exact tactic would not work.
Re:Alpine Linux 3.4.0 Released by cyphar on Wednesday June 01, 2016 @01:43AM (#11812270)
I'm fairly sure it's not legal, because you're acting in bad faith (while you haven't changed the License terms, you are effectively coercing people into not being able to take advantage of the license). I'd also consider the tactic immoral because you're adding restrictions to free (and copylefted) software.
Re:Alpine Linux 3.4.0 Released by striking on Tuesday May 31, 2016 @09:24PM (#11811531)
You can. It seems legal (tho IANAL) and it seems to be working in practice.

Thing is, your distribution chain needs to be extremely tight (watermarked data or careful chain of trust) or else content will just get leaked every patch.

Re:Alpine Linux 3.4.0 Released by geofft on Tuesday May 31, 2016 @09:35PM (#11811563)
How do they reconcile this with the statement on https://grsecurity.net/download.php that the patches are under GPLv2 and distributors must ship the complete corresponding source? What happens if I redistribute grsecurity binary kernels with no other patches, and offer source as I am obligated to do?