70 karma · joined January 19, 2011
I can envision a _lot_ of use cases for having your name publicly recognized by a trusted party.
class A:
a = (1,)
b = [1,]
def __init__(self):
self.a = (1,)
self.b = [1,]
A.a # this is the class attribute
(1,)
A.b # class attribute
[1]
obj = A()
obj.a # instance attribute
(1,)
obj.b
[1]
obj.a += (2,)
obj.b += [2,]
A.a
(1,) # still the same class attribute
A.b
[1]
obj.a
(1, 2) # instance attribute appended
obj.b
[1, 2]Re1Ra1 Re2Ra2 Re3Ra3 Re4Ra4 Re5Ra5 Re6Ra6
Re2Ra2 Re3Ra3 Re4Ra4 Re5Ra5 Re6Ra6 Re1Ra1
Re3Ra3 Re4Ra4 Re5Ra5 Re6Ra6 Re1Ra1 Re2Ra2
Re4Ra4 Re5Ra5 Re6Ra6 Re1Ra1 Re2Ra2 Re3Ra3
Re5Ra5 Re6Ra6 Re1Ra1 Re2Ra2 Re3Ra3 Re4Ra4
Re6Ra6 Re1Ra1 Re2Ra2 Re3Ra3 Re4Ra4 Re5Ra5
This is not a security flaw. Comparing browser password storage to a safe is mildly retarded.
Feels like the blinking banners of "you've just won a car!!!!" we all love from the former web, no?
But it's real - no charge on my credit card - and I think it's a wonderful way of getting lots of attention for a fair price.
I know I'll tell all my friends ;-)
Go Sparkfun!! :D
Edit: I'm not sure I understand what you mean - there was 100k passwords in one file, already cracked, and another with all 6.5M hashes. I found my hash in the hashes file.
Did they not post the entire load (and are in fact sitting on _all_ the hashes?) Is the dump an old backup or breach from when they had fewer accounts? Is it just one DB partition / file that's been lost, an archive?
The leaked hashes seems to be SHA-1. I've also confirmed that the hash of my own (semi-complex) LinkedIn password is in the list. Accidentally this is the same password as I had for HN and that I've now changed (phew! THAT'd been bad! :-)