Keys Not Trusted Despite trust_mode Set to 1

[rfrederick]

The problem

When the key for a known user changes, the new key is marked as "UNTRUSTED" rather than "TRUSTED_UNVERIFIED" despite trust_mode for the account being set to 1 (AlwaysTrust).

The installs exhibiting this behavior are running in JSON-RPC mode. I haven't tested with other modes.

Are you using the latest released version?

• [X] Yes

Have you read the troubleshooting page?

• [X] Yes

What type of installation are you running?

signal-cli-rest-api Docker Container

In which mode are you using the docker container?

JSON-RPC Mode

What's the architecture of your host system?

x86-64

Additional information

No response

[lastfreeusernameicouldfind]

same problem here. I then tried to make the number trusted again with rest-api: /v1/identities/{number}/trust/{numberToTrust}. Calling this returns a 204. But the given number is still considered as UNTRUSTED when calling: /v1/identities/{number} What can I do to fix this? Can I maybe change some configuration files on disk to fix it? This problem makes signal-cli unusable for me. I just need to get this number trusted again. Please help. Thanks

[bbernhard]

Which mode are you using? If you are using the normal/native mode, then you need to call the receive endpoint afterwards. If you are using the json-rpc mode, then you could try to temporarily switch to the normal mode and try to trust it there.

[lastfreeusernameicouldfind]

I am using json-rpc. Meanwhile I got the number to TRUSTED_UNVERIFIED with executing /v1/identities/{number}/trust/{numberToTrust} and "trust_all_known_keys": true. Looks like without setting "trust_all_known_keys": true the /v1/identities/{number}/trust/{numberToTrust} does not work even though it returned 204.

Can I get rid of some identities listed in /v1/identities/{number}? Because I desperately did set "trust_all_known_keys": true they all trusted now but some of them shouldn't. Can I untrust individual identities or remove them completely?

[bbernhard]

Unfortunately, there seems to be no untrust implemented in signal-cli.