Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: RonB <ronb02NOSPAM@gmail.com>
Newsgroups: comp.os.linux.advocacy
Subject: Re: Lunduke's video on this latest issue
Date: Sun, 29 Sep 2024 17:44:40 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <vdc3m7$1qkcp$4@dont-email.me>
References: <%5mJO.22860$MxR.7503@fx47.iad> <vd5chg$jdi1$6@dont-email.me>
 <hVxJO.220449$FzW1.41428@fx14.iad> <vd7eib$tcgq$4@dont-email.me>
 <eeSJO.387625$_o_3.269231@fx17.iad> <llr0nhFm711U1@mid.individual.net>
 <1BaKO.165120$EEm7.8010@fx16.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 29 Sep 2024 19:44:40 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="ada1a2d3795a5818b0bdc3fcf2b63556";
	logging-data="1921433"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19FnSzMZ/Ge7eAxjlSdKU4u"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:vHeIbiolOzzUicX7ynWbWvo9G0o=
Bytes: 2988

On 2024-09-29, CrudeSausage <crude@sausa.ge> wrote:
> On 2024-09-28 2:37 p.m., rbowman wrote:
>> On Sat, 28 Sep 2024 08:01:14 -0400, CrudeSausage wrote:
>> 
>>> Like I said, I'm happy to see that the solution is as simple as it is
>>> and that it doesn't affect printing as much as I expected that it would.
>>> When the problem was revealed, it truly sounded like the fix would be
>>> worse than the problem.
>> 
>> I don't know if it is a fix but I noticed cups-browsed and other cups
>> files were in the Fedora 40 update I did last night.
>
> That would be interesting since the article suggested that developers 
> have been looking for a solution for weeks and been unable to find one. 
> All the better if they've figured something out. Seriously though, if it 
> is possible to simply disable cups-browsed without compromising 
> functionality, why even make a big deal out of this? They seem to have 
> made it sound much worse than it actually is.

The reason to make a "big deal out of it" is that it is a potential security 
risk for those with their UDP 631 ports exposed to the Internet and who are 
using cups-browsed. Just for the sake of safety I've uninstalled 
cups-browsed on my computers, but I'm pretty sure I don't have my UDP 631 
port opened to the world. I think this is mostly an issue for companies and 
corporations who do remote printing (which I'm guessing isn't that common 
anymore, but I don't know for sure because I don't work in that 
environment).

When they say they've been trying to find a solution for weeks, I think it 
means for those who still need the cups-browsed feature. For most of the 
Linux world the fix is easy (or not necessary).

-- 
“Evil is not able to create anything new, it can only distort and destroy 
what has been invented or made by the forces of good.”  —J.R.R. Tolkien