PaX Team

@paxteam

pax.grsecurity.net
Vrijeme pridruživanja: veljača 2010.
1 fotografija ili videozapis Fotografije i videozapisi

Tweetovi

Blokirali ste korisnika/cu @paxteam

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

  1. 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

    2 proslijeđena tweeta 14 korisnika označava da im se sviđa
    Poništi
  2. 5. pro 2019.

    today's quiz: what's wrong with the seemingly trivial (and even reviewed) commit 492c88720d36eb662f9f10c1633f7726fbb07fc4? (it was just backported to stable kernels, hence the belated notice)

    1 reply 3 korisnika označavaju da im se sviđa
    Poništi
  3. 29. lis 2019.

    a myth from the same academic jokers^Wresearchers who graced us with their ASLR 'research' in the past: in table 2 shows RAP vulnerable to ret2user (it isn't, after all we invented KERNEXEC/i386 in 2003 and UDEREF in 2006 :) but everybody else not...

    15 proslijeđenih tweetova 25 korisnika označava da im se sviđa
    Poništi
  4. proslijedio/la je Tweet
    25. lis 2019.

    I always like bugs that prove you're the first to ever use something. We seem to be the first ones to try to use the event registration system for GCC plugins since it was introduced almost a decade ago:

    1 reply 4 proslijeđena tweeta 33 korisnika označavaju da im se sviđa
    Poništi
  5. proslijedio/la je Tweet
    3. ruj 2019.

    Teardown of a Failed Linux LTS Spectre Fix (alternatively: Sweeping Study of a Spectacular Stable Spectre Screwup) wherein we demonstrate the value of Respectre and an independent and funded security backport/review process for the Linux kernel

    1 reply 27 proslijeđenih tweetova 54 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  6. 22. srp 2019.

    today's quiz: find the infoleak bug introduced by upstream commit 85164fd8b05320 that was caught by a recent rewrite of our structleak GCC plugin.

    1 reply 5 proslijeđenih tweetova 15 korisnika označava da im se sviđa
    Poništi
  7. 27. lip 2019.

    Bet of the day: Intel vs. DSE ()

    4 proslijeđena tweeta 15 korisnika označava da im se sviđa
    Poništi
  8. 20. svi 2019.

    looks like FreeBSD (in)security is in very (in)capable hands:

    5 replies 5 proslijeđenih tweetova 24 korisnika označavaju da im se sviđa
    Poništi
  9. 18. ožu 2019.

    there's a 2 year old easter egg in enum scmi_error_codes, can you find it? :)

    1 reply 4 proslijeđena tweeta 9 korisnika označava da im se sviđa
    Poništi
  10. 8. ožu 2019.

    academic research not at its best. it took too long considering how since the beginning the only realistic threat model was 'arbitrary read-write' (slide 5 in ). i hope that people won't waste another 2 decades on such 'defenses'.

    4 proslijeđena tweeta 15 korisnika označava da im se sviđa
    Poništi
  11. 8. ožu 2019.

    btw, in case someone didn't figure it out yet, the hash is not a riddle but a git commit. happy hunting :).

    i'd propose to name the upcoming linux 5.0 kernel as Easter Egg Hunt Come Early and kick it off with 61cb5758d3c46bc1ba87694fefc0d9653613ce6b.
    3 korisnika označavaju da im se sviđa
    Poništi
  12. 2. ožu 2019.

    i'd propose to name the upcoming linux 5.0 kernel as Easter Egg Hunt Come Early and kick it off with 61cb5758d3c46bc1ba87694fefc0d9653613ce6b.

    2 proslijeđena tweeta 8 korisnika označava da im se sviđa
    Poništi
  13. 1. ožu 2019.

    look at what the cat^W^Warxiv has just dragged in: . finally someone dispels a myth, many more to go :).

    16 proslijeđenih tweetova 27 korisnika označava da im se sviđa
    Poništi
  14. 21. velj 2019.

    KSPP fairy tale du jour: … (hint: if RANDKSTACK was inspired by stackjacking then how could the supposed inspiring presentation have talked about it? perhaps because in reality it had already existed for almost a decade? :))

    6 proslijeđenih tweetova 13 korisnika označava da im se sviđa
    Poništi
  15. 21. velj 2019.

    the paper has been updated, i wish arxiv added some changebars...

    1 proslijeđeni tweet 3 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  16. 8. sij 2019.

    interesting paper from SP19: SoK: The Challenges, Pitfalls, and Perils of Using Hardware Performance Counters for Security (pdf: abstract: )

    18 proslijeđenih tweetova 27 korisnika označava da im se sviđa
    Poništi
  17. 15. stu 2018.

    almost 6 years later STRUCTLEAK comes to Windows:

    Please join the Windows kernel in wishing farewell to uninitialized plain-old-data structs on the stack. As of today's WIPFast build, any Windows code compiled with /kernel also gets compiled with InitAll, a compiler security feature that initializes POD structs at declaration.
    Prikaži ovu nit
    1 reply 11 proslijeđenih tweetova 34 korisnika označavaju da im se sviđa
    Poništi
  18. 14. stu 2018.

    A Systematic Evaluation of Transient Execution Attacks and Defenses:

    1 reply 4 proslijeđena tweeta 10 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  19. 15. lis 2018.

    Reminded during the 4.19 port the repeating theme of kernel devs still not understanding what they upstream from us: compare to . it cost the totally unnecessary realignment of a hundred lines of code in a core VM structure /o\.

    2 proslijeđena tweeta 10 korisnika označava da im se sviđa
    Poništi
  20. 4. lis 2018.

    so on the heels of we've just got another academic paper (, on no less than RAP itself) that thinks that calling execve = arbitrary code exec. off to a bad start...

    After yesterday's discussion about the use of Turing-Complete in exploitation papers, and realizing how commonly the other important term close to my heart, "weird machine", is misunderstood, I wrote a (rather unpolished) blog post about it.
    6 proslijeđenih tweetova 9 korisnika označava da im se sviđa
    Poništi

@paxteam još nije objavio nijedan Tweet.

Č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:

    ·