From kde-commits Sun May 08 19:55:55 2005
From: Dirk Mueller
Send a mail to sysadmin (at) office (dot) kde (dot) org +
Send a mail to sysadmin (at) kde (dot) org justify why you need cvs access. Make sure to specify your full name and e-mail address, if the From field in your mails doesn't specify them. Please include the name of your bugs.kde.org account if already existent @@ -491,7 +491,7 @@ attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to - notify sysadmin (at) office (dot) kde (dot) org immediately when you notice that someone may have + notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.
@@ -504,7 +504,7 @@ private/public key pair with ssh-keygen -t dsa . This will create a private key as ~/.ssh/id_dsa andNote how ,v
was added to every file name.
- Then send this list to sysadmin (at) office (dot) kde (dot) org.
+ Then send this list to sysadmin (at) kde (dot) org.
Once the files have been copied on the server, you can delete
the old ones from the client using cvs remove -f
and make the necessary changes (updating the Makefile.am in particular).