Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The cookies spec really should be incorporated into the SSL/TLS layer. Right now it's basically performing two encryption/signing steps immediately after each other, one at the web server, and another for the applications server. This is a pain-in-the-ass for the web server framework and adds several milliseconds of redundant latency.

The cookie data should be signed with the web server's private key.



Token Binding achieves something simular to what you propose. See http://www.browserauth.net/token-binding




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: