Looks like that only would be useful when you can't protect the link's resource itself with authentication requirements, and I can only see it as being useful when assuming a passive attacker who aren't trying to access the link before the intended recipient. I would even consider encrypting the link before giving it to the server, and sharing the key along with the custom link/password. Instead of having one password and one counter, I'd prefer a number of one time passwords that I can give separately to the different recipients. Each person gets one password, each password works once.
On Thu, May 3, 2012 at 8:38 AM, John Doe <[email protected]> wrote: > > A friend of mine created a service called: *This Link Will Self > Destruct*(TLWSD) > It is a free public temporary URL service. The mission is to provide the > internet with a fast, friendly, private, and secure means to exchange > hyperlinks without leaving a digital paper trail. > > He provided the source http://tlwsd.info/source/ - for everybody to check > the implementation as well.. > Direct contact: [email protected] > > Think this is a clever way to help enabling privacy a bit more. > Any suggestions? > > --Michael > > > > _______________________________________________ > cryptography mailing list > [email protected] > http://lists.randombit.net/mailman/listinfo/cryptography > >
_______________________________________________ cryptography mailing list [email protected] http://lists.randombit.net/mailman/listinfo/cryptography
