And you do that by adding the school's CA certificate as a trusted one. So, for the SSL connection to work in the school, you need to consciously accept that "MITM" attack. When your browser tries to verify the school's provided cert against the CA that signed github's cert, it rightfully fails. Your school proxy is taking out github's cert and instead providing its own cert. To do that, what they do is in essence a "man in the middle" attack, and because of that, your browser complains rightfully that it is not being able to verify github's certificate. What is going on there is that your school is intercepting all the SSL communications, probably in order to monitor them. Let me explain what is going on also, so the other posters see why they don't need any certificate to use Github over HTTPS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |