Apache OpenOffice (AOO) Bugzilla – Issue 63157
Due to a possible security hazard, change my ssh key, please
Last modified: 2008-12-05 17:12:05 UTC
Due to a security hazard last night, I cannot be 100% sure that my key was not compromised. Therefore, I reinstalled from scratch the box and regenerated a new key. Could you, please, replace the existing key as soon as possible?
Created attachment 34858 [details] my new ssh key
support, please ask ops to upload this key. Louis
Taking this issue and will update you once it is done. Thanks, Kavitha Support Operations
Hi, We have uploaded the key for you on to the server. Please verify and let us know if you have any questions. Thanks, Kavitha Support Operations
The tunnel could be established. Thanks. Verified.
Reopening to reassign
Please, remove the old ssh public key, because I cannot exclude that the corresponding private key is compromised.
assigning to support
Hi fridrich Do you want to remove the public key which has been attached in this issue from the server,are you sure about it and by the way do you want me to upload a new key.If so please attach the new key so that we could upload the new one,please get back to be at the earliest. Regards, Karthik Support Operations
No, the key attached to this issue is a NEW key that I regenerated after I concluded that I could not be 100% sure that the key from http://qa.openoffice.org/issues/show_bug.cgi?id=36920 was safe. I would like to remove the key from http://qa.openoffice.org/issues/show_bug.cgi?id=36920 it means, my OLD key from the keyring so that nobody can use the corresponding private key to write access ooo cvs repository in cas it is compromised. Thanks to contact me if you need more precision Fridrich
reassigning to support for removal of old key.
Old key with the email address strbafridrich@shell.sf.net has been removed now. can you please verify and let us know if you have questions further. Thanks, Kavitha Support Operations
Fridrich, I guess without the old key you don't have a chance to verify the removal of the key. So we should close this issue...
st: exactly. So, following your suggestion, closing
.
Reopening so that the key might be integrated in svn
Migrated to SVN.
Close issue.