Re: Package grub-xen-host breaks PV domains with 11.5 point release

[David Wright]

On Mon 12 Sep 2022 at 01:15:47 (+0200), Tom Lew wrote:
> This is my first post, bear with me..
> 
> Package "grub-xen-host" shipped with point release 11.5 broke all PV
> domains on my Xen server, after "apt upgrade" from 11.4.
> 
> I found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944
> exactly mirroring my situation, and I wonder whether this can be fixed
> for other users in any (fast) way, upfront other users doing apt
> upgrade on their Xen hosts?
> 
> My workaround for this ATM: install and pin previous grub-xen-host
> (grub-xen-host_2.04-20_amd64.deb, grub-xen-bin_2.04-20_amd64.deb,
> grub-common_2.04-20_amd64.deb). Probably the wrong way to fix it, but
> works for me so far(TM).
> 
> In case this should be reported or added to something somewhere,
> please let me (a Debian bug reporting newbie) know.

I would imagine a fix could follow quite quickly as it only requires
rebuilding with a filename added to a list of files not to have
their symbols stripped (or reverting the compatibility level change).

AFAICT apt-listbugs would have reported this to you before
the upgrade of grub-xen-host took place, as someone had reported
it on 22 Aug. So it might be worth installing apt-listbugs.

Cheers,
David.

Re: Should a serious bug have made in into bullseye 11.5?

[David Wright]

On Mon 12 Sep 2022 at 03:36:46 (+0100), Tim Woodall wrote:
> On Sun, 11 Sep 2022, Greg Wooledge wrote:
> > On Sun, Sep 11, 2022 at 09:23:17PM +0100, Tim Woodall wrote:
> > > Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
> > > made it into debian 11.5? I thought serious bugs shouldn't make it into
> > > stable?
> > 
> > Bugs have to be discovered and reported.  If nobody found this during
> > the bullseye testing cycle, then it's quite likely bullseye would ship
> > with this bug.
> > 
> > I note that the bug report was reported August 22, 2022, over one year
> > after the bullseye release.  Maybe this package just doesn't have many
> > users, or the bug didn't affect most of its users.
> > 
> > 
> The buggy package was added to bullseye with the 11.5 point release on
> 2022-09-10. It wasn't present in 11.4 whose version of this package
> worked. It was added to proposed-updates on 2022-08-06.
> 
> Based on the comments in thw bug it looks like the breakage was due to
> the changing to use debhelper 13 instead of 10.

One way to read this is that a misfeature had been in grub-xen-host
since very early on. If it relies on not stripping the symbols from
any files, then those files' names should really have been placed
in the exception list that gets handed to dh_strip:

  -Xitem, --exclude=item
Exclude files that contain item anywhere in their filename from
being stripped. You may use this option multiple times to build up
a list of things to exclude.

