https://bugzilla.suse.com/show_bug.cgi?id=1219920 https://bugzilla.suse.com/show_bug.cgi?id=1219920#c6 --- Comment #6 from Michal Filka <mfilka@suse.com> --- (In reply to Stefan Hundhammer from comment #5)
It will depend in how many places this validation is actually needed.
If it's only for this yast2-dns-server, we need to consider that it's already dropped for Factory / Tumbleweed and future products, supported only for the remaining life time of SLE-15 SPx and Leap 15.x.
yes, depends on PMs how much do we want to bring "new" features into those products. However, they are still going to be here with us for 10 years or so.
Since during all the time until just now nobody asked for this, it can't be that important, so we probably shouldn't invest too much into it.
well ... nobody asked for that bcs there still were "less secure ways" how to configure your system available. Might be that huge players are stripping these ways off. (i don't know just guessing)
If we also need it for many other networking-related YaST modules, that's different; but only if it's about creating NEW domain names, not connect to an existing one. If you need to use an existing domain with such a name, you don't have much choice. But if you are creating a new one, that's different.
hostname validation is part of core library (yast2.rpm) and hostname validation is used at several places. However, DNS records are validated at one place only (AFAIK; and this is a change for particular DNS records not generic domains) - the dns server module. So, it should be an additional check in dns module only (if hostname validation fails, just check if it is valid '_' scenario or not) - no big deal at first view in my POV. But as usual, we have priorities in Agama now, so someone has to decide how much is needed and plan for this. -- You are receiving this mail because: You are on the CC list for the bug.