Skip to content

PassZit 0.9.6

Choose a tag to compare

@stefanzeljkic stefanzeljkic released this 10 Nov 18:31

Server and appliance 0.9.6 with the browser extension 0.9.5 (in review in the Chrome Web Store, Firefox Add-ons and Microsoft Edge Add-ons; the stores update installed extensions when it is approved).

Browser extension 0.9.5

  • Firefox with a server on its own port: with a server or a MaxZit console on a port such as 8443, "Connect with the web vault" stopped at "The PassZit extension does not answer on this page", and "Open with" from WatchZit did nothing. Firefox ignores permissions that name a port; PassZit now asks for the server's name without the port and still talks only to the exact address you entered. Chrome, Edge and other browsers keep working without a new question.
  • No offer to save what is saved already: a login captured while PassZit was locked (for example the sign-in on the PassZit page itself) is checked again once PassZit is unlocked — the same login is no longer offered, a new password is offered as an update.
  • Cards and addresses: on payment and shipping pages, Cards and addresses in the PassZit window fills the name, address, e-mail and phone of an identity, or the cardholder, number, expiry and security code of a card (after a question). Only empty fields, only on encrypted (HTTPS) pages and only in the page itself, never in frames of other sites.
  • Passphrases: the four words of the EFF list with a hyphen are replaced, so a passphrase always splits back into its words.

Server

  • Shared vaults always keep a manager: taking people out of a group or deleting a group is refused when a shared vault would be left without a manager; the group page warns beforehand. When the company directory makes such a change, it still happens, is written to the audit log and the administrators get an e-mail.
  • Appliance: the login screen and the setup menu show the console's real port (none for 443) instead of always 8443.
  • Web vault: no stray "null" text next to vault rights, in the Tools menu and under item documentation.

Testing

The extension is now also tested like a user does it: the store build in real Firefox, without permissions, against a server on HTTPS on its own port — popup, web vault sign-in, connect. The extension tests run in Chrome, Edge and Firefox. Before this release: Semgrep, Trivy, Gitleaks, an OWASP ZAP scan of a fresh appliance, role probes and a crawl of every page, and a scan of the appliance image (Trivy, Lynis, testssl.sh, Nuclei). See SECURITY.md.