As it was, there's was reliance on debhelper's guesswork, something
that had been reported as poor in 1999 (#35733), and improved in 2017
(protected by compatibility level 10).

It's beyond me to work out exactly when compatibility 10 becomes
deprecated, how strong deprecation actually is, what pressure
there is to increase the level in grub-xen-host, and why its level
had fallen so far behind.

Cheers,
David.

Re: Package grub-xen-host breaks PV domains with 11.5 point release

[Tim Woodall]

On Mon, 12 Sep 2022, Tom Lew wrote:


This is my first post, bear with me..

Package "grub-xen-host" shipped with point release 11.5 broke all PV domains 
on my Xen server, after "apt upgrade" from 11.4.


I found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 exactly 
mirroring my situation, and I wonder whether this can be fixed for other 
users in any (fast) way, upfront other users doing apt upgrade on their Xen 
hosts?


My workaround for this ATM: install and pin previous grub-xen-host 
(grub-xen-host_2.04-20_amd64.deb, grub-xen-bin_2.04-20_amd64.deb, 
grub-common_2.04-20_amd64.deb). Probably the wrong way to fix it, but works 
for me so far(TM).


In case this should be reported or added to something somewhere, please let 
me (a Debian bug reporting newbie) know.



Snap. See "Should a serious bug have made in into bullseye 11.5?"

Re: Should a serious bug have made in into bullseye 11.5?

[Tim Woodall]

On Sun, 11 Sep 2022, Greg Wooledge wrote:


On Sun, Sep 11, 2022 at 09:23:17PM +0100, Tim Woodall wrote:

Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
made it into debian 11.5? I thought serious bugs shouldn't make it into
stable?


Bugs have to be discovered and reported.  If nobody found this during
the bullseye testing cycle, then it's quite likely bullseye would ship
with this bug.

I note that the bug report was reported August 22, 2022, over one year
after the bullseye release.  Maybe this package just doesn't have many
users, or the bug didn't affect most of its users.



The buggy package was added to bullseye with the 11.5 point release on
2022-09-10. It wasn't present in 11.4 whose version of this package
worked. It was added to proposed-updates on 2022-08-06.

Based on the comments in thw bug it looks like the breakage was due to
the changing to use debhelper 13 instead of 10.

Re: Download links do not work

[Kevin Price]

Am 12.09.22 um 01:09 schrieb Tom Zarcone:
> Debian.org/download does not work. Not a single link works.

So double-check https://www.debian.org/download again.

All it says is “unable to connect”. I get this issue on every browser I use

Do you happen to be in a country whose government restricts Internet access?

Your IPv4 address 17.58.6.50 is allocated to Apple Inc.
-- 
Kevin

Re: Download links do not work

[The Wanderer]

On 2022-09-11 at 19:09, Tom Zarcone wrote:

> Debian.org/download does not work. Not a single link works. All it
> says is “unable to connect”. I get this issue on every browser I use

Works flawlessly for me, with all of Firefox, w3m, and wget.
(https://debian.org/download redirects to
https://www.debian.org/download , and the HTTP version redirects to that
same HTTP destination, but that shouldn't affect the result.)

What IP address are you getting for the site? I get:

$ host debian.org
debian.org has address 128.31.0.62
debian.org has address 130.89.148.77
debian.org has address 149.20.4.15
debian.org has IPv6 address 2603:400a::bb8::801f:3e
debian.org has IPv6 address 2001:67c:2564:a119::77
debian.org has IPv6 address 2001:4f8:1:c::15
debian.org mail is handled by 0 mailly.debian.org.
debian.org mail is handled by 0 muffat.debian.org.
debian.org mail is handled by 0 mitropoulos.debian.org.

$ host www.debian.org
www.debian.org has address 149.20.4.15
www.debian.org has address 128.31.0.62
www.debian.org has IPv6 address 2603:400a::bb8::801f:3e
www.debian.org has IPv6 address 2001:4f8:1:c::15

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Download links do not work

[Tom Zarcone]

Debian.org/download does not work. Not a single link works. All it says is 
“unable to connect”. I get this issue on every browser I use

Package grub-xen-host breaks PV domains with 11.5 point release

[Tom Lew]

This is my first post, bear with me..

Package "grub-xen-host" shipped with point release 11.5 broke all PV 
domains on my Xen server, after "apt upgrade" from 11.4.


I found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 
exactly mirroring my situation, and I wonder whether this can be fixed 
for other users in any (fast) way, upfront other users doing apt upgrade 
on their Xen hosts?


My workaround for this ATM: install and pin previous grub-xen-host 
(grub-xen-host_2.04-20_amd64.deb, grub-xen-bin_2.04-20_amd64.deb, 
grub-common_2.04-20_amd64.deb). Probably the wrong way to fix it, but 
works for me so far(TM).


In case this should be reported or added to something somewhere, please 
let me (a Debian bug reporting newbie) know.


Thanks
Tom

Re: fetchmail

[Gerard ROBIN]

Le Sun, Sep 11, 2022 at 09:24:27AM -0400, Greg Wooledge a écrit :
> Date: Sun, 11 Sep 2022 09:24:27 -0400
> From: Greg Wooledge 
> To: debian-user@lists.debian.org
> Subject: Re: fetchmail
> X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on bendel.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-7.7 required=4.0
>  tests=LDOSUBSCRIBER,LDO_WHITELIST, ONEWORD,RDNS_NONE,T_SCC_BODY_TEXT_LINE
>  autolearn=unavailable autolearn_force=no version=3.4.2
> 
> On Sun, Sep 11, 2022 at 12:14:15PM +0200, Gerard ROBIN wrote:
> > My problem is that I don't know what starts it.
> > [...]
> > Debian Bookworm (and Bullseye too) use systemd.
> 
> It's too late now, because you already "solved" the problem by purging
> and reinstalling the package.  (Which is not a bad solution -- just not
> one that enlightens.)

Thank you for your reply. reinstalling fetchmail is not the solution
because on the next start the problem comes back and (I must be stupid)
because despite all the ideas you give me I cannot kill the background
process of fetchmail.
The solution: purge fetchmail and install getmail6.
Getmail6 works well, without complications.

Thanks again.

Gerard


Created with Mutt  2.2.6-1
under Debian Linux BOOKWORM

Re: Should a serious bug have made in into bullseye 11.5?

[Greg Wooledge]

On Sun, Sep 11, 2022 at 09:23:17PM +0100, Tim Woodall wrote:
> Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
> made it into debian 11.5? I thought serious bugs shouldn't make it into
> stable?

Bugs have to be discovered and reported.  If nobody found this during
the bullseye testing cycle, then it's quite likely bullseye would ship
with this bug.

I note that the bug report was reported August 22, 2022, over one year
after the bullseye release.  Maybe this package just doesn't have many
users, or the bug didn't affect most of its users.

Printer pauses a few seconds between each page

[Yvan Masson]

Hi,

My printer is an (old) Epson EPL-6200, USB connected. When I print from 
my Debian laptop a multiple pages document, it pauses a few seconds 
between each page. It looks like there is one print job per page.


Another user of this printer, also running Debian and who experiments 
the same behavior, told me that *once* it printed a 5 pages document all 
at once, but it was a PDF printed from Evince whereas most of the time 
we print from LibreOffice.


I don’t know where I should look, CUPS is still a thing I do not really 
understand. Do you know/guess the reason of this behavior? Can it be 
changed?


You will find attached the PPD I use.

Thanks,
Yvan


EPL-6200.ppd
Description: application/vnd.cups-ppd


OpenPGP_signature
Description: OpenPGP digital signature

Should a serious bug have made in into bullseye 11.5?

[Tim Woodall]

Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
made it into debian 11.5? I thought serious bugs shouldn't make it into
stable?

I'm not sure this should be merely serious, it broke absolutely
everything for me and took me a while to track down.

Although the 'fix' was just to pin the package and downgrade, I ended up
resorting to backups because I had no dhcp, no dns after rebooting.

I wonder how many people have picked this up but not yet realized that
they cannot start new domU other than HVM.

Tim.

Re: Google Chrome can share but Chromium cannot share screen

[Pankaj Jangid]

Corentin Bardet  writes:

> I think you have no other option than using Google Chrome for your
> meetings.

Screen sharing works in Firefox ESR on Wayland. So I still have
options. Just that few features - like blur background etc. doesn't
work in FF.

Re: fetchmail

[David]

On Sun, 11 Sept 2022 at 23:25, Greg Wooledge  wrote:
> On Sun, Sep 11, 2022 at 12:14:15PM +0200, Gerard ROBIN wrote:

> > My problem is that I don't know what starts it.

> > Debian Bookworm (and Bullseye too) use systemd.

> Guessing the service name is non-trivial.  Sometimes it's the same as
> the package name, and sometimes it's the same as the name of the program
> inside the package.

> If it's not either of those, then you can try grepping the list of files
> contained in the package, thus:

> unicorn:~$ dpkg -L openssh-server | grep 'systemd.*service$'
> /lib/systemd/system/ssh.service
> /lib/systemd/system/ssh@.service

There's also:

$ systemctl list-units | grep ssh
  ssh.service  loaded active running   OpenBSD Secure Shell server

and

$ systemctl list-unit-files | grep ssh
ssh.serviceenabled enabled
ssh@.service   static  -
sshd.service   alias   -
ssh.socket disabledenabled
rescue-ssh.target  static  -
$

Re: fetchmail

[Greg Wooledge]

On Sun, Sep 11, 2022 at 12:14:15PM +0200, Gerard ROBIN wrote:
> My problem is that I don't know what starts it.
> [...]
> Debian Bookworm (and Bullseye too) use systemd.

It's too late now, because you already "solved" the problem by purging
and reinstalling the package.  (Which is not a bad solution -- just not
one that enlightens.)

Next time something like this happens, try to guess its service name,
and then start with:

systemctl status servicename

Guessing the service name is non-trivial.  Sometimes it's the same as
the package name, and sometimes it's the same as the name of the program
inside the package.

If it's not either of those, then you can try grepping the list of files
contained in the package, thus:

unicorn:~$ dpkg -L openssh-server | grep 'systemd.*service$'
/lib/systemd/system/ssh.service
/lib/systemd/system/ssh@.service

"So the service name for the sshd daemon in the openssh-server package
is neither openssh-server nor sshd, but instead, ssh!  Brilliant!"

You can also try looking through the contents of /lib/systemd/system/
either manually, or with globs or regular expressions, to try to figure
it out.

Anyway, once you've guessed the service name, systemctl status will
often give you some hints about what's happening.  It may also contain
a small number of journal (logfile) lines.  You can get more of those
lines by running "journalctl -u servicename".

Earlier in this thread, Nate posted the following output:

> $ systemctl status fetchmail.service 
> ● fetchmail.service - LSB: init-Script for system wide fetchmail daemon
>  Loaded: loaded (/etc/init.d/fetchmail; generated)
>  Active: active (exited) since Sat 2022-09-10 15:37:33 CDT; 52min ago
>Docs: man:systemd-sysv-generator(8)
> Process: 1790 ExecStart=/etc/init.d/fetchmail start (code=exited, 
> status=0/SUCCESS)
> CPU: 6ms

That's from .

Note that this particular package doesn't actually *have* a systemd
service file.  One is "generated" on the fly, which simply runs the
sysv-rc script /etc/init.d/fetchmail.

Debugging problems with a sysv-rc start script is going to be a lot
more difficult, because they are inherently much more complicated.  But
you can try a few things:

1) sysv-rc scripts are often configured by files in /etc/default/.  Look
   for a config file there, and see if it looks sensible.  It might
   contain comments; if so, read them.  They are often helpful hints or
   instructions for how the service can be configured.

2) You can try reading the init.d shell script itself, if you're fluent
   in shell.

