Keeping keys synced between Ciphermail installations

Gateway
1

Hi,

I recently inherited two Ciphermail installations (for different tasks, so
with different config settings), which are keeping the (PGP + S/MIME) keys in
sync via ugly shell scripting. New keys can come in via either gateway.

Is there a "proper" way of doing this? It's not too bad with S/MIME once the
necessary CAs are on both boxes, but trust settings on PGP keys are a
different thing.

(I perused the docs and mailing-list archives, but found nothing appropriate.)

Kind regards,
Robert

···

--
// CERT Austria - Robert Waldner<waldner(a)cert.at>
// http://www.cert.at/ - T: +43 1 5056416 78
// Eine Initiative der nic.at GmbH
// http://www.nic.at/ - Firmenbuchnummer172568b, LG Salzburg

2

The CipherMail Gateway Pro/Ent edition can be setup in full
master/master HA mode. In master/master HA mode, changes done at one
gateway are immediately available on the other gateways.

Doing this with the community edition requires at least a database which
provides master/master clustering.

Kind regards,

Martijn Brinkers

···

On 02-06-2020 13:21, Robert Waldner via Users wrote:

I recently inherited two Ciphermail installations (for different tasks, so
with different config settings), which are keeping the (PGP + S/MIME) keys in
sync via ugly shell scripting. New keys can come in via either gateway.

Is there a "proper" way of doing this? It's not too bad with S/MIME once the
necessary CAs are on both boxes, but trust settings on PGP keys are a
different thing.

--
CipherMail email encryption
Email encryption with support for S/MIME,
OpenPGP, PDF encryption and secure webmail pull.

W: https://www.ciphermail.com/
E: info(a)ciphermail.com
T: +31 20 290 0088