rivitheadz.bsky.social
Software/Systems Engineer | 🏔️ Mountain climber Denver, Colorado & Kyiv, Ukraine
👤 Joined on 18 Oktober 2024
Followers
Following
Total Posts
@rivitheadz.bsky.social@rivitheadz.bsky.social → @nitrojaguaruebdj.bsky.social@nitrojaguaruebdj.bsky.social → @rivitheadz.bsky.socialursinhofazraw.bsky.social
Not Found
pryvid-opery.bsky.social
aprilhuggettua.bsky.social
foyrees.bsky.social
ladyvaldivia.bsky.social
jienafo.bsky.social
mehdirhasan.bsky.social
Not Found
jdkahler.bsky.social
Not Found
Not Found
conk54.bsky.social
rahaeli.bsky.social
paco-taco.bsky.social
Not Found
Not Found
Not Found
askylitocean.bsky.social
Not Found
alvylad.bsky.social
Not Found
jim-stewartson.bsky.social
Not Found
Not Found
There are very good reasons for not conflating publishing Trust Anchors and publishing security policy.
Show PostAnyone who knew the DNS business at the time, knew that the registrars sold DNS names at cost hoping to upsell Web hosting. But most of their money came from CA affiliate deals reselling TLS certs. So the DANE proposal effectively killed DNSSEC deployment.
Show PostWhat we should have done is to use DNS optionally backed by DNSSEC to publish the security policy (must use TLS, must be via this anchor). Which I tried to do with CAA, then the DANE people insisted on doing it their way and made it undeployable.
Show PostCertificate pinning ultimately proved largely unworkable on the web, but it is unfortunate and we did try like in HPKP. Pinning is used in many software update mechanisms, however it's spotty.
Show PostThe first guy to discover you can just have sex with men, talking on his podcast: "I just don't see how women come back from this."
Show Post