David Benjamin

@davidben__

There are lots of people with my name. I'm the Chromium (and cuttlefish) one. I work on TLS, privacy, and general amusements in Chrome.

Vrijeme pridruživanja: studeni 2014.

Tweetovi

Blokirali ste korisnika/cu @davidben__

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

  1. proslijedio/la je Tweet
    3. lis 2019.

    Chrome is starting to move towards blocking all mixed content. 🔒🎉 see this blog post for why and how: (cc )

    Poništi
  2. proslijedio/la je Tweet
    31. srp 2019.

    Excited++! "Intent to Implement: Partition the HTTP Cache" -

    Poništi
  3. proslijedio/la je Tweet
    12. pro 2018.

    CECPQ2: further post-quantum TLS experiments in Chrome.

    Poništi
  4. proslijedio/la je Tweet
    15. lis 2018.
    Poništi
  5. 2. lis 2018.

    Hey , is TLS 1.3 intolerant and will break in Chrome & Firefox soon. Are you running a prerelease OpenSSL 1.1.1? They had a version negotiation bug:

    Poništi
  6. proslijedio/la je Tweet
    24. srp 2018.

    IT'S ALIVE! chrome 68 rolls to stable today, and with it, all HTTP pages are marked "not secure". happy "HTTP-bad" day, internet! 🍾🔐

    Poništi
  7. proslijedio/la je Tweet
    11. srp 2018.

    After lots of incredibly hard work by a ton of folks on Chrome, full site isolation is reality on desktop: . Thank you everyone who has helped, too long of a list to include!

    Prikaži ovu nit
    Poništi
  8. proslijedio/la je Tweet
    17. svi 2018.

    check out our roadmap for the next ~6 months of Chrome security indicators! (h/t )

    Poništi
  9. proslijedio/la je Tweet
    10. ožu 2018.

    When Her Majesty's Government is confused about TLS 1.3:

    Poništi
  10. 10. ožu 2018.

    TLS 1.3 (draft 23) is rolling out with Chrome 65! Let's hope it sticks. Third time's the charm?

    Poništi
  11. proslijedio/la je Tweet

    Fast ECC implementations extraction from Coq proofs, with target and curve independence.

    Poništi
  12. proslijedio/la je Tweet
    8. velj 2018.

    🔐⚠️ The moment we've all been waiting for! Chrome will mark all HTTP sites as "Not secure" in July 2018. 🔐⚠️

    Prikaži ovu nit
    Poništi
  13. proslijedio/la je Tweet
    12. srp 2017.

    Dear Lazy Twitter: does anyone have a contact at Fortinet (r.e. their TLS inspection)?

    Poništi
  14. proslijedio/la je Tweet
    Poništi
  15. proslijedio/la je Tweet

    TA17-075A: HTTPS Interception Weakens TLS Security

    Poništi
  16. proslijedio/la je Tweet
    23. velj 2017.

    Remember: things would be much more awkward today if , and friends hadn't spent years working to rid the Web PKI of SHA-1.

    Poništi
  17. proslijedio/la je Tweet

    I am very happy to announce that we found the first SHA1 collision -

    Poništi
  18. proslijedio/la je Tweet
    21. velj 2017.

    Dear lazy-Twitter, if anyone knows technical contacts r.e. MITM proxies/firewalls at Watchguard or iBoss, could you email or DM me?

    Poništi
  19. proslijedio/la je Tweet
    25. sij 2017.

    Some background and details on TLS 1.3, OpenSSL, Akamai. TLS1.3 FTW

    Poništi
  20. proslijedio/la je Tweet
    8. sij 2017.

    Still a little buggy, but you can try out chrome://flags/-http-form-warning in Chrome Canary to see HTTP warnings on autofill!

    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:

    ·