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

Me: Have you heard of Nvidia?
Her: Is that a salad?
this post | permalink
@hanno I'm pretty sure many people could get more work done today *because* Microsoft services were offline.
this post | permalink
Project of the day:

https://github.com/docker-mailserver/docker-mailserver

My impression is that mail services on Linux follow the Unix philosophy very strictly, making them very flexible, but also one of the hardest things to configure on a single system IME.

This is a nice use-case for containerization where you can package parts of userspace in a configuration that will fit 80% of the potential users with <10% of the administration complexity.

#selfhosted #email
this post | permalink
@dey You were wiser last night it seems :D
this post | permalink
@dey I don't even
this post | permalink
... on the bright side: memes are excellent these days!
this post | permalink
Based on past experience:

- A resignation won't burst a bubble
- A critical outage won't convince leaders that outsourced IT should be brought home

#thoughtleading
this post | permalink
@SecurityWriter they definitely have a quiet one...
this post | permalink
[RSS] JSON Schema References Considered Harmful

https://www.svix.com/blog/json-schema-external-entities/

While I kind of agree with the title, the article is mostly explaining how hitting their finger is the hammers fault. This is the gist:

"[Rust jsonschema] automatically (and, as of v0.21.0, eagerly) handles dereferencing $ref entries, including fetching arbitrary HTTP Resources and loading files off of disk if a file:/// URI is specified. If a resource doesn't include a valid JSON Schema document, the error message will include fragments of the affected document."

In other words jsonschema follows the spec, which they didn't read before implementing arbitrary schema upload+parsing.
this post | permalink
[RSS] How I Ended Up Turning a 22-Year-Old PostgreSQL Type-Confusion Primitive into RCE (CVE-2026-6460)

https://mehmetince.net/part-3-6-how-i-ended-up-turning-a-22-year-old-postgresql-type-confusion-primitive-into-rce-cve-2026-6460/
this post | permalink
Next Page