Hashtopolis Forum
Offer regarding the previous topic - making corrections - Printable Version

+- Hashtopolis Forum (https://hashtopolis.org)
+-- Forum: Support (https://hashtopolis.org/forum-1.html)
+--- Forum: Howto (https://hashtopolis.org/forum-5.html)
+--- Thread: Offer regarding the previous topic - making corrections (/thread-117.html)



Offer regarding the previous topic - making corrections - zielar - 01-23-2019

Due to the fact that nothing is happening here completely and I do not have the strength to read this stupid message "returned non-zero exit status status 1" chasing after my own tail for over two weeks - I am asking for a willing person who will make corrections in appropriate files to enable interaction with BitCracker.

For the job done, I am willing to pay some reasonable sum for both parties.

The topic is on the list of topics under this topic, but I think that a handful of readers already know this topic.

Simple rule ... I want to use the full capabilities of Hashtopolis using BitCrack (only because Hashcat does not have a function that is necessary to me [just do not support it from the beginning and that's it]).
The server and API have been set up and configured.
Agents will be installed on hardware with more than one GPU card. BitCrack does not support multithreading (yet), so I have to run a separate process for each card. Each card is then set to a different hex range in which to search for the correct key.
Used by BitCrack and needed by me (editable) flags:
-d X (selection of the GPU device number)
 [otherwise --device]

--keyspace START: END [specifies the starting point of the scanned range and the end point in hex format]
--share X / Y [Y - determines how many parts I have divided the given range, X - determines which part of this range will scan the selected card] {useful on my example where on a given computer with four cards - all four cards work on the selected range keyspace and I run four processes there, where each of them has successively --share 1/4, --share 2/4, --share 3/4, etc.

Now additional flags that are fixed, but must work without any problems (I do not know if there would be any problem with them, because I have never seen the progress of the whole two weeks of tinkering in codes):
-b X -t X -p X (specify settings for blocks, threads and points for the GPU)
- stride X - jump value during scanning [e.g. stride 9] will cause the scan to be 9x faster by scanning every ninth hex in the range instead of one after the other)


I am waiting for the quickest options and proposals.