Christian Schoenebeck
2017-03-05 16:52:28 UTC
Hi guys,
on March 2nd we had an attack on our svn server. Due to that we took most
services temporarily offline on March 3rd to protect people from accessing any
potentially compromised material and to prevent further damage.
After investigating this incident we came to the conclusion that the attack
and its damage was fortunately quite limited. We rolled back the system,
closed the exploited security hole and finally brought all services back
online today.
In case you accessed any source files from our svn server between March 2nd
and March 3rd, we encourage you to delete the entire source directory and make
a fresh svn checkout. The svn server is now back at a clean state.
Additionally, several old svn user accounts have been disabled for now. In
case you haven't been active for a while and your svn user account doesn't
work anymore, just contact me or Andreas and you will get your account
re-enabled with a new password.
CU
Christian
on March 2nd we had an attack on our svn server. Due to that we took most
services temporarily offline on March 3rd to protect people from accessing any
potentially compromised material and to prevent further damage.
After investigating this incident we came to the conclusion that the attack
and its damage was fortunately quite limited. We rolled back the system,
closed the exploited security hole and finally brought all services back
online today.
In case you accessed any source files from our svn server between March 2nd
and March 3rd, we encourage you to delete the entire source directory and make
a fresh svn checkout. The svn server is now back at a clean state.
Additionally, several old svn user accounts have been disabled for now. In
case you haven't been active for a while and your svn user account doesn't
work anymore, just contact me or Andreas and you will get your account
re-enabled with a new password.
CU
Christian