Absolutely you're right the best way to handle a rootkit is restore from a known-good backup. Just like you practiced, last month when you tested it when found and fixed the problem with backup system.
Unfortunately, 90% of people don't have a proper backup system. Probably over half of systems that are being "backed up" can't actually be restored because the backup media went bad a year ago or whatever.
For the people who don't have a solid backup:
> some IT professional who sells himself to a client by cl
Huh? What operating system are you using? Out of the box, Windows sets you up with OneDrive and points all of your storage stuff to OneDrive. The result is that all your files are backed up.
Out of the box, Apple sets up iCloud and points all your file storage to iCloud. The result is that all your files are backed up.
You can use DropBox or a thousand alternatives if you want.
If you want a better solution, you can use either Windows Backup and Restore or Apple Time Machine which does pretty much the same thin
That said, to be honest, I have absolutely no idea how to maintain good backups of my Linux systems.
I don't mean to be rude, but you should turn in your geek card. Maintaining good backups is even easier in Linux than any other operating system.
Everything unique will be under/home/username. You can back this up with rsync, cp, tar, or even dd if it is a partition. There is no hand holding, but then, it really shouldn't be necessary when the design itself is so elegantly simple. What is even cooler is that this knowledge of backing up carries across to the various BSDs and other Unix-like operating systems.
I have to admit, since Windows 10 came out, I find myself using Windows a LOT less. I only ever boot into it to patch it. Every time I try to do something in it, I end up giving up after an hour and go back to Linux. Windows 10 feels like slipshod engineering along with the whole "microscope up my ass" feeling.
Re: (Score:3)
Data yes, OS and programs, no (Score:2)
Absolutely you're right the best way to handle a rootkit is restore from a known-good backup. Just like you practiced, last month when you tested it when found and fixed the problem with backup system.
Unfortunately, 90% of people don't have a proper backup system. Probably over half of systems that are being "backed up" can't actually be restored because the backup media went bad a year ago or whatever.
For the people who don't have a solid backup:
> some IT professional who sells himself to a client by cl
Re: (Score:3, Interesting)
Out of the box, Windows sets you up with OneDrive and points all of your storage stuff to OneDrive. The result is that all your files are backed up.
Out of the box, Apple sets up iCloud and points all your file storage to iCloud. The result is that all your files are backed up.
You can use DropBox or a thousand alternatives if you want.
If you want a better solution, you can use either Windows Backup and Restore or Apple Time Machine which does pretty much the same thin
Re:Data yes, OS and programs, no (Score:2)
That said, to be honest, I have absolutely no idea how to maintain good backups of my Linux systems.
I don't mean to be rude, but you should turn in your geek card. Maintaining good backups is even easier in Linux than any other operating system.
Everything unique will be under /home/username. You can back this up with rsync, cp, tar, or even dd if it is a partition. There is no hand holding, but then, it really shouldn't be necessary when the design itself is so elegantly simple. What is even cooler is that this knowledge of backing up carries across to the various BSDs and other Unix-like operating systems.
I have to admit, since Windows 10 came out, I find myself using Windows a LOT less. I only ever boot into it to patch it. Every time I try to do something in it, I end up giving up after an hour and go back to Linux. Windows 10 feels like slipshod engineering along with the whole "microscope up my ass" feeling.