Re:Sidejack Prevention
by mseebach on Wednesday October 27, 2010 @07:14AM
(#1838080)
What's wrong with GitHubs solution? As I understand it, only insensitive stuff is available in the unencrypted session, while writes and sensitive stuff goes via unsidejackable HTTPS. Stealing a read-only Facebook/Twitter session is much less critical, and allows for CDNs etc.
[ Parent
| on HN ]
Can someone still sidejack a session and view a private repo?
The secure cookie is meant to prevent this.