I'm working on a small #debian package to provide basics to assist in #security #hardening a current debian installation.

"Conflicts" with dangerous/problematic packages. Docs with hints or config steps. Predefined settings for known issues/vulns. Something that is both a guide and provides automatic assistance and prework and prescription where possible. (E.g. lists of modules for use with kernel.modules_disabled=1)

I'd be interested to hear what else one would expect from such a package.

Soo .. what if we set up a TLD for families (in general), have each family of today register a name, then have each child register a subdomain for their prospective family, have each grandchild register a subsubdomain for their family, and so on. You'd create a family-tree-domain-system. Names would get pretty impressive.

Only downside: it'll be sparse and deep, which is rather counter-functional to DNS.

Organized coordinated #workplace #harrassment and #abuse at #ASML.

https://mastodon.social/@cobratbq/115895322248283999

The other side of the coin: https://dannyvanheumen.nl/post/harassment-asml-first-team-team-architect-conflicts/

My other account is blocked on several instances.

#softwareengineer #softwarearchitect #engineering