Hello, I ported kraken to win32. It is working fine in my setup. This is without source code (yet). I am still cleaning up and looking into minimizing the changes for a clean SVN commit.
It is using asynchronous reads to (hopefully) make use of NCQ. ATI code is also ported, but I didn't find anyone who could test this. So I don't know if this works. If you want the source zipped and cannot wait until its finished, just tell me. I will upload/mail it. Download: ----------- http://g3gg0.de/projects/Kraken/Kraken-win32.zip Other Changes: ---------------- - improved ServerCore to allow console + remote connection - improved network protocol - ATI CAL kernels in extra files - config file allows to specify a sector offset - merged Kraken with find_kc - startup speedup with cached table indexes Config file: --------------- - execute "wmic diskdrive list" on your console to get the \\.\PhysicalDrive-ID of your data disks - use some fdisk tool to get the start sector of the data partition on your disks (e.g. sector 63) - specify above information in your tables.conf: 'Device: \\.\PhysicalDrive1+63 40' Network connection: --------------------- - please specify your tcp port if you dont want to have port 8866 - every command will return a status code from the list below - for every queued request, you will receive an ID - results will get printed out with the ID of the request Commands: ----------- - crack <bits1> [<COUNT1> <bits2> <COUNT2>] will try to find the Kc if bitsx and COUNTx are given. if just the bits are given and no COUNT etc, kraken will report the intermediate result as usual, but with some other formatting. - cancel cancel currently processed request - fake successfully finish current request immediately with a faked result key. its mainly for testing the client. - quit (console only) will call exit(0) and so quit the client Example communication: ------------------------ > crack 101010101... 122332 111001010... 122351 < 100 Queuing request (0 already in queue) < 101 277 Request queued < 102 277 Processing your request now < 103 277 ABCDEF0123445 23 (found a table hit) < 200 277 DEADBEEFDEADBEEF Key found (search took 395 seconds) > crack 101010101... 122333 111001010... 122352 < 100 Queuing request (0 already in queue) < 101 278 Request queued < 102 278 Processing your request now < 103 278 ABCDEF0123445 23 (found a table hit) < 404 278 Key not found (search took 395 seconds) I would appreciate if someone could test this and give some feedback. BR, Georg /* * Kraken Status codes: * * 100 - your request will get queued * 101 [id] - your request has been queued with ID [id] * 102 [id] - your request [id] is getting processed now * 103 [id] [result] [bitpos] - intermediate result found * * 200 [id] [key] - Kc for [id] was found * * 400 - invalid request * 404 [id] - no key found for this request * * 210 - status response * 211 - idle response * 212 - cancelling positive response * 213 - faking response * */ _______________________________________________ A51 mailing list [email protected] http://lists.lists.reflextor.com/cgi-bin/mailman/listinfo/a51
