CS 189: Introduction to Machine Learning
eecs189.org
CS 189: Introduction to Machine Learning
1–10 of 24 posts
Re: CS 189: Introduction to Machine Learning
#2The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
Re: CS 189: Introduction to Machine Learning
#3The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
shit like this makes me die a little bit on the inside.
Re: CS 189: Introduction to Machine Learning
#4The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
You're right.
I looked into this a little further. The data is encrypted with Github's private key (thus decrypted with their public cert). I then wondered how he got a copy of Github's private key...but as it turns out, the IP does belong to Github.
In either event, definitely misconfigured, but I added an exception as it all seems legit in the end. It looks like he's just hosting his site (with his own DNS) on github's server and didn't get an ssl cert yet.
Re: CS 189: Introduction to Machine Learning
#5The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
You're right. I looked into this a little further. The data is encrypted with Github's private key (thus decrypted with their public cert). I then wondered how he got a copy of Github's private key...but as it turns out, the IP does belong to Github. In either event, definitely misconfigured, but I added an exception as it all seems legit in the end. It looks like he's just hosting his site (with his own DNS) on gith…
disclaimer: i work for berkeley EECS, but have no association w/these faculty or class.
TL;DR: they probably wanted to save some money by not paying our instructional group to do the hosting, and instead are (most likely) paying github for hosting. because they're doing this themselves, it means that things like real, working SSL certs are their responsibility, and most likely were "too hard" or would take "too long" to set up properly.
¯\_(ツ)_/¯
Re: CS 189: Introduction to Machine Learning
#6The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
Weird, this shouldn't happen. If you set GitHub's certificate up correctly it should work. I'm assuming they never set up HTTPS at all, but someone linked to HTTPS here anyway?
Re: CS 189: Introduction to Machine Learning
#7The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
>try to visit site
>immediately get certificate warnings
hilarious
Re: CS 189: Introduction to Machine Learning
#8The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
Strange, GitHub Pages should support TLS on custom domains: https://blog.github.com/2018-05-01-github-pages-custom-domai...
Looks like the site is using a wrong IP for the A record. It is 192.30.252.153, but should be 185.199.108.153, where Let's Encrypt is enabled.
Re: CS 189: Introduction to Machine Learning
#9Earlier quoted context omitted.
You're right. I looked into this a little further. The data is encrypted with Github's private key (thus decrypted with their public cert). I then wondered how he got a copy of Github's private key...but as it turns out, the IP does belong to Github. In either event, definitely misconfigured, but I added an exception as it all seems legit in the end. It looks like he's just hosting his site (with his own DNS) on gith…
disclaimer: i work for berkeley EECS, but have no association w/these faculty or class. TL;DR: they probably wanted to save some money by not paying our instructional group to do the hosting, and instead are (most likely) paying github for hosting. because they're doing this themselves, it means that things like real, working SSL certs are their responsibility, and most likely were "too hard" or would take "too long"…
Github is free for open source
Re: CS 189: Introduction to Machine Learning
#10Earlier quoted context omitted.
disclaimer: i work for berkeley EECS, but have no association w/these faculty or class. TL;DR: they probably wanted to save some money by not paying our instructional group to do the hosting, and instead are (most likely) paying github for hosting. because they're doing this themselves, it means that things like real, working SSL certs are their responsibility, and most likely were "too hard" or would take "too long"…
Github is free for open source
The whole hosting package wasn't always