Language Selection

English French German Italian Portuguese Spanish

Thank you, Linux! My Windows computer is infected

Filed under
Linux
Microsoft
Security
Humor

That's right. My desktop, which runs Windows, is infected and I blame Linux.

As it normally happens in these cases, this new infection in my XP system can be traced back to user carelessness. However, I think that calling me "careless" is not fair for I did everything on the book (and more!) to keep a Windows machine healthy:

1. I have an updated antivirus, which runs full scans when I turn the PC on.
2. My firewall was up and running.
3. I have additional anti-malware software for protection.
4. Firefox is my browser and I installed add-ons for extra security.
5. I neither open suspicious email attachments nor visit questionable sites.

Since I was not careless, I am not the culprit. However, if I did something wrong, this is it:

res there




User's fault entirely

If you download an infected file to your machine, it is your fault. If you use autoplay in Windows, it is your fault. If you can't use Windows properly, it is your fault.

Fancy titles = lots of clicks; this post proves it.

User's fault?

@Snoochie

So you said, "If you download an infected file to your machine, it is your fault. If you use autoplay in Windows, it is your fault. If you can't use Windows properly, it is your fault."

What?
It is the fault of the user who downloads a file which turns out to be infected, and the windows system didn't detect and warn and/or stop the infection?
Using your windows system as designed for ease of use (autoplay) becomes the user's fault?
Having taken all the precautions expected, (and beyond the usual) and a windows infection happens, it is the user's fault?
This is not a fair critique.
I know, I know...I can hear you say you have used your current windows setup for years without any infection.
But you have to be on constant alert, deny yourself the whole, wide range of the Internet and avoid those cute, huggable-bunny vids that your grandma attached to her email to you because they may have a windows virus.
That is too much work and worry for me, a happy Linux Mint user!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's leftovers

Software: VirtualBox, TeX Live Cockpit, Mailspring, Qt, Projects, and Maintainers

  • VirtualBox 5.2.2 Brings Linux 4.14 Fixes, HiDPI UI Improvements
    The Oracle developers behind VM VirtualBox have released a new maintenance build in the VirtualBox 5.2 series that is a bit more exciting than their usual point releases.
  • TeX Live Cockpit
    I have been working quite some time on a new front end for the TeX Live Manager tlmgr. Early versions have leaked into TeX Live, but the last month or two has seen many changes in tlmgr itself, in particular support for JSON output. These changes were mostly driven by the need (or ease) of the new frontend: TLCockpit.
  • Mailspring – A New Open Source Cross-Platform Email Client
    Mailspring is a fork of the now discontinued Nylas Mail client. It does, however, offer a much better performance, and is built with a native C++ sync engine instead of JavaScript. According to the development team, the company is sunsetting further development of Mailspring. Mailspring offers virtually all the best features housed in Nylas Mail, and thanks to its native C++ sync engine it uses fewer dependencies which results in less lag and a reduction in RAM usage by 50% compared to Nylas Mail.
  • Removing Qt 4 from Debian testing (aka Buster): some statistics
    We started filing bugs around September 9. That means roughly 11 weeks, which gives us around 8 packages fixed a week, aka 1.14 packages per day. Not bad at all!
  • Products Over Projects
    However, projects are not the only way of funding and organizing software development. For instance, many companies that sell software as a product or a service do not fund or organize their core product/platform development in the form of projects. Instead, they run product development and support using near-permanent teams for as long as the product is sold in the market. The budget may vary year on year but it is generally sufficient to fund a durable, core development organization continuously for the life of the product. Teams are funded to work on a particular business problem or offering over a period of time; with the nature work being defined by a business problem to address rather than a set of functions to deliver. We call this way of working as “product-mode” and assert that it is not necessary to be building a software product in order to fund and organize software development like this.
  • Why we never thank open source maintainers

    It is true that some of you guys can build a tool in a hackathon, but maintaining a project is a lot more difficult than building a project. Most of the time they are not writing code, but [...]

today's howtos

Tizen News