3 ms·
That is a good start. Although I am not a paying user (which would have TLS if I am one), that makes everyone protected from the benefits. I also hope that they
by itsnotvalid 16y ago
That is a good start. Although I am not a paying user (which would have TLS if I am one), that makes everyone protected from the benefits. I also hope that they would not suffer from performance issues, as I've see several loading problems since the change.
- kneath 16y agoWe have always implemented SSL regardless to your paid or unpaid status. This is an unfortunate inaccuracy in Eric's Firesheep followup post that he refuses to correct. Previously, SSL was only implemented on private facing pages, such as (everyone's) dashboard, (everyone's) account pages, (everyone's) repository admin pages and all pages under private repositories. I know it's a small difference (private vs paid), but GitHub would never hold security hostage for money — the thought of that makes my skin crawl.
- bostonvaulter2 16y agoBack when github first launched, SSL protection was only included on private repositories. http://web.archive.org/web/20080621111340/http://github.com/plans http://web.archive.org/web/20080621111340/http://github.com/... Although I may be misunderstanding something.
- kneath 16y agoWell, first off... that's a really old archive (come on now). The problem there was that the wording was wrong (private repositories vs paid accounts).
- itsnotvalid 16y agoThanks for correcting me on this regard. Now it is nice that TLS is mandatory.