Change to http from https to work around Qualcomm IT SSL issues #390
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| ruby "3.2.3" | ||
|
|
||
| source "https://rubygems.org" | ||
| source "http://rubygems.org" |
Check failure
Code scanning / CodeQL
Dependency download using unencrypted communication channel High
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 11 months ago
The best way to fix the problem is to change the protocol of the source URL from HTTP to HTTPS. This ensures that the communication channel used to download the dependencies is encrypted, protecting against potential MITM attacks.
To implement this fix, we need to modify the Gemfile to use the HTTPS protocol for the source URL. Specifically, we will change the line source "http://rubygems.org" to source "https://rubygems.org".
| @@ -4,3 +4,3 @@ | ||
|
|
||
| source "http://rubygems.org" | ||
| source "https://rubygems.org" | ||
|
|
…l-certificate-failure
|
I'm getting this Code scanning result (CodeQL) failing in the smoke test. How do we handle this? We intentionally changed from https to http.
|
|
I think we determined this was a configuration issue with your machine. Re-open if I'm mis-remembering. |
james-ball-qualcomm
deleted the
388-cant-install-python-into-devcontainer-ssl-certificate-failure
branch
Still need a fix for Python.