|
grsecurity
@
grsecurity
|
|
Foundational security for the Linux kernel. Solving the most difficult memory unsafety problems. Created by @opensrcsec
|
|
|
2.724
Tweetovi
|
2
Pratim
|
6.457
Osobe koje vas prate
|
| Tweetovi |
|
grsecurity
@grsecurity
|
6 h |
|
Storing this here: ee64c081fcfcdd78091f823c15e7886c9f8a61e38b078fc9298d427414a5682c
|
||
|
|
||
|
grsecurity
@grsecurity
|
11 h |
|
Typo: the above should have read 2011, not 2001 (though these subscription policies have been in place and widely-accepted for just as long)
|
||
|
|
||
|
grsecurity
@grsecurity
|
13 h |
|
This would make every Linux vendor, including all Linux kernel developers themselves, a GPL violator. You are free to root your cell phone, but the GPL doesn't magically force the vendor to support the breakage you caused. It didn't prevent you from making the modification
|
||
|
|
||
|
grsecurity
@grsecurity
|
13 h |
|
If it's an "added term" to exercise your own rights that in no way affect a user's ability to exercise their own GPL-granted rights of modification and distribution, then refusing to support a customer who has modified the software you provided them would also be a GPL violation
|
||
|
|
||
|
grsecurity
@grsecurity
|
13 h |
|
SFC on Red Hat's identical subscription model: "GPL Expert Gives Red Hat The All-Clear", from 2001 itwire.com/open-sauce/gpl… "I'm not persuaded that it's a 'further restriction'."
|
||
|
|
||
|
grsecurity
@grsecurity
|
13 h |
|
FSF (creators of the GPL itself) on an identical subscription model as ours, from 2004: hardware.slashdot.org/comments.pl?si… "I see no problems with this model. [...] you are under no obligation to supply future releases to anyone."
|
||
|
|
||
|
grsecurity
@grsecurity
|
13 h |
|
A statement from our legal counsel on today's Appeals Court decision: clfip.com/ip/blog/the-gr…
|
||
|
|
||
|
grsecurity
@grsecurity
|
18 h |
|
STACKLEAK has a 1% hit on kernel compilation too, doesn't at all mean STACKLEAK is cheap, just that the "benchmark" spends 99% of its time in userland, helping dilute whatever real performance hit exists
|
||
|
|
||
|
grsecurity
@grsecurity
|
18 h |
|
Outside of what would be mentioned there though, its reason for existence is based on a falsehood: "Backward edge CFI is not available for X86 at all today", typical bad/useless benchmarks: "1% hit in kernel compilation" 1% of what? kcbench "points" (elapsed wallclock)?
|
||
|
|
||
|
grsecurity
@grsecurity
|
19 h |
|
Would prefer to leave it for a Blackhat talk or something of that sort 😉
|
||
|
|
||
|
grsecurity
@grsecurity
|
19 h |
|
Added a few more, got through half of the list from 2018 on before my hands started cramping. Current count is now 464 😀 twitter.com/ageis/status/1…
|
||
|
|
||
|
grsecurity
@grsecurity
|
5. velj |
|
|
||
|
grsecurity
@grsecurity
|
2. velj |
|
No problem!
|
||
|
|
||
|
grsecurity
@grsecurity
|
2. velj |
|
#grsecurity beta patch for 5.5.1 has been released to beta testers, enjoy!
|
||
|
|
||
|
grsecurity
@grsecurity
|
2. velj |
|
|
||
|
grsecurity
@grsecurity
|
1. velj |
|
|
||
| grsecurity proslijedio/la je tweet | ||
|
Mathias Krause
@_minipli
|
1. velj |
|
Very proud and happy to join the team 😊 twitter.com/grsecurity/sta…
|
||
|
|
||
|
grsecurity
@grsecurity
|
1. velj |
|
You were right :)
|
||
|
|
||
| grsecurity proslijedio/la je tweet | ||
|
Open Source Security Inc.
@opensrcsec
|
1. velj |
|
Our team is growing! Very happy to welcome @_minipli as our newest full-time kernel developer, accelerating our development of the next generation of @grsecurity features
|
||
|
|
||
|
grsecurity
@grsecurity
|
1. velj |
|
Extremely excited to finally welcome @_minipli to the team!
|
||
|
|
||