3) You can try running the init.d shell script directly, with trace mode
   turned on, e.g. "sh -x /etc/init.d/foobar start".  See where it blows
   up, if it is in fact blowing up.

   Of course, in your case, your grievance was that the service *wasn't*
   blowing up.  It was successfully starting and running, and that's
   what you didn't want.  So it would more likely be a configuration
   issue, not a problem that sh -x is going to help you pinpoint.

   Nevertheless, in other scenarios, where you *want* a service to run and
   it's not running, this is sometimes useful.

Re: Installing Wi-Fi card driver

[john doe]

On 9/11/2022 1:16 PM, Timothy M Butterworth wrote:

On Sun, Sep 11, 2022 at 5:11 AM Mansour zermello  wrote:


Hi Timothy, i appreciate too much your response, but i already installed
the debian OS, but install the driver of the wifi card that still blur for
me to be honest, i really need to be guided step by step I'm sure I'll
finish by doing it, my wifi car is the : intel 8265NGW

Do you have any working network cards? If you do, you can try this.


sudo nano /etc/apt/sources.list

deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free



Or in your '/etc/apt/sources.list', you can add on eatch line and after
'main' 'non-free contrib'.


Save Changes "Control+O" , exit Control+X

sudo apt update
sudo apt install firmware-linux-nonfree



