You are not logged in.

#1 2024-02-16 11:21:12

gcb
Member
Registered: 2014-02-12
Posts: 157

systemd resolved.conf, LLMNR=no?

Should we default to `LLMNR=no` on the default `/etc/systemd/resolved.conf`?

I mean, we don't ship samba enabled by default, why should we enable netbios NS replacement?

It is weird to see unexpected open ports listening on all public interfaces.

Offline

#2 2024-02-16 13:56:33

seth
Member
Registered: 2012-09-03
Posts: 57,026

Re: systemd resolved.conf, LLMNR=no?

https://wiki.archlinux.org/title/Systemd-resolved#LLMNR

The board is the  wrong platform for this.
You'd file a bug at https://gitlab.archlinux.org/archlinux/ … d/-/issues but the reply is, likely, gonna be that the upstream defaults won't be changed and to file a bug at https://github.com/systemd/systemd/issues

But in terms of "TGN", archlinux should™ default to not shipping resolved itfp.

Offline

#3 2024-04-04 08:25:48

Brocellous
Member
Registered: 2017-11-27
Posts: 146

Re: systemd resolved.conf, LLMNR=no?

Systemd already has an open discussion to disable LLMNR by default : https://github.com/systemd/systemd/pull/28263. It will probably be disabled within a few releases.

LLMNR is used (almost) exclusively for single-label names in sd-resolved, so it's not really the disaster that it is on windows.

Offline

Board footer

Powered by FluxBB