Issue 39440 - ssh key change ...
Summary: ssh key change ...
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: mmeeks
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-22 10:19 UTC by mmeeks
Modified: 2008-12-05 17:12 UTC (History)
4 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
the same string - as an attachment. (603 bytes, text/txt)
2004-12-22 16:49 UTC, mmeeks 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mmeeks 2004-12-22 10:19:11 UTC 
So - ooo.ximian.com was compromised yesterday; and in the process my [passphrase
protected] private key escaped into the wild.
Thus - it would be good to switch my old key:

[ OLD KEY ]
ssh-dss
AAAAB3NzaC1kc3MAAACBAMzjMJYt+qUgCQVBUrZNWNMEDZYg+/XAJoWvT3uSLud6w7OdlWnkz1Z7hkLXAvMzX/gvz0wlnRm3nLCbOovWbk+RT1DZvArZKhdf8WX3NnW4l7sajr/X2ga1vz7RiOgfo2qrvEHkRKktM9WjR6J+BAO4m2MTlTfDrM0kYNDZqNbvAAAAFQCmpKIx/nhYAa2jMzjhS0Fb1huGqQAAAIA1Px6IT9Vg58l0YNXvBkzBuyY8mHW557ngMHXKne8Z050VyLa3fptsl43LozsF7SYbH/9Pc0djpLlO7GRCpe6wXHKp6te3l8wT8G7giC2gj93x3l5n+n23Vk1WWqwB/+U1Qqm+28piifSUZNnSlDQx+E+OFmOBN2vvd5cSc0HNGAAAAIEAn1ADgLVa/DdUVUyRi6cHyRThrAMgCCuQGnpfb4HOm/LUgaLQ3I/f6OoCqvV3N6Mxka54x69IUZb8qezE+Y8OLAlpUwsYzklJNZMR8hWFKaO1lUc3SCWJtaJXx+1iE19vz9ckOxXVP+CegqyQoBDYBgqvtlw+tmdEtDP0yyvXO7w=
michael@michael.home
[ / OLD KEY ]

For my new Key:

[ NEW KEY ]
ssh-dss
AAAAB3NzaC1kc3MAAACBAM5vJNERTZG4cbvF4IU2uKaFO91q8QAJtR5GIgVpyjfFgqX5pKSIKEr/hOmXsPilAL23dZ5irhDxPsf7qRK/ORHmbh1GSLBnVUqQ1CXiDi5KTf0M/lbgEKeQTeld7zEjduow44rJwpmniWFV85Pjrsrlhwo0PiJSrFedullQB/sxAAAAFQCbDvgAIZ3KXp+XbCPtWmXHPAEFwQAAAIEAxliTa8/eQSwuXOlCTdtcuMZdl9dHRi9pOMI2z4YR/CiLUuQtkYU6n0rL/+/0qWGES2WhDwClGPGqk6Gf527OFrFRR8jLhRWyAHE+49epGbmW0b/N/FrmYqoP9Wi9xk4UsuoU59IxzgX7v8z1wZWL45BBi4JiODAy6Up/m9jBym0AAACANzpIrI0TmIsaP3pgPtejHXJb+6Y7dQWP+dOY299kROTqoeVZN0VxSGqY9j5BcbJJEQkqXsfVUtr+qPFKajkYqeLRg0t/QzO5wH+TVfQ6GTgPDjhVNIe/9BXIzs5tHnMffeJ74u5590+ZtAHEgfcpWMIFF3cTmTdSO5uZ1u2V7SE=
michael@linux
[ / NEW KEY ]

the private key for which now also has an insanely strong pass-phrase for good
measure.
Comment 1 stx123 2004-12-22 10:32:03 UTC 
Please remove the old key and add the new one.
Thanks, Stefan
Comment 2 lsuarezpotts 2004-12-22 16:38:25 UTC 
Michael,
We normally require that the key  be attached as an attachment.

Louis
Comment 3 mmeeks 2004-12-22 16:49:11 UTC 
Created attachment 20774 [details]
the same string - as an attachment.
Comment 4 lsuarezpotts 2004-12-22 17:21:27 UTC 
thanks, Michael. Our apologies for being such sticklers. 
Cheers, and enjoy the holidays,
Louis
Comment 5 Unknown 2004-12-23 08:29:15 UTC 
The key has been uploaded , resolving the issue .

Jobin.
Comment 6 stx123 2004-12-23 08:53:09 UTC 
Please confirm that the "OLD KEY" has been removed.
Thanks, Stefan
Comment 7 mmeeks 2004-12-23 21:00:09 UTC 
While the new key functions, the old key has not been removed (as you suspected
Stefan)
Comment 8 Unknown 2004-12-24 12:30:36 UTC 
Requesting the operations to remove the old key .

Jobin.
Comment 9 Unknown 2004-12-28 11:46:33 UTC 
The old key has been removed , closing the issue .

Jobin.
Comment 10 Unknown 2004-12-28 13:52:49 UTC 
closing
Comment 11 Unknown 2006-10-25 14:11:53 UTC 
Could we close this issue .
Comment 12 lsuarezpotts 2006-10-26 17:05:33 UTC 
reassigning to mmeeks
Comment 13 lsuarezpotts 2006-10-26 17:06:41 UTC 
reassigning
Comment 14 mmeeks 2006-10-26 17:33:41 UTC 
I didn't realised there was another step after 'fixed' of 'closed' ;-) it is now
closed.
Comment 15 mmeeks 2008-11-25 13:58:31 UTC 
re-open for new SVN I guess.
Comment 16 jens-heiner.rechtien 2008-11-25 14:49:12 UTC 
Migrated to SVN.
Comment 17 jens-heiner.rechtien 2008-12-05 17:09:03 UTC 
Close issue.