https://bugs.kde.org/show_bug.cgi?id=395419
--- Comment #7 from Ardith Metz <itgvk...@grr.la> --- (In reply to David Edmundson from comment #6) > >It's worth noting that adding -nolisten options from the compositor doesn't > >work, because if that option isn't available (e.g. '-nolisten tcp6' when > >you've built without IPv6 support), failure to not listen will be a hard > >error. > > From Daniel Stone. > > So we're definitely not doing that. > > I will monitor that upstream thread. Please do not reopen it here. Option '-nolisten tcp6' doesn't even exist, it should be '-nolisten inet6' but I'm not advising to use it. Option '-nolisten tcp' will work always - it disables both ipv4/ipv6 and doesn't fail hard when ipv6 isn't available (see 'man xserver' for valid options). Actually kwin_wayland hard fails currently when ipv6 isn't available (just boot with 'ipv6.disable=1' kernel arg to test) so we have exactly opposite situation of what you quoted[1]. To conclude we have both: potential security issue and crash and you closing them both and pointing to upstream while upstream points to you while there is no sign they will address it in any way. [1] https://bugs.kde.org/show_bug.cgi?id=394431 -- You are receiving this mail because: You are watching all bug changes.
