New identities still get "UNTRUSTED" status after changing trust_mode to "always"

[gb-0099]

The problem

I changed the trust_mode from "on-first-use" to "always" using the API. Now when I GET '/v1/configuration/{number}/settings' I see {"trust_mode":"always"}.

But group members who change devices or otherwise re-install Signal are still getting an "UNTRUSTED" status on their new identities (verified with call to /v1/identities/{number}), making the bot account unable to receive their messages.

Are you using the latest released version?

• Yes

Have you read the troubleshooting page?

• 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

[bbernhard]

It looks like that this was never implemented for the json-rpc mode. Due to the way the json-rpc mode works, it doesn't make much sense to expose that setting via the configuration/{number}/settings endpoint. Instead, I've added a new env variable called JSON_RPC_TRUST_NEW_IDENTITIES which can be set to always.

If you want to give it a try, you can use this docker image: bbernhard/signal-cli-rest-api:1765233217-ci

[gb-0099]

Amazing, thanks. I won't be able to test immediately but can post here once I do.

[gb-0099]

Scratch that, I can't actually test this with the signalbot framework I'm using because of an unhandled packaging.version.InvalidVersion: Invalid version: 'unset'

https://github.com/filipre/signalbot/blob/614647dd423f5f01f0475f4f78f29c5fffbbae20/signalbot/bot.py#L184

[bbernhard]

I guess you could disable that check manually for now by changing the Python code.

[gb-0099]

Okay I tried that and it looks good. A safety number changed and the identity status is trusted.