4 ms·
So whats the attack vector here? You have unknown users private key to a unknown service. Of course you should keep your private keys private, but exploiting th
by zokier 17y ago
So whats the attack vector here? You have unknown users private key to a unknown service. Of course you should keep your private keys private, but exploiting this takes quite a stretch.
- olefoo 17y agoKey oriented scanners exist, in fact they became wildly popular after the 2008 Debian openssh randomness debacle. You should rekey your network on a regular schedule at least as often as you change your passwords.
- wmf 17y agoat least as often as you change your passwords So, never? http://www.boston.com/bostonglobe/ideas/articles/2010/04/11/please_do_not_change_your_password/ http://www.boston.com/bostonglobe/ideas/articles/2010/04/11/...
- olefoo 17y agoI'd missed that story, it has a point, in that passwords are a very poor solution to that problem. But, if you're going to use them, you should change them regularly. But you should write them down and keep them in a secure location. Just like you keep a backup of your private keys...
- vog 17y agoThis is not about a conctete attack. It is about a fundamental lack of care and understanding in crypto security. These Google results demonstrate the utter sluttery of various system administrators. In the same vein: Buffer overflows should never be tolerated, even if they were un-exploitable in some cases because of lucky circumstances.
- duck 17y agoFor starters anyone with access to the pastie server logs has your IP which would be a great starting point.