Roger Oberholtzer wrote:
If a windows machine infected with this Trojan also has mRemote installed, and mRemote's configuration contains a root password to a Linux machine, the Trojan ssh's in to the Linux machine as root and erases /kernel, /usr, /etc, and /home.
Classically, one never allows root access to an important machine except locally from the console. Even for less important machines, one never allows network root login; an admin must login over the network as himself and then su or sudo to access privileged capabilities.
If the bash script is clever enough, it will take this into account and use the found pw for the user to do a sudo.
Storing passwords is the not so clever practice here, I think.
Correction: storing password on a windows machine.
Do as I say, not as I do, of course :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org