I’ve been subscribed to Brian Krebs’ blog for twelve years (started during his time at The Washington Post), but I guess it’s time to let go. Whatever important info he might have, it will show up elsewhere as well. His understanding of ethics seems more and more questionable.
> Thank you.
> Please don't feed the reporters who will stomp all over intel/jeopardize sources for their own gain.
> I can't stand Krebs.
Hey #Feedly, don’t you want to start using Referrer Policy on your website? Currently, when your users click a link you will typically leak their user ID and some info about how they organize their feeds via the Referer header. #privacy
“Edit (2020-10-28): As @firstname.lastname@example.org pointed out, extensions acquire this Verified badge by paying for the review. All the more interesting to learn what kind of review has been paid here.”
@calculsoberic Yes, there certainly are more extensions like this. But this one claims to have 17 million users, a claim that matches reported numbers in Mozilla Add-ons and Chrome Web Store…
I did not expect the #Honey browser extension to provide great privacy. Still, finding four (!) different mechanisms allowing the Honey server to run arbitrary code on any website exceeded my expectations by far. It even uses AES for obfuscation.
Software developer and security researcher, browser extensions expert. He/him
Other Mastodon account for non-technical topics: https://social.tchncs.de/@WPalant
A Mastodon instance for info/cyber security-minded people.