newsNews: Information on the password compromise

 
 
Latest News
The git service has moved to the new server posted by rwp, Sun Dec 4 00:38:44 2016 - 0 replies
Savannah is migrating to updated systems. posted by rwp, Wed Nov 30 23:56:33 2016 - 0 replies
Savannah suffering networking problems posted by rwp, Fri May 13 22:58:25 2016 - 0 replies
Savannah https SSL certificates updated posted by rwp, Fri Mar 25 05:32:10 2016 - 0 replies
Savannah IPv4 address has changed posted by rwp, Sun Aug 9 20:07:57 2015 - 0 replies
[180 news in archive]

Information on the password compromise

Item posted by Sylvain Beucler <Beuc> on Thu Dec 2 23:24:53 2010.

We'll keep this page updated:
http://savannah.gnu.org/maintenance/Compromise2010

Comments:

Copy of potentially compromised repositories (posted by Jean Delvare, Tue Dec 7 15:03:59 2010)

Where do we get access to a copy of the potentially compromised repositories, i.e. right before they were overwritten by the known-good backups? I definitely hope that a copy was made. I did commit a lot of changes between November 23rd and November 26th, and I would like to get access to them so that I can commit them again.

The project I am worried about is "dmidecode" but I am certain that other developers have similar concerns.


What to do (posted by Alex Schroeder, Tue Dec 7 10:12:53 2010)

When I svn commit I get the error "svn: File not found: transaction '455-ct', path '/emacswikipages/mon-macs.el'" and when I svn up, I get the error "svn: No such revision 458".

What happened? As far as the repository is concerned, my local files are in a future that wiped when the backup was restored.

If you're in the same situation, you may want to copy everything except the .svn dirs to another place, make a new checkout, move the backup in there and commit it as a single commit from the backup-restore-point to where your newer checkout was before the restore.

(Thanks to IcePic on #svn.)


   

 

Back to the top


Powered by Savane 3.1-cleanup