Hi Javier. > I would like to know if the preliminary beta Kraken for windows is > ready. I read on the list that there are some developpers working on it.
Yeah, it's already in an usable state. But there might still be some issues. Just test it and report :) I made many changes in the code to make Kraken-win32 looking like what I expect it to look like. So don't see this as an official Kraken port for win32, but as an heavily customized version. We have also cleared the responsibilities for the kraken-win32 port now. (thanks Karsten, thanks Frank!) Kraken-win32 will be maintained by me. I think its better not to ask Karsten, Frank, etc about bugs that might have been introduced with my changes :) Unfortunately I used the (older) SVN version for my changes, since some guide directed me to the SVN repository. The version in git has improvements similar to some of mine. I tested my code with this setup: DELL XPS 420, E8500, 8GB RAM Radeon HD3870 / Radeon HD4850 one 2TB WD HDD with 40 tables Windows Vista Business 64 bit and a while ago also Ubuntu hardy in VirtualBox just a compile test, but should still work on linux If there are questions, just ask. Below all the information you will need. (hopefully) BR, Georg Download: ----------- http://g3gg0.de/projects/Kraken/Kraken-win32.zip SVN: ------ http://svn.g3gg0.de/svn/kraken-win32/ user: kraken pass: kraken Changes: ---------------- - improved ServerCore to allow console + remote connection - improved network protocol - ATI CAL kernels in extra files - Support some ATI Radeon HD3xxx models (uses slower GPU code then!) - config file allows to specify a sector offset (required for win32) - merged find_kc into Kraken - startup speedup using cached table indexes - fixed some rare crash situations - introduced some new random crash situations ;) Config file: --------------- - execute "wmic diskdrive list" on your windows console to get the \\.\PhysicalDrive-name 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 don't 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: ----------- (<parm> are required parameters, [parm] are optional) - 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 network clients. - perf disk [reads] queue random block reads to test disk speed. without parameter [reads] it will queue 2000 reads. - quit (console only) will quit the client Example communication: ------------------------ > crack 101010101...1101 122332 111001010...1101 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...1101 122333 111001010...1101 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) old style syntax: > crack 101010101000...0001010101 < 100 Queuing request (0 already in queue) < 101 279 Request queued < 102 279 Processing your request now < 103 279 ABCDEF0123445 23 (found a table hit) <- candidate for find_kc < 404 279 Key not found (search took 395 seconds) /* * 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 - response to "status"-command * 211 - response to "idle"-command * 212 - response to "cancel"-command * 213 - response to "fake"-command * 214 - response to "stats"-command * 215 - response to "perf disk"-command * 216 - finished "perf disk"-command * */ _______________________________________________ A51 mailing list [email protected] http://lists.lists.reflextor.com/cgi-bin/mailman/listinfo/a51
