489 karma · joined September 20, 2010
My point still stands, though: the point of cookieless domains is not security, but bandwidth. And there are legitimate reasons to have top-level domain cookies - sharing authentication state between subdomains is a common example - which would prevent a subdomain from being used as a CDN, without receiving cookies.
It could probably access it less often by only sending deltas, but that would mean their servers would have to store your whole phone book. I don't think that's any better from a privacy perspective.
Of course Facebook Messenger doesn't do the same, it has its own contact list coming from Facebook.
Google, on the other hand, did the exact same thing, but I remember explicitly agreeing to that.
On the other hand, if anything, I exposed that they did a good job. They could have rolled out their own crypto, or some flawed form of code generation, in which case I would have disclosed it to them through proper means. But they adhered to standards (TOTP, RFC6238) and protected their data as well as possible. This article should be seen as praise.
Then again, corporations aren't always that understanding, which is why I would be happy to comply.
On the other hand, counter-based tokens as you described them do exist, and it would indeed be simple to detect if one of those was cloned.
I wouldn't even call this an attack, given that you would need physical access to a rooted device to carry it out.
Also, I noticed a public key in ~/.ssh/authorized_keys. Is that intentional or just part of how EC2 APIs work?
Other than that, great job. I would definitely use this service.
This pretty much sums it up. I couldn't agree more.
I used the "Video" library to make a video out of the animation, and Maxmind's Java library for geolocation. Other than that, it's pure Processing.
>what platform did you do that on?
The video was rendered on a Mac. Is that what you meant?
Giving out passwords to customers is the most common approach, but there must be a way to provide encrypted access without a shared key.
The default, on the other hand, is pretty secure, and I recommend it (unless you have a really good reason to do otherwise).
Also, someone claiming a system to be "cyber attack proof" is clearly misguided.