Skip to content

https downloads #5437

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NicoHood opened this issue Oct 3, 2016 · 3 comments
Open

https downloads #5437

NicoHood opened this issue Oct 3, 2016 · 3 comments
Labels
feature request A request to make an enhancement (not a bug fix)

Comments

@NicoHood
Copy link
Contributor

NicoHood commented Oct 3, 2016

A lot of link/downloads in the source do use http for download while a secure https is available instead.
Those files can be found for example via github:
https://github.com/arduino/Arduino/search?utf8=%E2%9C%93&q=http%3A%2F%2F

Most important are the sources in build.xml:
https://github.com/arduino/Arduino/blob/master/build/build.xml

And also the avr cores:
https://github.com/arduino/Arduino/blob/master/hardware/package_index_bundled.json

Since arduino has https encryption you could possibly replace verything starting with http://www.arduino.cc with https. That would cover most links and would not break anything.

@cmaglie
Copy link
Member

cmaglie commented Oct 3, 2016

All files downloaded from build.xml or from json indexes are verified with checksums (sha/sha256).
Changing everything to https will increase the servers load without any improvement in security.

Maybe there are some places where using https will improve security but this is not in build.xml or inside the indexes.

@NicoHood
Copy link
Contributor Author

NicoHood commented Oct 3, 2016

Its not about integrity, its about confidentiality (but still happy to see that some people understand the meaning of integirty finally =) ).

I personally do not want everyone to see what I download, no matter if its "just" arduino or not. I am not sure about sever loads, but https is the (... not future, actually the past) ... its time to use https. The server should be able to handle such downloads.

@NicoHood
Copy link
Contributor Author

Please conside the switch to https. Archlinux now switched every possible source to https and gpg signatures. And if i am right debian also has a policy about that:
https://www.archlinux.org/todo/use-gpg-signatures-and-https-sources/

Here is what google thinks about https:
https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https

Everything is already covered in this PR:
#5438

And the gpg signing is tracked here:
#5619

@per1234 per1234 added the feature request A request to make an enhancement (not a bug fix) label Mar 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request A request to make an enhancement (not a bug fix)
Projects
None yet
Development

No branches or pull requests

3 participants