New
- Settings → Certificate: give the console a certificate that browsers trust.
- Upload your own certificate (company CA or bought).
- Or get a free Let's Encrypt certificate, checked over port 80 or through a DNS record at Cloudflare. The DNS check also works for servers that are only in your network.
- The certificate is renewed automatically and switched without a restart.
- The browser extensions need a trusted certificate to connect.
- Connect the extension with only the server address: the extension opens the web vault. Sign in there once and click Connect. No password or code is typed in the extension.
- One click from WatchZit: Open with on a WatchZit device signs in with the login saved in PassZit, through the MaxZit Launcher. In the extension, click Allow on this console on the WatchZit page; only HTTPS consoles can be allowed. The console never receives a password.
- The Launcher page offers only the MaxZit Launcher (the same program as in WatchZit), with its installer when the WatchZit release has one.
Fixes
- deb/rpm packages: the self-signed certificate now names the server's IP addresses. Before, the service sandbox hid them.
- Restore instructions: they use
runuser, which minimal Debian systems have (they have nosudo). The guide explains how to get a new certificate when a restored server has another address. - Test servers can switch off the second factor with
PASSZIT_TEST_NO_2FA=yes. Every page then shows a warning. - Browser extension packages contain
LICENSEandTHIRD_PARTY_LICENSES.txt, generated from the actual dependencies.
