Repository navigation
GHOSTWIRE v0.11.1
Passkeys now work in browsers that send extra extension data, and a failed passkey sign-in says why.
Changes
- Passkey sign-in. Some browsers return extension results that were never asked for, such as
appid, when signing in with a passkey. GHOSTWIRE refused these sign-ins, so a correctly set-up passkey or YubiKey was rejected, with "this passkey is not known here" when signing in with the passkey alone. Such results are now ignored, for the passkey alone and for a passkey as the second step after the password. - Clearer passkey errors. "this passkey is not known here" now appears only for a passkey that belongs to no user on this server, for example one left on a security key from an earlier installation. A known passkey that fails a check gets "the passkey was not accepted", and the log names the reason.
- Peer search by IPv6. The search on the Peers page also finds peers by their IPv6 address. The list itself still shows the IPv4 address only.
Update
Copy the binary for your server to it and run, as root:
chmod +x GHOSTWIRE-v0.11.1-linux-amd64
sudo ./GHOSTWIRE-v0.11.1-linux-amd64 updateServers on v0.10.0 or later show this release under Settings → Updates with the exact commands. For a new installation, run curl -fsSL https://ghostwi.re/install | sh.
Files
| File | For |
|---|---|
GHOSTWIRE-v0.11.1-linux-amd64 |
64-bit x86 servers |
GHOSTWIRE-v0.11.1-linux-arm64 |
64-bit ARM, e.g. Raspberry Pi OS 64-bit |
GHOSTWIRE-v0.11.1-linux-armv7 |
Raspberry Pi OS 32-bit |
SHA256SUMS |
checksums: shasum -a 256 -c SHA256SUMS |