| |||||||||||||
Lessons from the Debian compromise: backups.Lessons from the Debian compromise: backups.Posted Dec 11, 2003 11:32 UTC (Thu) by hensema (guest, #980)Parent article: Lessons from the Debian compromise So after the fire at Twente University and the recent crack, Debian still fails to learn the most important lesson: make backups! It cannot be stressed enough how important this is. Backups are far more important than relying on the mistakes a cracker makes.
(Log in to post comments)
Lessons from the Debian compromise: backups. Posted Dec 11, 2003 20:44 UTC (Thu) by doogie (subscriber, #2445) [Link] There are backups. Debian machines backup their critical config data to other backup machines.Having backups does not mean compromises don't exist, and that when they do, they should just be ignored, and a backup deployed.
Lessons from the Debian compromise: backups. Posted Dec 13, 2003 18:57 UTC (Sat) by giraffedata (subscriber, #1954) [Link] And more than one copy too. Most people keep one copy of everything, just as protection in case a disk breaks or gets suddenly wiped out. So your backup contains the cracked version of your files.But what you really need to protect you from a crack, or various other forms of losses, is a multilevel rotation scheme. Have one copy from last night, but also a copy from each of the last 7 nights, and one copy from each of the last 7 weeks, and one copy from each of the last 49 weeks, etc. That way, when you find out that someone put a backdoor in your system a few weeks ago, you can restore the original files (which probably hadn't changed for years before that).
|
|||||||||||||