Skip to content
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

Update guide.md #16222

Closed
wants to merge 1 commit into from
Closed

Update guide.md #16222

wants to merge 1 commit into from

Conversation

brycefisher
Copy link

Encourage users to access rustup.sh over HTTPS from github.com not HTTP from www.rust-lang.org. See #16123 for details

Encourage users to access rustup.sh over HTTPS from github.com not HTTP from www.rust-lang.org
@steveklabnik
Copy link
Member

This is not the proper fix for this. The proper fix is #16123

@brycefisher
Copy link
Author

Agreed -- this is definitely a workaround. However, shouldn't we encourage users to only access rustup.sh over HTTPS? It's very scary to give root to untrusted content provided over HTTP.

@sfackler
Copy link
Member

sfackler commented Aug 3, 2014

I don't see how this would solve the problem. You'll still be pulling the nightly binaries down over HTTP and running the a script in that tarball.

@steveklabnik
Copy link
Member

That is also true.

@brycefisher
Copy link
Author

Right! I didn't think about the underlying binaries... Closing PR.

@brycefisher brycefisher closed this Aug 3, 2014
@brycefisher brycefisher deleted the patch-1 branch August 3, 2014 21:20
lnicola pushed a commit to lnicola/rust that referenced this pull request Jan 3, 2024
…, r=Veykril

add unresolved-assoc-item assist

I tried to copy from private-assoc-item for this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants