You might wish to read this thread online. Does not look terribly scary, but it is good to be aware of the piece of SW causing it.
On Thu, 19 Nov 2015 17:27:06 -0700, jd1008 wrote:
You might wish to read this thread online. Does not look terribly scary, but it is good to be aware of the piece of SW causing it.
And what is "the piece of SW causing it"?
And what do you mean by stating:"You might wish to read this thread online?". I read your post using a newsreader. Am I reading it online?
And BTW, I do not actually see a thread but you only single post.
I think you couldn't make your post less clear than you did. Takes a lot of effort, I guess. :-)
Thank you.
On 11/19/2015 06:48 PM, Juan R. de Silva wrote:
On Thu, 19 Nov 2015 17:27:06 -0700, jd1008 wrote:
You might wish to read this thread online. Does not look terribly scary, but it is good to be aware of the piece of SW causing it.
And what is "the piece of SW causing it"?
And what do you mean by stating:"You might wish to read this thread online?". I read your post using a newsreader. Am I reading it online?
And BTW, I do not actually see a thread but you only single post.
I think you couldn't make your post less clear than you did. Takes a lot of effort, I guess. :-)
Thank you.
Try http://lists.freebsd.org/pipermail/freebsd-questions/2015-November/subject.h... ans scroll down the page looking for the subject line: ransomware virus on Linux
On 11/19/2015 08:25 PM, jd1008 wrote:
Try http://lists.freebsd.org/pipermail/freebsd-questions/2015-November/subject.h...
ans scroll down the page looking for the subject line: ransomware virus on Linux
Old news.
http://www.zdnet.com/article/how-to-fix-linux-encoder-ransomware/
On 11/19/2015 09:34 PM, Glenn Holmer wrote:
On 11/19/2015 08:25 PM, jd1008 wrote:
Try http://lists.freebsd.org/pipermail/freebsd-questions/2015-November/subject.h...
ans scroll down the page looking for the subject line: ransomware virus on Linux
Old news.
http://www.zdnet.com/article/how-to-fix-linux-encoder-ransomware/
I looked at the article on zdnet. It does not mention another Linux routine that I heard about on one of the mailing lists. (I don't remember which one.) This other routine is called randm-C. As I followed the thread, it mentioned that BitDefender has a program that will _stop it_ but _not_ restore your files. One of the Linux forums commented that only servers need worry, the hackers won't bother with the home user. I don't know if I believe this.
(I have used BitDefender on Windows machines for several years, and it does seem to be a useful program; I haven't caught any virus in that time, but I don't boot up a Windows system very often, and I don't leave it up for a long time when I do.)
--doug
Allegedly, on or about 19 November 2015, Doug sent:
I haven't caught any virus in that time, but I don't boot up a Windows system very often, and I don't leave it up for a long time when I do.)
How long you're up really means nothing. Years ago, a friend rang me to tell me to come up and watch him install his brand new XP. 4 seconds after finishing the install, it got infected by a virus.
I nearly laughed my head off. He couldn't remove it, either. Windows allowed the virus to change an important system file, but wouldn't allow anything else to. So he had to reformat and reinstall. It happened again, seconds after booting up, despite my telling him that he ought to run a firewall, install anti-virus, before connecting his computer to a network, but he was sure that it wouldn't happen again.
Three times in a row we went through that pallaver, nearly wet myself laughing. And you may remember that it's not a quick process to install XP. Back in its day, computers and CD-ROMs were not that quick.
So I scoff at those who say it's okay to temporarily drop firewalls, only connect for a moment, etc. I know it's not true. I know that some ISPs are continually being port scanned and do nothing to stop it.
-
Doug -
Glenn Holmer -
JD -
Juan R. de Silva -
Tim