Pointy Castle tests broken in Dart 2.0 - does bignum work?

[stevenroose]

Pointy Castle relies on BigInteger everywhere. However, while starting to port it to Dart 2.0, a lot of the unit tests are broken. I'm having trouble figuring out what is the root cause, but it seems like bignum could be the cause.

F.e. BigIntegers instantiated using new BigInteger("<hex>", 16) print as 0 and comparisons fails. (Not sure if the actual value is 0 (constructor fails) or if the print function fails.)

[azenla]

Note, Dart has switched to int64 in 2.0

https://github.com/dart-lang/sdk/blob/master/docs/language/informal/int64.md

The BigInt class is now available in 2.0, however there are some bugs that must be worked around:
dart-lang/sdk#32626

[stevenroose]

I saw that. And yes, working on it :)

[stevenroose]

Damn. I should read this more carefully! I've been trying to debug that code for PointyCastle for over a week and I couldn't get my head around it. It's a blessing someone found that bug in modPow. Still not sure though if it's actually that!