You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding the options --secure-protocol=TLSv1_2 as suggested in that discussion worked. Presumably a newer wget could work too. We could run our fetch scripts from a docker to potentially get around this, but then it must be kept up to date with the latest ssl standards.
Simplest option might be to detect wget failures, and retry error 403 with specifying this TLS version?
The text was updated successfully, but these errors were encountered:
https://github.com/orgs/community/discussions/65227
This was reproduced in:
Task: DS_COMPONENT_WILC3000_FIRMWARE (host) 6/38: Installing WILC3000 firmware
--2023-08-28 16:04:58-- https://github.com/linux4wilc/firmware/archive/refs/tags/wilc_linux_16_1.tar.gz
Resolving github.com (github.com)... 140.82.114.4
Connecting to github.com (github.com)|140.82.114.4|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/linux4wilc/firmware/tar.gz/refs/tags/wilc_linux_16_1 [following]
--2023-08-28 16:04:59-- https://codeload.github.com/linux4wilc/firmware/tar.gz/refs/tags/wilc_linux_16_1
Resolving codeload.github.com (codeload.github.com)... 140.82.114.9
Connecting to codeload.github.com (codeload.github.com)|140.82.114.9|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2023-08-28 16:04:59 ERROR 403: Forbidden.
Running this on the host would reproduce it:
wget https://github.com/linux4wilc/firmware/archive/refs/tags/wilc_linux_16_1.tar.gz
Adding the options
--secure-protocol=TLSv1_2
as suggested in that discussion worked. Presumably a newer wget could work too. We could run our fetch scripts from a docker to potentially get around this, but then it must be kept up to date with the latest ssl standards.Simplest option might be to detect wget failures, and retry error 403 with specifying this TLS version?
The text was updated successfully, but these errors were encountered: