# zit 0.14.8

zit 0.14.8 fixes a clone, pull, push or sync whose account is named in the
URL: it sent a credential of its own making, unasked, and a private
repository answered as if it did not exist.

This release is from trunk. Stores, caches and the wire are unchanged from
0.14.7; nothing is rebuilt on upgrade.

## An account in the URL

`zit clone https://ACCOUNT@HOST/REPO` with the password in `ZIT_PASSWORD`
failed against a private repository with "the peer answered HTTP 404",
where `--user ACCOUNT` with the same password worked.

zit read the URL's user as the login, as it should. But the HTTP client
underneath also made an HTTP Basic header from the URL by itself and sent
it on the first request, with an empty password, before the server had
asked for anything. A forge in front of a private repository saw a sign-in
that failed, answered 404, and never sent the challenge that zit's real
credential answers. Each attempt counted as a failed sign-in on the
account.

The same header carried a password written in the URL
(`https://ACCOUNT:PASSWORD@HOST/`). zit's help says that password is never
read, and zit did not read it, but it was sent: on the first request,
without a challenge, and over plain `http` as well, which zit otherwise
refuses to send a Basic credential over. Upgrade if you have used a URL
with a password in it, and treat a password sent that way over `http` as
exposed.

Now nothing in the URL is sent as a credential. The URL's user names the
login, the password comes from `--password`, `ZIT_PASSWORD` or the prompt,
and the only Basic header on the wire is the one zit sends after the
server challenges for it. This applies to `clone`, `pull`, `push` and
`sync`.

## Qualification

The release manifest records native qualification against the exact tagged
source archive on macOS ARM64, Linux x86-64 and Linux ARM64, using the pinned
Zig 0.17.0 toolchain. Publication is gated on unit and end-to-end tests, Git
differentials, deterministic simulation, seeded fuzzing, and Fossil
interoperability checks on every distributed target.

For the basis of the conformance claim, see
[the 0.1.0 release notes](RELEASE-NOTES-0.1.0.md).
