fix: use system SSL context in install.py to avoid self-signed certificate errors (closes #28044)#33790
Conversation
…icate errors (closes Azure#28044)
|
Hi @botbikamordehai2-sketch, |
|
Hi @botbikamordehai2-sketch, |
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
@botbikamordehai2-sketch please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
@botbikamordehai2-sketch please reply comments from microsoft-github-policy-service |
| print_status("Downloaded virtualenv package to {}.".format(download_location)) | ||
| if is_valid_sha256sum(download_location, VIRTUALENV_ARCHIVE_SHA256): | ||
| print_status("Checksum of {} OK.".format(download_location)) | ||
| print_status("Checksum of {} OK.".format(download_location))ad_location)) |
|
Is this a duplicate of #30468 ? |
What
When running
az bicep installon corporate machines with self-signed root certificates, SSL verification can fail becauseurlopendoes not use the system's certificate store by default. This leads to the error:Fix
Modified
create_virtualenvto usessl.create_default_context()when making HTTPS requests, which respects the system's certificate store (including corporate certificates installed in the Windows cert store). This change is minimal and preserves backward compatibility.Closes #28044