GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
PLEASE NOTE: All LQ Rules apply to the General forum. Flame wars, personal attacks, hostility, insults and behavior of that nature will not be tolerated. Differing opinions are one of the things that make this site great, but to benefit from differing opinions the discourse must happen respectfully and thoughtfully... without insult or personal attack. Members who are unable or unwilling to participate in General under those parameters will not be permitted to do so. If you see behavior of this nature please report it.
some viruses spread on external hard drive, Usb key or stay online on your Mail inbox.. I use Avira free antivirus that should do the job just fine. Forget bios, as you won't stuck a game in bios, same virus won't stuck itself in bios or partition table.
I use Avira free antivirus that should do the job just fine.
"just fine" is relative and like "don't worry" doesn't say anything about the quality of the detection engine or the accuracy and speed of updates.
Originally Posted by yooy
Forget bios, as you won't stuck a game in bios, same virus won't stuck itself in bios or partition table.
BIOS viruses do exist: see CIH, search CanSecWest for Core Security's 2009 BIOS presentation or else see the more recent Mebromi. If one suspects BIOS tampering the first measure should be to flash it, not "forget" it.
@OP: I take it this isn't a Linux question so I'll be moving this thread to the Genral forum RSN.
I've read about CIH on wikipedia and it seems it only corrupts BIOS, not infects BIOS, but that may not be the case with Mebromi.. So be careful, maybe even your BIOS contains a virus. But don't panic.
Back in the olden days, when I was a young 'un, MBR viruses used to be common. They were commonly spread from the MBRs of infected floppies, so I think they've pretty much disappeared, though you can still google instructions for removing them.
I generally discourage the use of "biological" metaphors. They're popular but not accurate.
If you happen to walk into the elevator right after someone who's got Ebola walked out, you might be screwed. But only because of the way that biology works. Computers are machines. One. Zero. Yes. No.
Unfortunately, and especially in the Windows world, people run their machines as users (without passwords!) that "must be obeyed." In other words, a cat-burglar is lurking in a community knowing that every door and window is unlocked. In my experience, even the slightest attempt to actually use the authorization and authentication facilities, which every computer out there has, will stop rogue programs cold. If the file cannot be modified ... that's it.
Usually, and IMHO, exploits exploit a combination of "convenience," "inattentiveness," and simple "laziness." Attacking SSH passwords by brute-force, for example, because the SSH system is foolishly set up to allow passwords. Getting to a site which is uploaded via FTP to a shared system where everyone in the world is part of an "ftpusers" group and every file (yours, or someone else's) is read/writeable. And so on. But the rules of RNA and DNA, of biology, do not apply.
Malware could exist in any addressable region. That could include any writable area of any device. A device could be the normal storage of a drive or even the small eeprom on the drive. If one wanted to they could use groups of writable areas to make a more substantial malware. I suppose they could do tricks like use the format sectors or even use half or offset sectors to hide it.
As above, a bios is an addressable and writable area.