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

https://download.servo.org/ expired cert. #14795

Closed
a-p- opened this Issue Dec 30, 2016 · 4 comments

Comments

Projects
None yet
5 participants
@a-p-

a-p- commented Dec 30, 2016

https://download.servo.org/ currently appears to be using a certificate that expired on Dec. 29, 2016.

@highfive

This comment has been minimized.

Show comment
Hide comment

highfive commented Dec 30, 2016

@chr4

This comment has been minimized.

Show comment
Hide comment
@chr4

chr4 Jan 3, 2017

Would it be possible to publish checksums of the files, so it's possible to verify the downloads in the meantime?

chr4 commented Jan 3, 2017

Would it be possible to publish checksums of the files, so it's possible to verify the downloads in the meantime?

@jdm

This comment has been minimized.

Show comment
Hide comment
@jdm

jdm Jan 4, 2017

Member

This is being tracked at servo/download.servo.org#12. Thanks for reporting it!

Member

jdm commented Jan 4, 2017

This is being tracked at servo/download.servo.org#12. Thanks for reporting it!

@jdm jdm closed this Jan 4, 2017

@aneeshusa

This comment has been minimized.

Show comment
Hide comment
@aneeshusa

aneeshusa Jan 4, 2017

Member

@chr4 That's a good idea, I've added a tracking issue at servo/download.servo.org#14. Unfortunately it's not very helpful without HTTPS, since a MITM could just rewrite the checksums to match any altered files. Since we publish nightlies for multiple platforms, that's too many files to publish checksums for in e.g. this thread.

Member

aneeshusa commented Jan 4, 2017

@chr4 That's a good idea, I've added a tracking issue at servo/download.servo.org#14. Unfortunately it's not very helpful without HTTPS, since a MITM could just rewrite the checksums to match any altered files. Since we publish nightlies for multiple platforms, that's too many files to publish checksums for in e.g. this thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment