grsecurity

@grsecurity

Foundational security for the Linux kernel. Solving the most difficult memory unsafety problems. Created by

Vrijeme pridruživanja: lipanj 2012.

Tweetovi

Blokirali ste korisnika/cu @grsecurity

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @grsecurity

  1. 2. velj

    beta patch for 5.5.1 has been released to beta testers, enjoy!

    Poništi
  2. 2. velj
    Poništi
  3. proslijedio/la je Tweet
    1. velj
    Poništi
  4. proslijedio/la je Tweet
    1. velj

    Our team is growing! Very happy to welcome as our newest full-time kernel developer, accelerating our development of the next generation of features

    Poništi
  5. 1. velj

    Extremely excited to finally welcome to the team!

    Poništi
  6. 31. sij

    In the rare event where a manual fix wasn't already covered by Respectre, all such cases are investigated and the plugin's static analysis is improved to provide the necessary coverage

    Prikaži ovu nit
    Poništi
  7. 31. sij

    We expect to be already covered for most if not all of these Spectre v1/L1TF issues: Part of the work we do involves comparing manual upstream fixes to our verbose Respectre instrumentation logs.

    Prikaži ovu nit
    Poništi
  8. 31. sij

    MPX support being removed from 5.6, citing its adoption failure and removal of support from GCC:

    Poništi
  9. 30. sij

    The 5.5 beta patch should be available for testing within the next week

    Poništi
  10. 29. sij

    Looks like nothing was learned at all, the bad commit was backported to stable kernels today

    Poništi
  11. 29. sij

    This is the peak of technical self-improvement to me. Someone just spending a bunch of time on something for the sake of knowledge itself and demonstrating it can be done, regardless of the present utility of it. Dedication and follow-through are very rare these days

    Prikaži ovu nit
    Poništi
  12. 29. sij

    Hugely impressive amount of work in a very short amount of time. The github looks like a great resource for people to learn from:

    Prikaži ovu nit
    Poništi
  13. 28. sij
    Poništi
  14. proslijedio/la je Tweet
    27. sij

    Linux kernel 5.5 includes kcov extension that allows to collect code coverage from background kernel threads:

    Poništi
  15. 28. sij

    You did read the Kconfig help on the kernel you didn't configure or compile yourself, didn't you? :)

    Prikaži ovu nit
    Poništi
  16. 28. sij

    CONFIG_SECURITY_SELINUX_DISABLE being deprecated upstream in 5.6 because they had to weaken security with it being enabled: maintains the same read-onlyness for SELinux info regardless of the option. Also: b72c6bdeac96d21d67560779d5ea8bc3e3b0

    Prikaži ovu nit
    Poništi
  17. 27. sij

    5.5 just shipped with the bad fix too, so presumably this will get fixed in some 5.6-rc

    Prikaži ovu nit
    Poništi
  18. 26. sij

    it won't be backported until that happens first. This is why N-day is the new 0-day. It can take months for known fixes to make their way out to you, because the gears of this machine sometimes move very slowly.

    Prikaži ovu nit
    Poništi
  19. 26. sij

    5.4.15 was just released post-blog with the bug still intact. If you are surprised by this, then you are not aware of how the upstream -stable process works. The fix is queued by the maintainer for 5.5, but it hasn't yet landed in linus/master, so by -stable rules...

    Prikaži ovu nit
    Poništi
  20. 25. sij

    Looks like there will be a part 2 to this blog post, same people involved, same code base, same kind of bug, and all the info is already public (and even reported upstream). Let's see how long it takes this time:

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·