> So now I've got the questions related to KeyDerivationAlgo and
> EncryptionAlgo.
>
> 1. According to Bouncy Castle compatability patch and java example as I
> understand I need to instantiate:
>
> DL_KeyDerivationAlgorithm_P1363<ECP::Point, true /*DHAES_MODE*/,
> P1363_KDF2<SHA256> > derieveAlgo;
> DL_EncryptionAlgorithm_Xor<HMAC<SHA256>, true /*DHAES_MODE*/, true
> /*BC_COMPAT*/> encAlgo;
>
> In the documentation they mention DEM2 from ISO 18033-2.
> Is the encAlgo definition above fully compatible with that?
>
I have a copy of ISO 18033-2. I should probably copy that section and get
you a copy for interop/academic/research purposes since you are actively
working the problem. Can you email me off list at noloader, gmail account?
Eventually, I think we should provide something like the following. Then
all these interop problems go away.
ECIES_ANDROID_PAY<...>
We can provide it in the library proper, on the ECIES page under Android
Pay, or on the Patch Page (http://www.cryptopp.com/wiki/Category:Patch).
The point is, its available and "it just works" so users don't suffer the
interop.
I really like ECIES, but I really despise all of the interop problems with
it. No wonder it has never gained popularity.
Jeff
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
