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.
There are cryptographic methods which allow me to send you a public encryption key which is mathematically related to a private decryption key. Brute forcing the private key is possible but computationally expensive. An AES 256 key has 2^256 different keys that would need to be checked it would take Frontier, the fastest supercomputer right now can do 1.1e18 calculations per second 5.1e78 seconds 2.32e71 years.
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.
There are cryptographic methods which allow me to send you a public encryption key which is mathematically related to a private decryption key. Brute forcing the private key is possible but computationally expensive. An AES 256 key has 2^256 different keys that would need to be checked it would take Frontier, the fastest supercomputer right now can do 1.1e18 calculations per second 5.1e78 seconds 2.32e71 years.