Emily Stark

Trustworthy 🔑 transport 🚆 for Chrome. HTTPS, certs, encryption, security UX, software eng & mgmt. @estark.bsky.social. Opinions are my own. she/her

[Emily Stark @estark37]

I'm not checking this hellscape much anymore. Find me on 🦋 (estark at bsky dot social)

[Emily Stark @estark37]

@tqbf @dadrian this was also, apparently, the thought process of teachers in our school district. “Hey guys, should we do school the day after Halloween?” “Fuck no, let’s drink all night and let the parents deal with the kids’ Nov 1 sugar hangovers”

[Zhou (Joe) Li @lzcarl]

Wow, I appreciate @acm_ccs being frank about review ethics! #CCS

[Cryptoki @Cryptoki]

A proposed CA/Browser Forum ballot would radically shorten the max validity period of #TLS certificates over the next few years https://t.co/ZVaMxJ7Ddi

[Emily Stark @estark37]

@ericlaw @googlechrome Can you file a bug with cert please?

[Emily Stark @estark37]

@musalbas @distractedm1nd @ekr____ @taoeffect This was how the initial deployment of CT worked, but is no longer true for Chrome. SCTs are audited probabilistically.

[Emily Stark @estark37]

@distractedm1nd @ekr____ @taoeffect And the way Chrome has implemented SCT auditing means that all Chrome clients "see" the same tree head; in other words, a log can't target individual Chrome clients with a split-view.

[Emily Stark @estark37]

@distractedm1nd @ekr____ @taoeffect I'm not going to dispute that CT has nuanced security guarantees (https://t.co/wpa0fdZ0UL), but the tweet you quoted is pointing out that there are, in fact, deployed forms of gossip in the wild. Also doesn't seem fair to ignore that Chrome does do (probabilistic) SCT auditing.

[Emily Stark @estark37]

@prdonahue @thedanigrant @GrantSlatton @ptrschmdtnlsn It's sometimes more trouble than it's worth for us to do non-deterministic behavior like this because it can be confusing/hard to debug. (user reports cert error, site operator can't reproduce)

[Emily Stark @estark37]

@prdonahue @thedanigrant @GrantSlatton @ptrschmdtnlsn I don't think we (on Chrome at least) have considered this for upcoming expired certs, but I think Google has done it for some server-side cert changes.

[Emily Stark @estark37]

@benadida The DRM angle is that it creates an ecosystem in which users are limited in the software and hardware they can use to create/edit content. You can strip off the metadata, sure, but then your content is no longer "legitimate". It's not literally DRM, but spiritually similar IMO.

[Emily Stark @estark37]

@benadida ... contains much less fraught solutions if the goal is for skilled analysts (rather than the mass consumer user base) to be able to distinguish. Like even just having the metadata in the image but not displaying it to end users would be preferable IMO.

[Emily Stark @estark37]

@benadida ... resources should go into flagging mis/disinformation, and/or giving nuanced context around questionable content, rather than affirmative indicators.

[Emily Stark @estark37]

@benadida I really try not to shoot things down without presenting an alternative, which I don't have. But I vaguely feel that technology is putting the cart way before the horse, solutions must be customized to the UI and user base of each social media platform, and the bulk of the...

[Bas Westerbaan @bwesterb]

It's a common misconception that we need to move from AES-128 to AES-256 to counter quantum attack. In this great talk @sejaques explains why, and shows a few new arguments why Grover's algorithm is even less practical than we already understood it to be. https://t.co/KZnHCnid6w

[Emily Stark @estark37]

Update: flights grounded due to an “IT issue” so I might, in fact, just be living in SFO forever, Crowdstrike-style

[Emily Stark @estark37]

I will be at TPAC this week! Planning to attend WebAppSec, WebAuthn, various breakouts, and the hallway.