Ancestors

Toot

Written by warthog9 on 2025-01-13 at 04:12

glares

https://www.home-assistant.io/more-info/unsupported/systemd_resolved

No. No systemd-resolved IS NOT THE SOLUTION

good freaking grief, it's caused me so much stupid of late it's almost as bad as systemd-timesyncd.

sighs

I don't mind the idea of having frameworks, but I sure as heck have problems with assuming they know what's what and then introducing something that breaks so hard it's a mess.

[#]HomeAssistant #HASS

=> More informations about this toot | More toots from warthog9@social.afront.org

Descendants

Written by zl2tod on 2025-01-13 at 04:15

@warthog9

Is there anything that differentiates systemd from a rootkit?

=> More informations about this toot | More toots from zl2tod@mastodon.online

Written by Yet another Josh :donor: on 2025-01-13 at 14:53

@warthog9

This whole relying on systemd for damn near everything is kind of terrible.

I had a really cool toolchain to enable .onion resolution across a linux system. It permitted any program to communicate across the clear web OR to .onion tor URLs using tor, without using proxies that shove all your data one way or the other.

https://cdn.hackaday.io/files/12985555550240/Linux%20DNS%20Resolver%20for%20Onions.txt

That doesnt work any more with systemd crap.

=> More informations about this toot | More toots from crankylinuxuser@infosec.exchange

Written by warthog9 on 2025-01-13 at 17:48

@crankylinuxuser i mean "you need a local resolver" is a fine statement: bind, dnsmasq, heck even unbound (not my favorite for other reasons) work just fine here.

• Sighs*

=> More informations about this toot | More toots from warthog9@social.afront.org

Written by Yet another Josh :donor: on 2025-01-13 at 17:50

@warthog9

Yeah, it's "fine" until systemd stomps all over the local resolver.

Which it does EVERY DAMNED TIME.

Its systemd or the highway every time. If they didn't think of it to implement and you know, document, then it doesn't exist.

=> More informations about this toot | More toots from crankylinuxuser@infosec.exchange