News for hackers. Stuff that matters.
Re:I’m sorry, but were you actually trying to remember your ... by cubicle67 on Monday August 15, 2011 @07:49AM (#2886389)
At the risk of exposing my considerable ignorance, provided this is done over ssl, how is it different from a reset password link or any other information?
Re:I’m sorry, but were you actually trying to remember your ... by kgermino on Monday August 15, 2011 @08:33AM (#2886551)
Expiration time, password reset emails are typically one-time-use so it doesn't matter if they're in logs once the user has loaded the page.
Re:I’m sorry, but were you actually trying to remember your ... by cubicle67 on Monday August 15, 2011 @09:14AM (#2886700)
What if the key was tied to the machine it was first used with? That may get confusing for users though
Re:I’m sorry, but were you actually trying to remember your ... by owenmarshall on Monday August 15, 2011 @09:35AM (#2886803)
What happens when someone hits your app from a library computer? From behind a proxy? Have you thought about what happens when their IP changes?

Stop. You are inventing a crazy homebrew authentication system here. One great way to absolutely fuck your site's security is through crazy homebrew authentication/authorization/cryptography.

Do it right, don't do it yourself.

Re:I’m sorry, but were you actually trying to remember your ... by sapphirecat on Monday August 15, 2011 @11:50AM (#2887369)
> Have you thought about what happens when their IP changes?

++. When I was walking this road, I answered that question with "I'll use the user-agent instead!" Then I checked that assumption, and the Internet told me that could vary between requests as well. That was the key insight (you can't trust anything) that put me on the road to a much more standard system. (But probably still insecure, since I was younger and working for someone with NIH syndrome.)

Re:I’m sorry, but were you actually trying to remember your ... by politician on Monday August 15, 2011 @09:49AM (#2886865)
I previously did some work for an online poker service who had a financial incentive in knowing who was logging in as who and had a custom client with which they could do all sorts of nasty spyware-esque things to the client's machine. And they were still susceptible to hackers.

You have a browser for a client and HTTP. Please, don't end up on HN as sadly yet another cautionary tale for doing security wrong.

Re:I’m sorry, but were you actually trying to remember your ... by true_religion on Monday August 15, 2011 @09:22AM (#2886734)
IP addresses can be spoofed.

You'd have to also place a secret code on each page, and reject form data or user requests (e.g. to delete their data, etc.) if the secret code wasn't submitted.