estark37 Profile Banner
Emily Stark Profile
Emily Stark

@estark37

Followers
10K
Following
4K
Media
206
Statuses
3K

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

San Francisco Bay Area
Joined November 2010
Don't wanna be here? Send us removal request.
@estark37
Emily Stark
1 year
I'm not checking this hellscape much anymore. Find me on 🦋 (estark at bsky dot social)
0
1
6
@lzcarl
Zhou (Joe) Li
1 year
Wow, I appreciate @acm_ccs being frank about review ethics! #CCS
7
53
180
@bwesterb
Bas Westerbaan
1 year
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.
0
18
50
@estark37
Emily Stark
1 year
Update: flights grounded due to an “IT issue” so I might, in fact, just be living in SFO forever, Crowdstrike-style
0
0
5
@estark37
Emily Stark
1 year
I will be at TPAC this week! Planning to attend WebAppSec, WebAuthn, various breakouts, and the hallway.
1
0
11
@editingemily
emily freeman
1 year
I will die on the hill that RTO hurts families with young children the most — and mothers above all when mom is still the default caregiver. Don’t make people choose between their kids and their careers.
112
217
2K
@estark37
Emily Stark
1 year
(It does have security benefits, and they will increase over time as things evolve! But creating a passkey doesn't currently instantly make your account unphishable, for example.)
3
0
3
@estark37
Emily Stark
1 year
This means that creating passkeys doesn't harm availability of your account. It also means that creating a passkey might not have all the security benefits that one would like.
2
0
4
@estark37
Emily Stark
1 year
PSA: creating a passkey for a website does not imply that you can no longer log in with a password
2
3
23
@estark37
Emily Stark
1 year
Great comment from @arturjanc on why Content Security Policy is not a good tool for preventing untrusted code from exfiltrating sensitive data:
Tweet card summary image
github.com
CSP currently has a few gaps that prevent it from being a useful anti-exfiltration mechanism. https://www.w3.org/TR/CSP3/#exfiltration hints that preventing data exfiltration may be a goal, but it&...
1
4
20
@JoelWBerry
Joel Berry
1 year
When your 2-year-old starts correctly pronouncing a word she’s been adorably mispronouncing her whole life and you realize that little nonsense word is gone forever
713
2K
36K
@estark37
Emily Stark
2 years
Several years ago I complained that https://t.co/GEBztHXCZB doesn't use HTTPS. It still doesn't, but at least the complaint now exists in blog post form:
emilymstark.com
This blog post is an expanded version of a Twitter thread I posted several years ago about why every website should use HTTPS. Twitter seems less… readily citable these days, so I thought it would be...
@estark37
Emily Stark
4 years
1/ TIL that one of my most favorite websites, https://t.co/GEBztIfdR9, doesn't support HTTPS. That means it's time for a rant about why HTTPS is important even for a static website that serves no purpose but to let you copy-paste your favorite emoticon. đź§µ
3
4
20
@JoeBeOne
Joseph Lorenzo Hall, PhD
2 years
you have to read and write a lot; there are no shortcuts
0
4
14
@estark37
Emily Stark
2 years
Kudos to @davidcadrian @davidben__ @ryancdickson @modyoloN, Bob Beck, Chris Clements, and the rest of the team
0
0
4
@estark37
Emily Stark
2 years
My team has been BUSY! Highlights from this lovely Friday morning: - Postquantum TLS strategy: https://t.co/2vRbLYEMTJ - Distrusting CAs w/out breaking existing certs: https://t.co/EpNnnQB5XN - Updated draft of Trust Expressions for TLS cert negotiation:
Tweet card summary image
blog.chromium.org
Google and many other organizations, such as NIST , IETF , and NSA , believe that migrating to post-quantum cryptography is important due...
1
15
48
@rmhrisk
Ryan Hurst
2 years
There is a new draft for Trust Expressions. It is trying to address the real-world complexity of TLS deployment by making the ubiquity problem of root certificates manageable it does this by enabling relying parties to succinctly convey which certification authorities they trust.
1
4
8
@davidcadrian
David Adrian
2 years
Following up with some thoughts on how to think about migrating HTTPS to post-quantum cryptography. It's similar to the HTTPS adoption effort, but not quite the same because lack of post-quantum security is not the same thing as plaintext. https://t.co/2symnzslHt
Tweet card summary image
dadrian.io
HTTPS adoption in 2024 is around 95-98%, as measured by page loads in Chrome (it would be better if it was 100%!). These days, a plaintext HTTP site is a rarity, enough that many users of Chrome’s...
@davidcadrian
David Adrian
2 years
With Real World Cryptography coming up next week, I wanted to take an opportunity to point out that our current post-quantum cryptographic primitives are not suitable for the web
0
2
5