France bans ministers from WhatsApp, Signal; demands French alternatives
France bans ministers from WhatsApp, Signal; demands French alternatives
www.politico.eu
France bans ministers from WhatsApp, Signal; demands French alternatives
55 comments
-
the entire government will be using [Olvid], the world's most secure instant messaging system," French digital minister Jean-Noël Barrot confirmed on X.
Clearly they're very discerning when it comes to their choice of communication apps. 🙄
-
From their Google play store page: "Olvid is the first private instant messaging application for everyone."
-
At least it's open source, so we should know soon enough how it compares to Signal
-
the client is open source. but the server? not so much.
in any case, if security is the concern... they should probably switch to a government-built system that only runs on gooberment devices. Will it be shitty? absolutely. But data is owned by whoever has the hardware it sits on. if it's not your device its not your data.
-
No trust in servers Persistent security even in case of a compromised server
From Olvid website
They are advertising the fact that the security does not depend on the server.
I don't know what is worth.
Also it's developed by a French company, I think this is the main argument for the French government, they want to have options that does not rely on US companies.
-
Without the server-side code there’s no way to validate that. (This is the reason open source is preferred.)
It’s definitely being selected because it’s French. (And has all the buzzwords,)
-
You've misunderstood. With the client code you can be sure that your messages are properly encrypted before leaving the device. If that's done correctly, you don't need to trust the server, because it can't read your messages just like some attacker couldn't. Signal is pretty similar, they didn't update the public server source for a few years, and even with the source, we can't know that that is what they're actually running. But with a verified build of the client code we can know that our messages are encrypted such that, even if they held on to them until quantum computers became mainstream, they'd still be properly protected.
-
the server can store metadata though. who you're texting, when, how often, etc. - and store that indefinitely. or even store the encrypted message, and when a flaw in the encryption is discovered 10 years later, they're all readable. their servers could be breached and that info could be siphoned by criminals selling it to the highest bidder.
signals blog had an interesting post about what they're doing to prevent these issues
-
You’ve misunderstood. With the client code you can be sure that your messages are properly encrypted before leaving the device. If that’s done correctly, you don’t need to trust the server, because it can’t read your messages just like some attacker couldn’t.
It kind of depends on how keys are handled. If the key passes through their servers at all (and it probably does,) then they have access to the keys and sufficient information to decrypt it. it's possible the app does send keys independent of their server- I don't know- but I very much doubt it. if they were capable of sending keys without a server, chances are very good they don't actually need the server for the messages themselves. (which would then ask why they do have a server.)
But with a verified build of the client code we can know that our messages are encrypted such that, even if they held on to them until quantum computers became mainstream, they’d still be properly protected.
Assuming they don't have the keys. This is not a valid assumption so far as I'm aware.
-
It should most definitely be a valid assumption.
If the key passes through their servers at all (and it probably does,) then they have access to the keys and sufficient information to decrypt it. it's possible the app does send keys independent of their server- I don't know- but I very much doubt it.
The keys shouldn't be on or go through a server anywhere, that would be an absolute joke.
What makes you think that private keys are being sent anywhere? This app uses a slightly modified version of the Signal protocol (because of course it does), as they describe here, section 27, page 90. Only public keys should ever leave your device, otherwise no amount of showing the code would make it secure. That's the whole point.
Again, with the client code you should be able to tell that the keys are generated there and not sent anywhere.
As I said, with any app, just because they publish some server code does not mean that that's what they're running on their server - for security you have to be sure that the app is sufficiently secure on its own. Even if they were running the exact public code that "didn't save the keys" the server could harvest them from memory.
-
Again, with the client code you should be able to tell that the keys are generated there and not sent anywhere
then no one- including the intended recipient- can decode them without that physical device. kinda defeats the point of a messenger service. The codes have to be sent somehow. Either it's sent along their servers, or the recipient's device directly.
I really don't care to get into it. Just know that if you're using a generic, stock device... any message you send should be considered compromised. depending on the app, and the device in question, it may (but not necessarily) require physical access to the device. but, by it's very nature, the messenger service meant to be decoded and read. it is fundamentally permissive in nature.
Is it secure enough for France's needs? Probably. does it mean it's the best? Probably not.
-
You seem to be a bit confused about how asymmetric encryption works. There is no need for private keys to be transmitted for a messaging service to work. I encourage you to read about the difference between public and private keys in asymmetric encryption. They are generated in pairs, such that when something is encrypted using a public key, it can only be decrypted using the corresponding private key. So it's not correct to say that the message can't be decrypted by the intended recipient - they are in fact the only party who can, but even the sender can not.
-
-
-
-
-
-
-
I don’t know what is worth.
Jack-shit without evidence and demonstrations.
-
-
-
Only the client. Though that's probably enough to make sure messages leave your device suitably encrypted. Depending on the algos it could be quite vulnerable to hndl attacks, though, or (less likely) any undiscovered backdoors in the implementations. Of course, even for Signal one has to trust they're using the public server code anyway, but at least we know they're folding in a quantum-resistant algo.
-
That thing has some of the most verbose documentation I've ever seen. Stuff that should be a paragraph takes multiple pages.
-
-
-
Why dont they use SimpleX?
-
They’ve gone in on matrix pretty hard at this point
-
Simplex is promising, but not ready for primetime.
On my divest OS phone it doesn't even run. Just launches and dies.
Contact Discovery is still a big issue, simple x doesn't have a solution for that yet. You have to do out of band manual addition of your contacts.
-
No Contact Discovery is a feature for me.
Interesting it does not work on your device, I have tried it on a few different phones and have not had any issues. My friends are of course using it as well, all on different devices.
-
https://github.com/simplex-chat/simplex-chat/issues/3184
Appears to be a known issue
WRT Contact Discovery, if your a large organization like... the french government, you want your people to be able to communicate with each other, so they need to solve contact discovery if you really want them to adopt and use simplex for their communication.
-
-
-
Is it French?
-
It can be can be, some French person just have to fork it.
-
-
-
55 comments