Re: Pollard's kangaroo ECDLP solver

Quote from: citb0in on Today at 10:51:57 AM

Quote from: Baboshka on Today at 02:10:50 AM

... therefore most of the time those tools never work correctly.

As I told before, after testing the Kangaroo-256 with the examples of JeanLucPons and got no result, I started doubting the other tools therefore I created a simple test tile the same as the one from JeanLucPons but in the range of puzzle 130 but with a very small range as following

Code:

2F633CBE3EC02B9401000000007000000
2F633CBE3EC02B9401000000009000000
021c20007f8c8984d403a695494d6afbff37f55a01c8bd1aafb9b958fa9485bb02

which is small range of about 33M and the PKey is 2F633CBE3EC02B9401000000008000000 and run the following

Kangaroo 2.2 (JeanLucPons) : found the key in 15secs
Kangaroo 2.3 (NotATether) : no result
Etar-Kangaroo : no result
Rotor-Cuda: found key in few seconds - like Kangaroo 2.2

What exactly is your question? JLP Kangaroo works without any problems and as far as I have understood your statement correctly, you confirm this yourself. You found the key with JLP software, or have I misunderstood something?

He was talking about the Kanga-256 version. He used it with the examples (configuration of cmd line/input text) and it did not find the key. I believe NotATether can confirm it has bugs/slow speed. I know he worked on that years ago and I'm not sure he has messed with it since.