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.
Joined November 2014
- Tweets423
- Following143
- Followers985
- Likes47
David Benjamin retweeted
Picking parameters: imperialviolet.org/2022/03/1…. (It was too long for Twitter.)
I look forward to all the latent X.509 bugs around 2050, as we rollover from UTCTime to GeneralizedTime.
Did you think we were done with two-digit years after Y2K? Well, X.509 has some news for you!
David Benjamin retweeted
1/ Are you a software engineer interested in security, PKI, applied crypto, related topics, & willing to live/work in Washington DC area? Here's a job posting: goo.gle/30shtqE & a 🧵 for you (read to the end for some caveats, including other roles opening up soon):
David Benjamin retweeted
I'm hiring a technical lead for the team we're building in DC to work on the Privacy Sandbox. Please spread the word and feel free to ping with any questions.
goo.gle/30EVxZj
David Benjamin retweeted
if you're running Chrome Canary, Dev, or Beta and you want some more https in your life, go to chrome://flags and search for + enable "#omnibox-default-typed-navigations-to-https". Chrome will now send schemeless hostnames over https:// instead of http:// by default😎
cc @meacer
David Benjamin retweeted
Chrome is starting to move towards blocking all mixed content. 🔒🎉 see this blog post for why and how:
security.googleblog.com/2019…
(cc @carlosjoan91)
David Benjamin retweeted
Excited++! "Intent to Implement: Partition the HTTP Cache" - groups.google.com/a/chromium…
David Benjamin retweeted
CECPQ2: further post-quantum TLS experiments in Chrome. imperialviolet.org/2018/12/1…
David Benjamin retweeted
Apple, Google, Microsoft, and Mozilla today jointly announced a timeline for the removal of TLS 1.0 and 1.1 from their respective browsers. webkit.org/blog/8462/depreca… security.googleblog.com/2018… blogs.windows.com/msedgedev/… blog.mozilla.org/security/20…
Hey @thedarktangent, defcon.org 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: github.com/openssl/openssl/i…
David Benjamin retweeted
IT'S ALIVE! chrome 68 rolls to stable today, and with it, all HTTP pages are marked "not secure". happy "HTTP-bad" day, internet! 🍾🔐
blog.google/products/chrome/… xitter.cf/emschec/status/9616621…
🔐⚠️ The moment we've all been waiting for! Chrome will mark all HTTP sites as "Not secure" in July 2018. 🔐⚠️
security.googleblog.com/2018…
David Benjamin retweeted
After lots of incredibly hard work by a ton of folks on Chrome, full site isolation is reality on desktop: security.googleblog.com/2018….
Thank you everyone who has helped, too long of a list to include!
David Benjamin retweeted
check out our roadmap for the next ~6 months of Chrome security indicators! blog.chromium.org/2018/05/ev… (h/t @emschec)
David Benjamin retweeted
When Her Majesty's Government is confused about TLS 1.3: imperialviolet.org/2018/03/1…
David Benjamin retweeted
🔐⚠️ The moment we've all been waiting for! Chrome will mark all HTTP sites as "Not secure" in July 2018. 🔐⚠️
security.googleblog.com/2018…
David Benjamin retweeted
Dear Lazy Twitter: does anyone have a contact at Fortinet (r.e. their TLS inspection)?
David Benjamin retweeted
Next steps: marking more HTTP pages as "not secure" in Chrome
blog.chromium.org/2017/04/ne… 🙌🔒
David Benjamin retweeted
TA17-075A: HTTPS Interception Weakens TLS Security bit.ly/2m4yUMc