On Tue, Sep 21, 2021 at 10:40 AM Jeffrey Walton <noloa...@gmail.com> wrote: > ... > Typically you don't simply encrypt with an elliptic curve. Typically > encryption using elliptic curves is a hybrid public key encryption > scheme, like ECIES. In ECIES, you encrypt a bulk encryption key for a > block cipher like AES under the public key. But even that is slippery > since you don't really encrypt like with RSA. Rather, you use a key > agreement scheme and the person doing the encryption performs half of > the key exchange using a temporary key and the other party's public > key. The other party with the private key performs the other half of > the key agreement, recovers the bulk encryption key, and then uses a > block cipher like AES to decrypt the actual message.
I don't mean to beat a dead horse, but here's what the wikipedia article on EC says (https://en.wikipedia.org/wiki/Elliptic-curve_cryptography): <QUOTE>Elliptic curves are applicable for key agreement, digital signatures, pseudo-random generators and other tasks. Indirectly, they can be used for encryption by combining the key agreement with a symmetric encryption scheme.</QUOTE> So it is not just simple encryption like RSA. > But getting back to your problem... Do you know which JSON algorithm > you are using? I should have restated... The algorithms are listed in RFC 7518, Section 4.1. If you are dealing with some sort of custom scheme, do you have a link to the specification and test vectors? Jeff -- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to cryptopp-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/cryptopp-users/CAH8yC8nnJVtLQZB9_V7PJ4XJfWR%3D3SoTa5pgJVnOOd%3Drua87tQ%40mail.gmail.com.
