chickopozo
k is your id and c is the ciphertext the key is stored on their server.
And your email isn't stored but rather encrypted and the ciphertext passed via the url.
You should use a different domain as there are tricks to leverage arbitrary js on a subdomain.
Sandboxing is to help protect the client from arbitrary crap. It was never intended to protect the server.
And as for UI Redressing (aka ClickJacking) browsers that support the sandbox attribute must support X-Frame-Options.
See: cryptocat.
If you use the work social whilst creating a RSS reader you have already failed.
Sincerely, People who actually used Google Reader
P.S. A point-and-click html scraper to rss would be nice too.
crypt(1) should be an example of how not to do hashing.
@shanelija SHA-256 is a secure cryptographically secure hash function. It is not and was never intended nor should be used as a key derivation function.
Given time and email are not unique, they should not be used as a salt. Concatenation of a salt is not the correct method either, not for KDF and not for message authentication.
One of the aims of a hash functions is to be fast, really fast, super fast while making it computational infeasible to: make a message that will hash to a given value alter a message that when hashed will produce the same or a give value. Find two different messages with the same hash value.
bcrypt, scrypt, PBKDF2 are perfect for password storage.
YOU are not off the hook yet until you repeat these 2 sentences 10 times: A secure crypto algorithm/system/function/whatever MUST continue to be secure even if the algorithm/system/function/whatever is public.
It is perfectly fine to homebrew crypto given one key condition, you never ever ever ever use it for things that matter.
*I took my keys from in the house so... by ars standard that's serious theft.
Rather than reading that article might I suggest having a gander at moxie's https://www.cloudcracker.com and read his blog too for all the goodies.
It's quite likely actually.
Do you do your backups to an identical* computer right next to your main one? (* factor in wear)