Zammad 3.4.0 & 3.3.1

Zammad Team
Mon, 15 Jun 2020 15:40:00 +0200

We are pleased to release Zammad 3.4. This is also a Security-Release.

Zammad 3.4.0 (minor) & 3.3.1 (patch)

1: 🔏 S/MIME Integration

Email just got a serious upgrade. If your business needs industry-standard, guaranteed privacy and authenticity for its digital communication, S/MIME is the way to go—and it’s available in Zammad today.

Decrypt messages that were meant for your eyes only, and encrypt your outgoing mail so that only the intended recipient can read it. Digital signatures prove that the messages in your inbox haven’t been tampered with; S/MIME can verify these signatures on your incoming mail or add them to the messages you send out to others.

How does it work?

You and the people you communicate with will need S/MIME certificates, usually from a commercial certificate authority (CA). Add these certificates in the admin panel under System > Integrations > S/MIME to get started.

📣🎊🎈 Thank you to our feature sponsor, Barzahlen/viacash!

Barzahlen/viacash (a.k.a. Cash Payment Solutions GmbH) is Europe’s largest bank-independent payment system, and their customer service runs entirely on Zammad. Pay your bills or online purchases 💸 in cash 💸 at your nearest Penny, REWE, or one of over 16,000 other retail stores in your area. You can even make deposits and withdrawals at online banks such as DKB, N26 or Bunq.

Barzahlen/viacash made the switch to Zammad from OTRS in May 2018, and just became our newest feature sponsor. With the help of their financial support and invaluable insight, this long-awaited feature is finally a reality.

Now, thanks to Barzahlen/viacash, the entire Zammad community can enjoy industry-standard privacy and authenticity in their email correspondences.

2: 🛡 Google OAuth Integration

As early as 2019, Google announced that it was planning to disable traditional password authentication for third-party mail clients (like Apple Mail, Outlook, Thunderbird, and of course, Zammad) in favor of the more secure OAuth protocol. Thankfully, these changes haven’t taken effect yet, as many mail clients have yet to introduce support for OAuth.

With the release of version 3.4, Zammad users can rest assured knowing that OAuth support is here and ready to go. You don’t have to wait for Google to shut down password auth to migrate; make the switch to OAuth today.

How does it work?

Step 1: Register an “app” with Google and integrate your mailbox into Zammad. More information can be found in the documentation.

Step 2: Add your newly created Google App in the admin panel under Channels > Google Accounts.

3: 💬 Zammad + ServiceNow = 💘

ServiceNow is an ITSM solution with email integration (like Zammad).

In the past, the two services didn’t play well together: ServiceNow strips crucial email headers from outgoing messages, so Zammad couldn’t tell the difference between a follow-up and a new ticket. This meant that Zammad’s only choice was to create a new ticket for every single email from ServiceNow.

Now, Zammad features special detection logic to help it figure out when an email from ServiceNow belongs to an existing ticket. Pretty handy!

How does it work?

There’s no need to enable or set up this feature—it works out of the box.

📣🎊🎈 Thank you to our feature sponsor, Adfinis !

Drumroll for another highly appreciated feature sponsor, Adfinis! Adfinis is one of Europe’s largest IT & open-source technology service providers. Thanks to their support, Zammad and ServiceNow work together better than ever before.

4: Security vulnerabilities

After the major security audits of Zammad 3.3, we took the opportunity to dig in a little deeper ourselves. Thanks to additional support from the community, we’re proud to report that we’ve identified and fixed two more vulnerabilities in Zammad.

Hosted users: Your instance has been automatically updated already. No action on your part is required.

Self-hosted users: We recommend that you update your installations immediately.

The following Security Advisories have been addressed in this release.

ZAA-2020-12 Unverified Customer can self-assign to unauthorized Organization (CVE-2020-14214)

ZAA-2020-13 Authorization issue allows Customer to see internal Ticket information (CVE-2020-14213)

Technical Notes (for self-hosted users)

An installation package for Ubuntu 20.04 LTS is available.

Zammad 3.4 requires Elasticsearch 5.6+. Users upgrading from Zammad 3.3 do not have to reindex.

Zammad 3.4 requires Ruby 2.6.5. Users installing from source must prepare their systems accordingly.

Downloads

All improvements can be found in the changelog.

Download Zammad 3.4.0

Changelog (2020-06-15)

Source code

https://ftp.zammad.com/zammad-3.4.0.tar.bz2 (md5:e9a39ca9aa6e1095429ad5c7c5736fd1)

https://ftp.zammad.com/zammad-3.4.0.tar.gz (md5:fb8dd4d88d5ee52f6ab0d137497936e8)

https://ftp.zammad.com/zammad-3.4.0.zip (md5:df00afbec1b9723d44a8c198be4d568b)

Download Zammad 3.3.1

(link: https://github.com/zammad/zammad/blob/3.3.1/CHANGELOG.md text: Changelog (2020-06-15)

Source code

https://ftp.zammad.com/zammad-3.3.1.tar.bz2 (md5:b3d673112ba687e9eed8647b9800d88e)

https://ftp.zammad.com/zammad-3.3.1.tar.gz (md5:5d38beeffaecff2ade0266666b54a321)

https://ftp.zammad.com/zammad-3.3.1.zip (md5:20c87f83de25eda53f27bd50558ebdb7)

Packages

CentOS: https://docs.zammad.org/en/latest/install-centos.html

Debian: https://docs.zammad.org/en/latest/install-debian.html

Ubuntu: https://docs.zammad.org/en/latest/install-ubuntu.html

Docker-Compose: https://docs.zammad.org/en/latest/install-docker-compose.html

Upgrade

Information about upgrading a Zammad installation can be found here:

From source: https://docs.zammad.org/en/latest/install-update.html#source-update

With RPM: https://docs.zammad.org/en/latest/install-update.html#update-with-rpm

With DEB: https://docs.zammad.org/en/latest/install-update.html#update-with-deb

Your Zammad team!