From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] RIP hardened-sources
Date: Sun, 30 Apr 2017 15:32:04 +0300 [thread overview]
Message-ID: <20170430153204.dee4dc8fbab98dce312b5be5@gentoo.org> (raw)
In-Reply-To: <1862f6e2-7bed-1414-630d-7e864e7662b5@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]
On Sun, 30 Apr 2017 13:55:16 +0200 SK wrote:
> And it's not about money from what I've read, should read this if you
> want some more information :
> https://hardenedlinux.github.io/announcement/2017/04/29/hardenedlinux-statement2.html
Sounds like a very lame excuse...
> Closing the public access doesn’t make PaX/Grsecurity a
> non-free/libre software. Those who purchase subscriptions can
> access the source code. We don’t see GPL violated in any way here.
The devil is in the detail. If subscribers will not be restricted
in all four freedoms including distribution, than this is
unfortunate, but legal action. But if subscribers will be limited
in distribution of the source code, e.g. by a threat of cancelling
their subscription, this will be illegal, this will be GPLv2
violation and PaXTeam will turn into bunch of criminals.
> After all, it’s PaX team/Spender’s creation and they can do
> anything they want.
No, they can't, because it is not their exclusive creation: many
people have contributed to PaX/GrSec over past years and they also
have rights for parts of these code. Moreover PaXTeam is using Linux
kernel code (without it the whole project is meaningless) and they
must respect copyright right and authorship of everyone who
contibuted to the Linux kernel. If GPLv2 is respected, all is OK.
But PaXTeams plays on the very edge of GPLv2 violation right now
(without the exact terms of the subscription it is not possible to
say if GPLv2 is violated or not).
Frankly, I'm more and more convinced that the real reason behind
all this charade is that GrSec/PaX is indeed a very powerful
security technology. So powerful that in became a serious hindrance
for nsa (or any other shitty agency) and PaXTeam was nailed down to
provide further updates only to "proper" customers and cut off wide
FOSS community from this powerful technology. Of course they likely
have some secret court orders denying them to disclosure the real
reason, so we all are watching this charade.
P.S. Please do not top-post.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-30 12:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 11:49 [gentoo-hardened] RIP hardened-sources Luis Ressel
2017-04-29 12:47 ` Alex Efros
2017-04-29 15:56 ` Daniel Cegiełka
2017-04-29 16:52 ` Javier Juan Martinez Cabezon
2017-04-29 16:58 ` Luis Ressel
2017-04-30 8:15 ` Javier Juan Martinez Cabezon
2017-04-29 17:04 ` Luis Ressel
2017-04-29 18:43 ` Daniel Cegiełka
2017-04-29 20:34 ` "Tóth Attila"
2017-04-29 22:04 ` Brant Williams
2017-04-30 13:00 ` Andrew Savchenko
2017-04-30 13:16 ` Alex Efros
2017-04-30 14:34 ` Andrew Savchenko
2017-04-30 14:56 ` "Tóth Attila"
2017-04-30 13:07 ` Andrew Savchenko
2017-04-29 13:11 ` Alex Efros
2017-04-29 13:46 ` PaX Team
2017-04-29 16:46 ` Alex Efros
2017-04-30 11:08 ` Alex Efros
2017-04-30 11:50 ` SK
2017-04-30 11:55 ` SK
2017-04-30 12:32 ` Andrew Savchenko [this message]
2017-04-30 12:56 ` Alex Efros
2017-04-30 13:28 ` Andrew Savchenko
2017-04-30 13:07 ` Daniel Cegiełka
2017-04-29 15:30 ` Paweł Hajdan, Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170430153204.dee4dc8fbab98dce312b5be5@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-hardened@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox