[Bug]: atuin-update invalid peer certificate

[linickx]

What did you expect to happen?

I was previously running atuin 18.3.x and wanted to upgrade to 18.4.0 using atuin-update however it failed with the following.

╰─❯ atuin-update
Checking for updates...
  × error sending request for url (https://api.github.com/repos/atuinsh/atuin/releases): error trying to connect:
  │ invalid peer certificate: UnknownIssuer
  ├─▶ error trying to connect: invalid peer certificate: UnknownIssuer
  ╰─▶ invalid peer certificate: UnknownIssuer

What happened?

This system is behind an SSL Inspection MitM Proxy. Its an ubuntu box. To make apt, curl, etc work, the system has already been updated to support the custom CA, with the following.

root # cp Company_MitM_CA.crt /usr/local/share/ca-certificates/Company_MitM_CA.crt
root # update-ca-certificates

With this run, curl works, i.e. I have upgraded to 18.4 using this....

user $ curl --proto '=https' --tlsv1.2 -LsSf https://github.com/atuinsh/atuin/releases/download/v18.4.0/atuin-installer.sh | sh

I would like to be able to upgrade using atuin-update in future; how can I import the custom Certificate Authority into the atuin-update process?

Footnote: Currently my proxy admins are not inspecting api.atuin.sh but it is something that someone might face (or I might face) , and may need to import a CA for that as well, and of course make their own risk assessment around still wanting to sync or not, although the E2E might still make it ok 🤷🏻‍♂️

Atuin doctor output

N/A as not related to atuin binary.

Code of Conduct

• I agree to follow this project's Code of Conduct