Path: ...!feeds.phibee-telecom.net!news.mixmin.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.advocacy
Subject: Re: Lunduke's video on this latest issue
Date: 27 Sep 2024 02:00:10 GMT
Lines: 22
Message-ID: <llmhtaF18kdU4@mid.individual.net>
References: <%5mJO.22860$MxR.7503@fx47.iad>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net /UQCygugegH5P21Xct+5rAFBR6463w/JWJC+oURBKxHanmIi8Y
Cancel-Lock: sha1:ZYVu4IEhHG8ZwGmFz+/xiy0tccw= sha256:olTCCTMgTZ7f+QiaCzE+XBVjsQ9OfQFN/k+9cOoAa2E=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 1382

On Thu, 26 Sep 2024 19:27:50 -0400, CrudeSausage wrote:

> Spoiler: you're going to need to remove pretty much everything that has
> to do with CUPS and never print from a UNIX machine ever again to fix
> this.
> 
> <https://lunduke.locals.com/upost/6159931/the-9-9-linux-vulnerability-
revealed-its-the-printers>

On Ubuntu cios is a snap package so you need 

sudo snap stop cups
sudo snap disable cups

I still had to run

sudo systemctl stop cups

to get rid of cupsd. cups.cups-browsed wasn't running on the Fedora box 
and systemctl got rid of cupsd. I print something every other year so I 
don't see a downside.