Skip to content

EmailZit 0.11.1

Choose a tag to compare

@stefanzeljkic stefanzeljkic released this 15 Nov 12:25
· 23 commits to main since this release

A security release: the public DNS, not another server, decides what the relay and a domain are allowed to do.

The HostZit team read the code of 0.11.0 and ran joint tests with two HostZit and two EmailZit servers in a lab. Six findings came back, all of them the same mistake in different places: EmailZit trusted what the other server said instead of what the DNS shows. This release answers all six. Servers that run both products for their own customers see no difference; a server that links a HostZit of a client gets the fences it was missing.

Changes

  • A zone inside HostZit is no longer a proof of a domain. Any hosting account can create a zone for a name that is not theirs, and such a zone does nothing in the public DNS. EmailZit now writes the verification record into the zone as well and verifies the domain only from the public DNS, at the name servers of the domain itself — right after the write and once an hour. A HostZit that really holds the delegated zone makes the record visible in seconds, so nothing changes for honest customers. The same rule now decides the DKIM signing: a domain is signed when its record really is in the DNS, not when HostZit accepted it.
  • Websites of a linked HostZit may only send with domains that are proven. A domain that has mailboxes here is accepted only when the HostZit of that relay login hosts the domain as well, for the same customer; a customer an administrator assigned to the link by hand needs no such question. A domain that has no mail here must show the record EmailZit asked that HostZit to publish in the public DNS: while it is not visible the answer is 451 (the website's message waits in its queue), afterwards 550, and a proof counts for seven days. Each link has to make its own record appear, so one HostZit can neither pass with the record of another nor take its proof away.
  • A relay login works only from the addresses of its own link. The port is open for the addresses of all linked HostZit servers together, so without this the login of one hosting server could be used from another.
  • The scope of a new link belongs to the pairing code. Settings → HostZit → Make a pairing code asks which customers the new link serves, and the link has that from its first second — a HostZit never sees more than the administrator meant, not even in the seconds between the pairing and a change on the settings page. The first link of a server starts at "all customers"; with a link already there, a new link (also one added by hand) starts with none until its customers are chosen. Pairing again with a server that is already linked leaves its customers alone.
  • The records of a domain that no HostZit holds are offered again every six hours, so a zone created later, or a write that was refused while something else was in the way, is picked up without anybody clicking.
  • The DKIM check asks the system resolver when a name server of the domain answers the test question and then refuses the record itself — one such name server used to leave the check undecided for ever.
  • The guide says in all 14 languages how a domain verifies itself from the public DNS, what the pairing code decides, and what the relay demands.

Install or update

curl -fsSLO https://github.com/Max-Zit/emailzit/releases/download/v0.11.1/install.sh
sudo sh install.sh --hostname mail.example.com

Existing servers update from the panel (Updates and server). Appliance images are attached below (check them against SHA256SUMS-appliance).

Thanks to the HostZit team for the review and the joint tests.