Re: [aerogear-dev] Data Sync braindump
My 2 cents here, ed25519 is the best choice and we could do it with kalium
(https://github.com/abstractj/kalium), but that would require the installation of C
library, IMO a drawback. Another alternative would be to implement ed25519 on top of
ECDSA, because the only curves supported by BouncyCastle are
http://www.bouncycastle.org/wiki/display/JA1/Supported+Curves+(ECDSA+and+....
So my suggestion is: start simple with the curves supported by BC, slow or not. Improve
later.
On December 3, 2013 at 12:21:41 AM, Douglas Campos (qmx(a)qmx.me) wrote:
3) Crypto signatures
We could have ed25519 signatures on the changes, making it potentially
safer to decide who should win a change conflict based on rules that
goes beyond simple merging strategies (business roles?)
--
abstractj