#grsecurity — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #grsecurity, aggregated by home.social.
-
New PaXtest release after years of silence 🥳
Git source: https://github.com/opensrcsec/paxtest/
Small announcement: https://grsecurity.net/paxtest_release/ (worth a read, contains even more info than what’s written about 😛)
-
New PaXtest release after years of silence 🥳
Git source: https://github.com/opensrcsec/paxtest/
Small announcement: https://grsecurity.net/paxtest_release/ (worth a read, contains even more info than what’s written about 😛)
-
New PaXtest release after years of silence 🥳
Git source: https://github.com/opensrcsec/paxtest/
Small announcement: https://grsecurity.net/paxtest_release/ (worth a read, contains even more info than what’s written about 😛)
-
New PaXtest release after years of silence 🥳
Git source: https://github.com/opensrcsec/paxtest/
Small announcement: https://grsecurity.net/paxtest_release/ (worth a read, contains even more info than what’s written about 😛)
-
New PaXtest release after years of silence 🥳
Git source: https://github.com/opensrcsec/paxtest/
Small announcement: https://grsecurity.net/paxtest_release/ (worth a read, contains even more info than what’s written about 😛)
-
Similarly, a lot of decisions are mostly done out of necessity
[i.e. #SystemD doesn't fit into 1440kB]or due to licensing conflicts
[i.e. #grsec / #grsecurity is #paywalling access to it's sources so we won't even consider it as #FLOSS... ]
https://grsecurity.netAlso apparently grsec managed to get their #Wikipedia [article wiped](
https://en.wikipedia.org/wiki/Grsecurity ) so [WaybackMachine to the rescue]( https://web.archive.org/web/20190429055854/https://en.wikipedia.org/wiki/Grsecurity )...So yeah...
I hope that answers the question... -
@landley The sad part is that you are in fact correct.
The only thing #Copyleft like #GPLv3, #AGPLv3 and espechally #AssholeLicensing of the #SSPL, #RHEL and #grsecurity kind can do is commit #AssetDenial and even that is flaky as one can only put actual #code under a license and not an implementation of something like a #Codec...
...But those are usually covered by #patents and other legalese trolling efforts, like the way #MELP / #MELPe is licensed so everyone who doesn't want to exclusively make a radio for NATO / U.S. DoD has to arrange a licensing deal woth half a dozen tech giants, so #Codec2 had to be made...
https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction
https://en.wikipedia.org/wiki/Codec_2As of now I am considering to relicense my content under #0BSD and sinve very few of my projects have any external contributions, this should be trivial to do so.