While I do love your optimism and appreciate the addition of this software to our (collective) arsenal, it absolutely can. Chat Control can force the developers to add back doors, for example, or to start log collection to include IPs and PSPs, etc. Please don’t misunderstand, I’m not negating the benefits of Amnesichat at all. It’s awesome. But, being a chat, it would still fall under the same regulatory nonsense as Briar, for example, which can also be run through Tor. Now, whether the developers adhere to Chat Control regulations, is another thing altogether.
If a backdoor is forced to be added into any project, wouldn’t someone be able to fork it and go on without the backdoor? Maybe even the original dev incognito…
Theoretically, yes. But if it’s a legal entity that added it, they can easily circumvent any attempt to eradicate it. Or, in a more extreme way, criminalize FOSS chat apps altogether, then the code will have to be analyzed in a RE environment. Maybe the non FOSS server code is where the backdoor is added. There are so many relatively hidden ways to compromise a chat app’s supply chain.
I doubt any FOSS restriction is doable at all. As for the supply chain - xz showed this is indeed possible… But no one can guarantee that every encrypted client would be able to get such a well-hidden backdoor, and that it will stay undiscovered, and that it wouldn’t be invalidated with an update… But yeah, the only way this can be combatted is having more eyes on such software.
Chat Control will not affect this chat if it’s source code and public instance are hosted in darknet ;)
While I do love your optimism and appreciate the addition of this software to our (collective) arsenal, it absolutely can. Chat Control can force the developers to add back doors, for example, or to start log collection to include IPs and PSPs, etc. Please don’t misunderstand, I’m not negating the benefits of Amnesichat at all. It’s awesome. But, being a chat, it would still fall under the same regulatory nonsense as Briar, for example, which can also be run through Tor. Now, whether the developers adhere to Chat Control regulations, is another thing altogether.
If a backdoor is forced to be added into any project, wouldn’t someone be able to fork it and go on without the backdoor? Maybe even the original dev incognito…
Theoretically, yes. But if it’s a legal entity that added it, they can easily circumvent any attempt to eradicate it. Or, in a more extreme way, criminalize FOSS chat apps altogether, then the code will have to be analyzed in a RE environment. Maybe the non FOSS server code is where the backdoor is added. There are so many relatively hidden ways to compromise a chat app’s supply chain.
I doubt any FOSS restriction is doable at all. As for the supply chain - xz showed this is indeed possible… But no one can guarantee that every encrypted client would be able to get such a well-hidden backdoor, and that it will stay undiscovered, and that it wouldn’t be invalidated with an update… But yeah, the only way this can be combatted is having more eyes on such software.
I would never comply with Chat Control
Honestly, neither will I. No one should.