Comment on One-time Secret: Share passwords etc with URIs that work only onceparentComments−mbreese14yI'm thinking that their unique ID (31 char) plus the key (AES 22) is a little long for a URL:http://example.com/1234567890123456789012345678901/123456789...I do like the idea though of keeping the secrets safe with a client-side (or non-stored) key. So long as it's known that it isn't about keeping the server honest, since you have to implicitly trust that they won't be storing the key.−JoachimSchipper14yTinyURL is currently giving out 8-character identifiers; I'm confident that those 31 characters can be trimmed a bit. ;-)
Comments
I'm thinking that their unique ID (31 char) plus the key (AES 22) is a little long for a URL:
http://example.com/1234567890123456789012345678901/123456789...
I do like the idea though of keeping the secrets safe with a client-side (or non-stored) key. So long as it's known that it isn't about keeping the server honest, since you have to implicitly trust that they won't be storing the key.
TinyURL is currently giving out 8-character identifiers; I'm confident that those 31 characters can be trimmed a bit. ;-)