In a new Q&A, Philip Bump, columnist for The Washington Post, reflects on why archiving the news goes beyond saving stories. From holding leaders accountable to capturing moments in culture, Bump shares insights on the need to preserve digital media. #VanishingCulture
đź”— https://blog.archive.org/2024/11/04/vanishing-culture-qa-with-philip-bump-the-washington-post/
Don’t miss out—RE//verse tickets are on sale now! https://shop.binary.ninja/products/re-verse
Announcement: ph0wn registration is opening today at 2pm!
The Ph0wn/Pico fan shop is already open. You'll find there hoodies, t-shirts, bags and many other items with or without @picolecroco . All items are sold at cost price and there's a 25% discount for 10 days.
Wear your item on the day of ph0wn!
I have written a copyleft #chiptune and #lofi album for the upcoming Radare2 conference: https://rada.re/con/2024/
Enjoy!
Hotdog or not hotdog?? đźŚ
Let's take a look into a machine learning app that can detect hotdogs. How does it work? Can we change it into a pizza detector 🍕 app?
https://youtu.be/e2kosWm2vag
#reverseengineering #reversingshorts
🔥💀After 40 hours of constant reversing of weird looking c++ and no sleep, I Finally cooked the
CVE-2024-47575 fortimanager unauthenticated RCE 🩸
Code auditing is not the same as vulnerability research
https://pacibsp.github.io/2024/code-auditing-is-not-the-same-as-vulnerability-research.html
@sha1lan I see the two as very similar activities, but as you say with different goals and outputs.
I think what I would call code auditing is closer to what you would call vulnerability research. One example you gave was of a highly vulnerable library used to process static content. If I am reviewing a product or feature I will do my best to avoid ever reporting something like that, because it’s not actually vulnerable to anything. That’s not to say I am perfect as sometimes time constraints and complexity can lead to a useless report, but I do what I can under the circumstances. I might just be nitpicking that specific example. :)
I wrote about a slightly different framing of this a few months back: https://nickg.ca/posts/economics-of-proving-exploitability/
I see the difference as depth vs breadth. Depth provides stronger evidence of exploitability at the expense of breadth. Breadth provides a higher quantity of dangerous looking code or at the expense of possibly useless findings.
Anyway any differences I have with it are quite minor. I think I like it so much because it’s very focused on the customer goals instead of my focus on the activities I would take to meet those goals.
I love how this looks like they’re having a conversation.
Stop thinking of Twitter, TikTok, IG, (et al) as social media sites.
They are **Content Refineries.**
Like processed food manufacturers they take user content & extract the most addicting/engaging content. Brains eat it up but in an unhealthy “devour the whole bag of chips” way.
They make hyper-processed social media junk food.
Mastodon is more like a potluck. We're all bringing dishes. It's a mess. Kids are running all over. But we are, at least, real people sharing real things.
Finally achieved empty tcpdump starting Firefox. Had to find and clear location.services.mozilla.com and push.services.mozilla.com from show-all in about:config. Then there were the following that are hard-coded, not appearing in about:config, for which /etc/hosts needed to be invoked:
firefox.settings.services.mozilla.com content-signature-2.cdn.mozilla.net prod.remote-settings.prod.webservices.mozgcp.net content-signature-chains.prod.autograph.services.mozaws.net
FFS do better.