Ask HN: Why not to bind cookie to IP-address of the user? (Facebook and Tunisia)

3 points·pankratiev··8 comments

This thought came when I read comments about Facebook, passwords and Tunisia http://news.ycombinator.com/item?id=2135563

In this case stealing the cookie will not so reasonable. And it can be easily implemented - just store key of the cookie with IP-address of the user on the server-side.

What do you think?

View on HN

It's not possible to do this as with certain ISPs that assign dynamic IPs or inside large buildings that have multiple outgoing IPs, one user can have a different IP for different requests made at the same time.

Ohh, I missed the problem with dynamic IPs. But what about MAC-address, why browsers don't bind the cookie to the MAC-address of the computer?

Browsers? You mean web servers, surely? Servers don't know the client's mac address.

In the post I meant server-side, in my comment I meant client-side.

The general question - why not to bind the cookie to some other identifier of the user or user's computer to make cookie useless in thief's hands.

In general, the attacking computer can pretend to have the characteristics of the impersonated computer.

Then again, if someone would go the lengths to hack into someone else's account, I think it's possible to spoof a MAC-address.

You are right, in the case of Facebook in Tunisia - providers could inject the code which store user's cookie and MAC-address. My idea is useless. :-(

There is no way the server would know the mac address of the client unless the browser stores and shares that information. This is not how currently implemented networking protocols work.

Reply on news.ycombinator.com