I took this course last year with Professor Shewchuk. It was excellent.
CS 189: Introduction to Machine Learning
11–20 of 24 posts
Re: CS 189: Introduction to Machine Learning
#12this works fine over http instead of https. is there a way to fix the link?
Re: CS 189: Introduction to Machine Learning
#13Earlier 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
point.
Re: CS 189: Introduction to Machine Learning
#14Took this class with Prof. Sahai last semester when they redesigned the syllabus. I would recommend to anyone who wants to understand ML with some math rigor. The class notes: http://snasiriany.me/files/ml-book.pdf is excellent. The hw problems are pretty fun too
Re: CS 189: Introduction to Machine Learning
#15The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
Link without https works: http://www.eecs189.org/
Re: CS 189: Introduction to Machine Learning
#16The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
Whoever set this up should have taken Introduction to Web Security first
Re: CS 189: Introduction to Machine Learning
#17The 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…
> The data is encrypted with Github's private key (thus decrypted with their public cert).
I don't think that's how it works, because then anyone could decrypt the data since the decryption key is public.
Rather, I think how asymmetric crypto works is you pass your public key to them so they can encrypt stuff with it and send it to you to decrypt with your private key. Then, to send stuff to them, you use their public key to encrypt the data for them so they can decrypt with their private key. That said, I think TLS works differently by using asymmetric crypto only to negotiate a symmetric key for the actual encryption of data.
EDIT: made wording more precise
Re: CS 189: Introduction to Machine Learning
#18The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
When Github enabled https for sites hosted on Github Pages, sites that were using custom domains went from redirecting https->http to giving certificate errors overnight. This happened to me. I didn't get a notification; the only way I found out what happened was by reading the Github blog. The blog post has a fix but it requires action by the site owner.
Re: CS 189: Introduction to Machine Learning
#19The SSL certificate used here does not match the domain name as it is Github's wildcard certificate.
If you want to use https with github and a custom domain you need to use either Cloudflare flexible SSL or with a domain host that allows ANAME or a flattened Cname... https://kolemcrae.com/Moving-To-GitPages/
Re: CS 189: Introduction to Machine Learning
#20Earlier 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"…
thanks for sharing... It's crazy that Berkeley (such an awesome institution) has come to this... The US/CA govt's owe it to the university to increase funding.