News for hackers. Stuff that matters.
Re:Instagram's Million Dollar Bug by dogecoinbase on Thursday December 17, 2015 @05:16PM (#10754991)
I certainly wouldn't consider dumping credentials to test for reuse/continued use a privacy violation. If FB wants people not to dump data, they need to make that explicit and specific.
Re:Instagram's Million Dollar Bug by foldr on Thursday December 17, 2015 @05:21PM (#10755016)
Really? The article states: "To say that I had gained access to basically all of Instagram's secret key material would probably be a fair statement". How on earth would holding on to that data not be a privacy violation?
Re:Instagram's Million Dollar Bug by dogecoinbase on Thursday December 17, 2015 @05:24PM (#10755039)
Holding credentials is not violating privacy. It would be possible to use those credentials to violate privacy, but merely having them is not that act.
Re:Instagram's Million Dollar Bug by dsacco on Thursday December 17, 2015 @05:36PM (#10755123)
Holding sensitive credentials is absolutely a violation of privacy. This is like saying that having a user's password is not a privacy violation unless you use it to gain access to their account.
Re:Instagram's Million Dollar Bug by enixn on Thursday December 17, 2015 @06:18PM (#10755412)
So would you agree that holding the keys to someone's house is also a privacy violation? What if instead of keys, you were holding a set of lockpicks? Would everyone's privacy of home be immediately violated?
Re:Instagram's Million Dollar Bug by foldr on Thursday December 17, 2015 @08:15PM (#10755969)
It's all a question of intent. If you keep the lockpicks so that you can pick locks, then yes. If you're a lockpick collector, then no.
Re:Instagram's Million Dollar Bug by comex on Thursday December 17, 2015 @06:43PM (#10755559)
Holding a manually chosen password can be a privacy violation because it's a small peek into the user's psyche. (I wouldn't say the employee "changeme", "instagram" etc. passwords count, although the act of running a password cracking tool meant that he could have seen a more personal password.)

Holding some randomly generated numbers that could be used to access a server is not.

Re:Instagram's Million Dollar Bug by Gravityloss on Thursday December 17, 2015 @06:19PM (#10755416)
I understood it was employee credentials, not customer.
Re:Instagram's Million Dollar Bug by Cakez0r on Thursday December 17, 2015 @06:17PM (#10755405)
Surely they would have to revoke all the keys anyway as they would have no idea if a blackhat got their first and took the keys before the vulnerability was reported?
Re:Instagram's Million Dollar Bug by bigiain on Thursday December 17, 2015 @06:36PM (#10755514)
According to the timeline, Instagram have known about the ssl keys since 1 Dec.

My browser is currently showing an ssl cert for instagram.com that was issued in April and expires on Dec 31.

Doesn't look like they're in any hurry to revoke that one. (I guess like Alex Stamos told his employer - it's "trivial and of little value"...)

Re:Instagram's Million Dollar Bug by eropple on Thursday December 17, 2015 @08:04PM (#10755918)
Or, like almost any company that's reasonably competent, they have multiple certificates with different private keys.
Re:Instagram's Million Dollar Bug by bigiain on Thursday December 17, 2015 @08:08PM (#10755936)
And they just happen to only leave some of them in their S3 buckets?

Seems … contradictory.