Should we always use a hybrid encryption protocol to share information?
Whenever we think about sharing information securely, we think about encryption, sharing keys, and the best approach, which is often called "hybrid cryptography." But is it really necessary to expe...

Source: DEV Community
Whenever we think about sharing information securely, we think about encryption, sharing keys, and the best approach, which is often called "hybrid cryptography." But is it really necessary to expend so many resources on one-way, single messages? For these types of messages, it's not so necessary. Let me give you an example to see why: we need to share a specific piece of data, just one, some coordinates, a unique message to verify activity or to initiate an action... The first thing we might think of is to start with the protocol as we know it. We would begin by creating an asymmetric key pair (RSA/ECC), then create the symmetric key (AES/ChaCha20), and then share the public keys among the users, finally sharing the symmetric keys to perform encryption and secure sharing. But this clearly doesn't make sense; these types of protocols are used for persistent connections, and that's clearly not our situation. If you've noticed, we recently shared encrypted data without any issues: that d