From 183d7629758f85c7319867eabb8d86eaf155e898 Mon Sep 17 00:00:00 2001
From: IUCCA <33322841+IUCCA@users.noreply.github.com>
Date: Thu, 16 Jun 2022 00:52:37 +0200
Subject: [PATCH] Auto trust new signal identities

from signald doku: when a remote key changes, set trust level to TRUSTED_UNVERIFIED instead of UNTRUSTED
I find it much more convenient when new identities are automatically recognized as trusted, as the process to do that manually is cumbersome.
Should this the default behavior, or should i add an option to configure this behavior?
---
 .../templates/systemd/matrix-mautrix-signal-daemon.service.j2    | 1 +
 1 file changed, 1 insertion(+)

diff --git a/roles/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal-daemon.service.j2 b/roles/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal-daemon.service.j2
index 0ee05d7d7..4ee878805 100644
--- a/roles/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal-daemon.service.j2
+++ b/roles/matrix-bridge-mautrix-signal/templates/systemd/matrix-mautrix-signal-daemon.service.j2
@@ -24,6 +24,7 @@ ExecStartPre={{ matrix_host_command_sleep }} 5
 # We can't use `--read-only` for this bridge.
 ExecStart={{ matrix_host_command_docker }} run --rm --name matrix-mautrix-signal-daemon \
 			--log-driver=none \
+			--env SIGNALD_TRUST_NEW_KEYS=true \
 			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
 			--cap-drop=ALL \
 			--network={{ matrix_docker_network }} \