You might want to restart/reboot after having installed the firmwares.

Note that you might need to add extra firmware, you will need to look at
the log to see what FW you require.

--
John Doe

Re: Google Chrome can share but Chromium cannot share screen

[Steve Litt]

On Sun, 2022-09-11 at 10:26 +0200, Corentin Bardet wrote:
> Hi,
> 
> Le 2022-09-11 07:39, Pankaj Jangid a écrit :
> > For a few work related meetings, I have to use Google Meet. But the
> > screensharing doesn't work in the Chromium installed from stable APT
> > repository. Clicking on the share-screen icon and then selecting any of
> > the three options - Tab, Windows, Entire Screen - shows this error
> > message,
> > 
> > "Your browser can't share your screen"
> > 
> > But if I install and use Google Chrome, then the screen sharing works 
> > in
> > Google Meet.
> 
> That doesn't surprise me much.
> 
> Google removed the majority of its APIs from Chromium : 
> [here](
> https://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrom
> e) 
> and 
> [here](https://www.omgubuntu.co.uk/2021/01/chromium-sync-google-api-removed)
> 
> Maybe screen sharing was a Google thing. Especially screen sharing to 
> Google Meet.
> 
> I think you have no other option than using Google Chrome for your 
> meetings.

O r   u s e   J i t s i ! 

SteveT

Re: Installing Wi-Fi card driver

[Timothy M Butterworth]

On Sun, Sep 11, 2022 at 5:11 AM Mansour zermello  wrote:

> Hi Timothy, i appreciate too much your response, but i already installed
> the debian OS, but install the driver of the wifi card that still blur for
> me to be honest, i really need to be guided step by step I'm sure I'll
> finish by doing it, my wifi car is the : intel 8265NGW
>
> Do you have any working network cards? If you do, you can try this.

sudo nano /etc/apt/sources.list

deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free

Save Changes "Control+O" , exit Control+X

sudo apt update
sudo apt install firmware-linux-nonfree



>
>
> Sent from Yahoo Mail on Android
> 
>
> On Sat, Sep 10, 2022 at 23:59, Timothy M Butterworth
>  wrote:
>
>
> On Fri, Sep 9, 2022 at 8:48 AM Mansour zermello 
> wrote:
>
> Hi, I'm a new user in the Linux world especially debian, but i was
> interested by debian since very long time but one day I decided to install
> it and start to use it, i had difficulties to install it but with a lot of
> effort and searches i succeeded, BUT the problem where I'm stucked is the
> WIFI card ( i don't know at all how to do ) to be honest, i really need
> your help I'm sure I'll can to do it if you explain to me how to do step by
> step and I'll transfer this knowledge to other user who is in my case.
>
> I'm waiting for your response impatientely to start using debian certainly
> the best OS ever made.
>
> Have a nice day,
> Cordially
>
> Sent from Yahoo Mail on Android
> 
>
>
> If you are missing drivers or binary blobs for drivers the easiest way to
> fix it is to install with the non-free installer.
> https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: fetchmail

[Gerard ROBIN]

Le Sun, Sep 11, 2022 at 06:18:07AM +0200, to...@tuxteam.de a écrit :
> Date: Sun, 11 Sep 2022 06:18:07 +0200
> From: to...@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: fetchmail
> 
> On Sat, Sep 10, 2022 at 10:45:23PM +0200, Gerard ROBIN wrote:
> > Hello,
> > in Bullseye (stable) fetchmail works fine, but in Bookworm (testing) I
> > get:
> > 
> > fetchmail: can't accept options while a background fetchmail is running.
> > argc = 5, arg list:
> > arg 1 = "-k"
> > arg 2 = "--ssl"
> > arg 3 = "--mda"
> > arg 4 = "/usr/bin/procmail -d %T"
> > 
> > No mail arrived since 
> > 
> > ps ax | grep fetchmail
> > 
> > 1943 ?Ss 0:00 fetchmail --nodetach --daemon 300
> > 4220 pts/1S+ 0:00 grep fetchmail
> > 
> > how can i prevent the fetchmail daemon from running on startup in
> > Bookworm ?
> 
> What is starting it? What init system do you use?

My problem is that I don't know what starts it.
If I knew what started it I might be able to prevent it from starting.
I never had this problem with bullseye.
Debian Bookworm (and Bullseye too) use systemd.

Thanks.

-- 
Gerard
_
*
 Created with Mutt  2.0.5 
 under Debian Linux BULLSEYE
*

Re: Google Chrome can share but Chromium cannot share screen

[David]

On Sun, Sep 11, 2022 at 10:26, Corentin Bardet  
wrote:

Hi,

Le 2022-09-11 07:39, Pankaj Jangid a écrit :

For a few work related meetings, I have to use Google Meet. But the
screensharing doesn't work in the Chromium installed from stable APT
repository. Clicking on the share-screen icon and then selecting any 
of

the three options - Tab, Windows, Entire Screen - shows this error
message,

"Your browser can't share your screen"

But if I install and use Google Chrome, then the screen sharing 
works in

Google Meet.


That doesn't surprise me much.

Google removed the majority of its APIs from Chromium : 
[here]()#Differences_from_Google_Chrome) 
and 
[here]()


Maybe screen sharing was a Google thing. Especially screen sharing to 
Google Meet.


I think you have no other option than using Google Chrome for your 
meetings.


If that's truly the case, they don't appear to be living up to 
licencing agreement.

Cheers!

Re: Google Chrome can share but Chromium cannot share screen

[Corentin Bardet]

Hi,

Le 2022-09-11 07:39, Pankaj Jangid a écrit :

For a few work related meetings, I have to use Google Meet. But the
screensharing doesn't work in the Chromium installed from stable APT
repository. Clicking on the share-screen icon and then selecting any of
the three options - Tab, Windows, Entire Screen - shows this error
message,

"Your browser can't share your screen"

But if I install and use Google Chrome, then the screen sharing works 
in

Google Meet.


That doesn't surprise me much.

Google removed the majority of its APIs from Chromium : 
[here](https://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome) 
and 
[here](https://www.omgubuntu.co.uk/2021/01/chromium-sync-google-api-removed)


Maybe screen sharing was a Google thing. Especially screen sharing to 
Google Meet.


I think you have no other option than using Google Chrome for your 
meetings.


Cheers,

Corentin Bardet
coren...@noxnet.eu

Re: Shikitega Malware Criptominer

[Camaleón]

El 2022-09-10 a las 17:38 +0200, Juan Gómez "Txonta" escribió:

> Acabo de recibir la noticia de un criptominero muy sofisticado que ataca
> servidores y sistemas linux, le llaman Shikitega.
> He buscado el tema en las listas de Debian y no he visto nada, en internet
> he encontrado bastante información pero relativo a prevención, detección y
> eliminación muy poca cosa.
> 
> Me gustaría poder sentirme seguro ante esto y poder certificar la integridad
> de mis maquinas.
> 
> ¿Algún consejo u orientación?
> 
> Muchas gracias.
> 
> Salud.
> 
> https://unaaldia.hispasec.com/2022/09/nuevo-malware-para-linux-elude-la-deteccion-mediante-un-despliegue-en-varias-fases.html

Ayer lo leí en Hispasec, que sigo mediante RSS, pero sinceramente, no 
entendí absolutamente nada :-)

Normalmente de estos anuncios de vulnerabilidades me fijo en el vector 
de ataque (cómo entra el bicho en el sistema) y el rastro que deja una 
vez dentro (para poder comprobar si el bicho está dentro) pero en este 
caso no lo dice (o no he podido descifrarlo de la noticia), no sé si por
desconocimiento porque no saben aún cómo logra acceder a los sistemas o 
por cualquier otro motivo.

En fin, se trata de una noticia interesante por el riesgo que supone, 
pero que me ha dejado así → (·_·)
  
Cualquier aclaración o traducción a los efectos prácticos de saber cómo 
mitigar/evitar la infección o una vez dentro, cómo detectarla, se 
agradecerá.

Saludos,

-- 
Camaleón