-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Prefer https #30826
Prefer https #30826
Conversation
Isn't HTTPS safer in case of man-in-the-middle attacks; and should thus be preferred in all cases I see HTTP used? At least here (confirmed file is available either way). Some counterpoint I can think of is, if HTTPS breaks, you don't get the file that way (you'll get an exception and know?). I'm not sure it's a good reason here to avoid HTTPS, even with this only for a test. Seems the alternative is the testing infrastructure could be compromised. |
I looked for other cases: https://github.com/JuliaLang/julia/search?q=http&unscoped_q=http Also in Vagrant file (on page 1) and doc/Makefile and at least one .sh file (I do not feel like going through all 10 pages, mostly just for http in comments). And there are e.g. http://httpbin.org/ip (doesn't seem important). and for "issue 8278" Line 25 in c9e5a6a
there the interesting case of the image search for "apartheid wall in palestine"...: |
Keeping the If you want to add changes for the Vagrantfile, I'll be happy to take a look at that too. |
Should we have a checksum for the |
That executable can change at any time; it's not versioned. We should probably host our own version, add a checksum, and use that URL instead (with HTTPS). |
I changed all three but only confirmed links for other two [now three], not: julia/contrib/windows/Vagrantfile Line 16 in c446444
At least https://mirrors.kernel.org/sourceware/cygwin/ works so all links to that host should also work. |
This looks good to me for now, it's clearly an improvement. We should move toward versioned, hash-checked downloads for pretty much everything, I'll open an issue to track that independent of this PR. |
With my seemingly trivial change passing on Linux, I believe the macOS CI fail is a false alarm, for something entirely unrelated and this PR should just be merged:
|
Bump. Just merge as CI false alarm "Probably a temporary connection problem"? |
Yep. Thanks! |
No description provided.