Bug 4959 - tlclient.conf UPDATE_URL only supports HTTP; not HTTPS
Summary: tlclient.conf UPDATE_URL only supports HTTP; not HTTPS
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2014-01-13 12:40 CET by Peter Åstrand
Modified: 2023-08-29 19:11 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2014-01-13 12:40:34 CET
The automatic update feature works by retrieving the URL pointed out by UPTDATE_URL. This must currently be a HTTP URL. If you try to use HTTPS, you will get a failure and a not very obvious error message. With:


...I get:

2014-01-13T12:39:54: Unable to retrieve update configuration: Could not parse response status line

We should consider support HTTPS or at least improve the error message.
Comment 1 Pierre Ossman cendio 2014-01-14 11:45:16 CET
One major issue is the whole mess with certificates. Who to trust, how this list should be maintained and what to do when the certificate doesn't match.

One easy solution is to have to provide the trusted CA certificates to tlclient. None of the major ones will be trusted by default. In order for the updates to work out-of-box for us, we will have our own (self-signed) CA for a special domain, e.g.:


That way we can make sure we get a trusted transfer of the file and still have the freedom to chose any certificate provider for our normal www.cendio.com site.

Customers might run in to the same issue though. If they want to ship clientupdate.conf from the same domain as the actual updated exe/rpm/deb, then they'll have to add that well known CA to the list of CAs that tlclient trusts.
Comment 3 Pierre Ossman cendio 2023-06-16 13:49:50 CEST
For reference, these are the locations that Go seems to search for a certificate store on Linux:


Note You need to log in before you can comment on or make changes to this bug.