Intrusion Cleanup Forces Delay For GNOME 2.6 170
An anonymous reader writes "Looks like the GNOME site (both web and FTP) is back up and running again (from a replacement system). The restoration work is still going on, and dynamic content does not work yet. Bugzilla should be up by tomorrow (it is already in testing mode). More details are available in this announcement. Kudos to the GNOME sysadmin team for such a rapid recovery." However, blurzero writes "GNOME 2.6 was scheduled to be released sometime today, however after evidence of possible intrusion on the web server, the release has been delayed by one week, until March 31st." Update: 03/24 14:08 GMT by T : An anonymous reader points to this story on the delay at ZD Net Australia.
Well, there is one difference I appreciate... (Score:5, Insightful)
If only MSFT (and more importantly, proprietary software companies that aren't so much in the spotlight) were as forthcoming about break-ins.
Ya know... (Score:2, Insightful)
Re:Must've been a real bugger (Score:2, Insightful)
I am personally disappointed in having to wait another week, however I completely respect the Gnome team on their tireless efforts. :)
I definatly agree with the idea of rolling back to a backed up copy of their site, but perhaps they do not know how long someone was able to access their systems?
Gnome team, take all the time you need. :)
Re:Must've been a real bugger (Score:5, Insightful)
Either way, you only have to check the backup server data itself against (externally backed-up) MD5 checksums, and ask developers to re-commit any changes made during the suspect time.
Now try and do that to a mail server, and the fecal matter hits the air-handler. But, with data that is relatively static by comparison, it takes work, but isn't too much of a trial.
$0.98 in change, please :)
Dumb Cracker? (Score:4, Insightful)
According to Waugh, the GNOME Web servers that are hosted by Red Hat were compromised by "a dumb cracker who probably didn't realise what they got into".
Seems like he was smart enough to hack their system.
Kudos to the GNOME sysadmin team for getting owned (Score:0, Insightful)
Ack. Insightful? (Score:3, Insightful)
Something bad happens to someone we don't like. Haw Haw.
Why do people make such a big fucking deal out of double standards? Should I feel equally angry toward someone who kills a stranger as I would if they'd killed a relative? No.
Goes to show, Open Source != always secure (Score:1, Insightful)
MOD PARENT DOWN (Score:2, Insightful)
Re:Must've been a real bugger (Score:1, Insightful)
The caveat with that scenario is that you have to a) know exactly how the break-in occured in order to b) know that you can fix the system from the pre-break in state to remove the vulnrability before bringing the system back online.
Just re-imaging the server and putting it back online will result in the server being comprimised again.
Could it be?? (Score:3, Insightful)
Re:Confidence ? (Score:4, Insightful)
The point is, after a breakin you must determine when the breakin occured, because everything after that is suspect. The problem is it can sometimes be very difficult -- or impossible -- to determine when the breakin happened. Then you're really, really screwed.
Re:Must've been a real bugger (Score:3, Insightful)
What if the OS has a vulnribility and the attacker can get back in without issues?
a backup from a time known before the break-in
What if the attacker had installed the back door months before hand? You may not have a valid backup.
Re:Must've been a real bugger (Score:3, Insightful)
Re:Ack. Insightful? (Score:3, Insightful)
If so, then even if you don't KNOW or LIKE the victim, you should still support punishment of the criminal. Otherwise, you're encouraging elitism. Or do you want to live in a world where crimes against the unpopular are cheered and go unpunished?
I lived in a similar world called "Middle School," and I wouldn't want to go back.
Re:Well, there is one difference I appreciate... (Score:3, Insightful)
How does a public disclosure ensure the binaries are secure?
How can a proprietary software company, let alone its customers, be sure that there aren't any nasty suprises hidden in their products?
How? Probably the same way everyone else does it. The OS model does not have a monopoly on practices used to ensure code integrity.
Re:Linux on the desktop? Fair question, on topic. (Score:3, Insightful)
No, dumbass, the difference is that closed-source companies keep it a secret (or doesn't know in the first place) when their servers are compromised while Gnome and Debian are very up-front about it.
If you think this kind of thing hasn't happened to Microsoft, Oracle, etc., you're wrong. They just like to keep it quiet.
Re:Well, there is one difference I appreciate... (Score:1, Insightful)
I'm guessing Gnome runs some type of Linux/Apache server combo... if they were running Windows IIS, folks would be talking about what a piece of garbage IIS is (regardless of if the security breach was a bug or an IT/config issue)... and Microsoft would be bashed on the 7:00 news for yet another "virus" (you need to dumb it down for the national news).
Re:Must've been a real bugger (Score:3, Insightful)