<<  >> (p.15)
    Author Topic: Pollard's kangaroo ECDLP solver  (Read 62537 times)
    Jean_Luc (OP)
    Sr. Member
    ****
    Offline Offline

    Activity: 462
    Merit: 737


    View Profile
    May 24, 2020, 02:47:00 PM
     #281

    Hi there Wink

    @etar
    I checked the client and server and I didn't manage to reproduce the issue.
    If I break the network at the client side, the server close the connection after the timeout (5min) and when the client goes back it reconnect.
    But I will add a http like connection mode and a way to set up the send period.
    There is way to do that by setting the CLIENT_TIMEOUT to 3 sec and the SEND period to 10 sec for instance. You get the following output but it works.

    Client side:
    [180.22 MK/s][GPU 180.22 MK/s][Count 2^29.99][08s][Server     OK]
    RecvFromServer(Status): Software caused connection abort
    [140.52 MK/s][GPU 140.52 MK/s][Count 2^31.07][18s][Server     OK]
    RecvFromServer(Status): Software caused connection abort
    [140.34 MK/s][GPU 140.34 MK/s][Count 2^31.68][28s][Server     OK]
    RecvFromServer(Status): Software caused connection abort
    [141.10 MK/s][GPU 141.10 MK/s][Count 2^32.11][38s][Server     OK]

    Server side:
    Closing connection with 127.0.0.1:64273
    [Client 0][DP Count 2^19.11/2^21.05][Dead 0][41s][19.2/49.5MB]
    Closing connection with 127.0.0.1:64274
    [Client 0][DP Count 2^19.70/2^21.05][Dead 0][51s][28.0/60.7MB]
    Closing connection with 127.0.0.1:64275

    @zielar

    wow, 460000Mkeys/s, really ? #110 should be solved tomorrow...
Page 14
Viewing Page: 15