| Tweetovi |
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
21. sij |
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
9. sij |
|
|
||
| Adam 'pi3' Zabrocki proslijedio/la je tweet | ||
|
Solar Designer
@solardiz
|
8. sij |
|
As far as I see, we did comment on all of the bypasses seen in that repo so far, on the lkrg-users mailing list. We also addressed many of these in newer LKRG. Now that Ilya collected the bypasses so nicely in that repo, we should perhaps also collect our commentary in one place.
|
||
|
|
||
| Adam 'pi3' Zabrocki proslijedio/la je tweet | ||
|
Openwall
@Openwall
|
25. pro |
|
passwdqc 1.4.0, a new version of our password/passphrase strength checking and enforcement tool set, is out. This version adds optional non-English messages, Linux-PAM audit support, and includes portability and documentation fixes: openwall.com/lists/announce…
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
14. pro |
|
Good Luck and... congrats? :)
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
4. pro |
|
In case of hypothetical more privileged true-RO owned page (which I was referring to as a way to protect such a buffers), CR0.WP won't have any effect since they won't be the owner of the page - just have visibility of it / mapping.
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
4. pro |
|
One way to protect it is to have true-RO enforced from different trustlevel (ring -1 / TZ?) and use it to protect such buffers. For desired modification invoke hypercall and do necessary modification on behalf from the secure zone (ring -1 / TZ).
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
4. pro |
|
Locking down group b) and c) is problematic from the compatibility point of view since you can kill desired functionality. Group d) can be removed if we don't need with mcelog daemon which can be for some people unacceptable. Nevertheless, there is a lot of potential targets.
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
4. pro |
|
My 2 cents, attacking UMH is well known but also problematic for defense. For LKRG UMH whitelisting I've went trough the all UMH consumers and identify 4 groups of them: a) can be hardcoded b) can be changed via sysctl / procfs interface c) can be set via module param d) mcelog
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
3. pro |
|
Ah "kendo marxist" ;-) You are another Polish friend from Google whom I know and is beating people with bamboo stick. I hope it's just a coincidence... :P
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
3. pro |
|
What's your hobby in CV? :>
|
||
|
|
||
| Adam 'pi3' Zabrocki proslijedio/la je tweet | ||
|
Hardened-GNU/Linux
@hardenedlinux
|
19. stu |
|
|
||
|
|
||
| Adam 'pi3' Zabrocki proslijedio/la je tweet | ||
|
Whonix ™
@Whonix
|
15. stu |
|
🔥🔥🔥 #LKRG 🔥🔥🔥
🔥🔥🔥 Innovate security feature. It renders whole classes of kernel exploits ineffective. Learn more: 🔥🔥🔥
whonix.org/wiki/Linux_Ker…
|
||
|
|
||
| Adam 'pi3' Zabrocki proslijedio/la je tweet | ||
|
Whonix ™
@Whonix
|
11. stu |
|
|
||
| Adam 'pi3' Zabrocki proslijedio/la je tweet | ||
|
Alex Matrosov
@matrosov
|
6. stu |
|
I’m thrilled to announce we are growing our offensive security research team. I want to welcome @Adam_pi3 and @AlexTereshkin to Nvidia!!
|
||
|
|
||
| Adam 'pi3' Zabrocki proslijedio/la je tweet | ||
|
Alexander Popov
@a13xp0p0v
|
2. stu |
|
I just did the full disclosure of the exploitable bugs in the 'vivid' driver of the Linux kernel:
openwall.com/lists/oss-secu…
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
1. stu |
|
I am, but sometimes I need a break ;p
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
31. lis |
|
I was able to run Linux Kernel Runtime Guard (#LKRG) on raspberry pi 3 (model B). Very beta version support for ARM32 might be coming. Took me some time but it's possible and works fine. pic.twitter.com/tmsGYZ1pt8
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
10. lis |
|
lol, smart decision! :)
|
||
|
|
||
|
Adam 'pi3' Zabrocki
@Adam_pi3
|
10. lis |
|
Thanks ;-)
|
||
|
|
||