Any reason why codeforces isn't using a secured http connection??
→ Обратите внимание
До соревнования
CodeTON Round 9 (Div. 1 + Div. 2, Rated, Prizes!)
3 дня
Зарегистрироваться »
CodeTON Round 9 (Div. 1 + Div. 2, Rated, Prizes!)
3 дня
Зарегистрироваться »
*есть доп. регистрация
→ Лидеры (рейтинг)
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | tourist | 4009 |
| 2 | jiangly | 3823 |
| 3 | Benq | 3738 |
| 4 | Radewoosh | 3633 |
| 5 | jqdai0815 | 3620 |
| 6 | orzdevinwang | 3529 |
| 7 | ecnerwala | 3446 |
| 8 | Um_nik | 3396 |
| 9 | ksun48 | 3390 |
| 10 | gamegame | 3386 |
| Страны | Города | Организации | Всё → |
→ Лидеры (вклад)
| № | Пользователь | Вклад |
|---|---|---|
| 1 | cry | 167 |
| 2 | Um_nik | 163 |
| 2 | maomao90 | 163 |
| 4 | atcoder_official | 161 |
| 5 | adamant | 159 |
| 6 | -is-this-fft- | 158 |
| 7 | awoo | 157 |
| 8 | TheScrasse | 154 |
| 9 | nor | 153 |
| 9 | Dominater069 | 153 |
→ Найти пользователя
→ Прямой эфир
Codeforces (c) Copyright 2010-2024 Михаил Мирзаянов
Соревнования по программированию 2.0
Время на сервере: 20.11.2024 18:39:04 (h2).
Десктопная версия, переключиться на мобильную.
При поддержке
The insufficient amount of paranoia among users and admins probably.
I also anticipate two minor troubles:
Serving via HTTPS requires additional processing time on both server and client (and also makes certain types of caching unusable). When the server is not experiencing peak load this would be hardly noticed. However during contest the amount of requests is very large and I suspect at least the delays will become quite sensible.
If policies of some countries require limited access to certain pages of the site (e.g. due to posting doubtful content by users) — then switching to HTTPS will force internet providers in such countries to limit access to the whole site as the per-page approach could not be used.
Now why we may want to use HTTPS? Do you suspect Snowden is stealing your solutions?
P.S. I myself do not mind HTTPS as long as it is optional, not obligatory.
UPD the main good point I learned from comments below is about preventing TCP sniffing in college LANs. Though I never heard this is a widespread problem right now :)
I don't want my ISP or free Wi-Fi provider inserting advertisement.
use adblock
It's not solution, only workaround
Just switch to more decent provider. There is no sane reason to mess with providers who do not respect its users.
If you can't trust provider enough, I doubt you can rely even on https over him as there could be foul play with certificates.
Not snowden, but if you are using college lan, than someone can sniff the packet and get the solution, during the live contest.
The correct question is: why wouldn't we want to use HTTPS? Privacy is a fundamental human right. You need to present very good reasons to deprive people of this right, not the other way around.
CodeForces provides free services. You are using these services voluntarily so it is not correct to complain you are deprived of privacy by evil CodeForces admins. And why do you need to post very private and personal info here?
And HTTPS do not automatically mean privacy.
I'm not complaining at all, I'm pointing out a flaw in your logic.
And you're making the same mistake again. I don't have to justify to you that I need privacy, you have to justify to me that there is a benefit in not having it. I have blinds on the window in my living room even though I don't do anything "private and personal" there.
HTTPS is a necessary but not sufficient condition for security and privacy.
I started with pointing out two.
Not in china
You just necroposted a 5 year old blog to say this
Given the times we are living in, I wrote the same (as the blog)question on Google and ended up writing the comment. Also if I were to write the same comment in any recent contest , you know what would have happened.
Yes, that is supposed to be a message that you should not do that (under a recent contest or otherwise).
If you're on an open wifi connection I'm pretty sure people can steal your CF username/password because CF isn't using HTTPS even in their login page.
https = http + slow