infosex.exchange <3
You are probably looking for the infosec.exchange Mastodon instance
This host is mostly for my random stuff, and in little part acts like a well-intentioned placeholder for the typosquatted domain.
Discoverability and Archiving
Currently I'm using this host for saving the items from my own feeds to the Wayback Machine and provide in-links for search engines. I hate that I have to do this, but the non-sense ideology of Mastodon pretty much ruined the search feature for Fediverse as a whole, and this wasn't changed by the fact that they owned their mistake and implemented search eventually.
Yes, I (or anyone else) could do similar things with other peoples published feeds, regardless of the tantrum. No, you can't defederate this, because the process doesn't rely on an instance.
Gluttony Section for Search Engines
Reading the latest BLASTPASS writeup I can only wonder how many engineer hours must have gone into this thing. Incredible stuff!
@osxreverser Nah, they'll just wait until someone adds them to the group :P
Napalm Death is like fine wine, but with napalm.
Anybody knows what Asimov is in MS lingo? :)
@kaoudis I have plenty of experience with technically competent people messing up 1) risk assessment 2) communication, so I'd write this off as incompetence, but that should be called out too (esp. since based on the latest post they seem to think they've done everything right).
Tuesday's cryptic message about atop turns out to be a local memory corruption issue, but details are unclear:
https://www.openwall.com/lists/oss-security/2025/03/26/2What is clear to me is that the original "warning" was a shameful example of spreading FUD...
CVE-2025-31160 was issued to track the problem.
@nixfreak no and tbf I don't really want to provide support for some half-baked stuff, so please just stick to upstream until x64 support gets merged or maybe comment on the relevant PR's if you think you found a bug in them (#97 tracks x64 support).
Next Page