task/website/src
Valentin Maerten dcebbd4ed4
fix(remote): refuse a redirect that drops TLS
The scheme was only checked on the URL the user wrote. A server answering
an https URL with a redirect to http was followed by the client without
any further check, so both the HEAD probe and the download travelled in
the clear, and a network attacker could substitute the Taskfile that is
about to be executed.

CheckRedirect now refuses an https to http hop. --insecure does not
loosen it: requesting an http entrypoint is the user's decision, being
sent to one is the server's. Setting CheckRedirect also replaces Go's
default cap, so the ten-hop limit is kept explicitly.

The three call sites turned almost every client error into a generic
download failure, which would have hidden the reason; TaskfileNotSecureError
is now passed through, with wording of its own for the redirect case since
--insecure is not a way out of it.
2026-11-05 21:34:02 +01:00
..
latest v3.54.0 2026-10-01 22:21:39 +02:00
next fix(remote): refuse a redirect that drops TLS 2026-11-05 21:34:02 +01:00
public v3.54.0 2026-10-01 22:21:39 +02:00
adopters.md feat(website): highlight big orgs / projects that use Task (#2803) 2026-04-22 10:02:06 +02:00
donate.md docs: improve public page accessibility and metadata (#3009) 2026-08-30 19:26:55 +02:00
index.md docs: redesign homepage (#3010) 2026-09-08 20:04:21 +00:00
team.md docs: improve public page accessibility and metadata (#3009) 2026-08-30 19:26:55 +02:00