Dance Mode Data Record after interrupt

[GilfoyleGit]

Hello Alberto,

I would like to recommend an implementation of a record of last seq ranges scanned in dance mode every time that for any reason keyhunt has to me stopped, before exiting it logs in a file last seq values scaned.

Thank you,

Ali G

[dem10]

Hello Alberto,

I would like to recommend an implementation of a record of last seq ranges scanned in dance mode every time that for any reason keyhunt has to me stopped, before exiting it logs in a file last seq values scaned.

Thank you,

Ali G

The dance sub-mode is also to some extent a random search. In the random mode, saving points is impossible since your disk will fill up very quickly, since the tool will have to save ALL scanned keys. And reading all this mess I think will slow down the instrument.

[GilfoyleGit]

Hello Alberto, I would like to recommend an implementation of a record of last seq ranges scanned in dance mode every time that for any reason keyhunt has to me stopped, before exiting it logs in a file last seq values scaned. Thank you, Ali G

The dance sub-mode is also to some extent a random search. In the random mode, saving points is impossible since your disk will fill up very quickly, since the tool will have to save ALL scanned keys. And reading all this mess I think will slow down the instrument.

Excuse me but maybe my english was not the best... the ideia its not to log all scaned keys... its only before aborting keyhunt, put in sleep mode and log last key from low range and log last key generated from high range both sequential.

Thanks,

Ali G

[dem10]

Hello Alberto, I would like to recommend an implementation of a record of last seq ranges scanned in dance mode every time that for any reason keyhunt has to me stopped, before exiting it logs in a file last seq values scaned. Thank you, Ali G

The dance sub-mode is also to some extent a random search. In the random mode, saving points is impossible since your disk will fill up very quickly, since the tool will have to save ALL scanned keys. And reading all this mess I think will slow down the instrument.

Excuse me but maybe my english was not the best... the ideia its not to log all scaned keys... its only before aborting keyhunt, put in sleep mode and log last key from low range and log last key generated from high range both sequential.

Thanks,

Ali G

I think storing the traversed sub-ranges is only profitable for sequential searches. Any element of randomness is a very difficult task. But this is my opinion. Perhaps Louis's opinion is different from mine.

[GilfoyleGit]

Hello Alberto, I would like to recommend an implementation of a record of last seq ranges scanned in dance mode every time that for any reason keyhunt has to me stopped, before exiting it logs in a file last seq values scaned. Thank you, Ali G

The dance sub-mode is also to some extent a random search. In the random mode, saving points is impossible since your disk will fill up very quickly, since the tool will have to save ALL scanned keys. And reading all this mess I think will slow down the instrument.

Excuse me but maybe my english was not the best... the ideia its not to log all scaned keys... its only before aborting keyhunt, put in sleep mode and log last key from low range and log last key generated from high range both sequential. Thanks, Ali G

I think storing the traversed sub-ranges is only profitable for sequential searches. Any element of randomness is a very difficult task. But this is my opinion. Perhaps Louis's opinion is different from mine.

Dance mode does seq from begining of specified range and seq from begining of end range specified, then calculate random values from those seq values... So what I am asking its to store both values of last 2 seq values!

Simple or not?

[dem10]

Hello Alberto, I would like to recommend an implementation of a record of last seq ranges scanned in dance mode every time that for any reason keyhunt has to me stopped, before exiting it logs in a file last seq values scaned. Thank you, Ali G

The dance sub-mode is also to some extent a random search. In the random mode, saving points is impossible since your disk will fill up very quickly, since the tool will have to save ALL scanned keys. And reading all this mess I think will slow down the instrument.

Excuse me but maybe my english was not the best... the ideia its not to log all scaned keys... its only before aborting keyhunt, put in sleep mode and log last key from low range and log last key generated from high range both sequential. Thanks, Ali G

I think storing the traversed sub-ranges is only profitable for sequential searches. Any element of randomness is a very difficult task. But this is my opinion. Perhaps Louis's opinion is different from mine.

Dance mode does seq from begining of specified range and seq from begining of end range specified, then calculate random values from those seq values... So what I am asking its to store both values of last 2 seq values!

Simple or not? Randomness is already complex. When you go sequentially, you save only the last scanned key. It does not take up much memory space. Randomness involves storing a few minimum subranges. And after saving these subranges, the program needs to read them and save them permanently in the RAM so as not to generate this subrange. As I understand it.

[albertobsd]

wow, that debate is good. Ok guys, i been thinking in this for a while and i going to make one file to store 2 things (Start range, Counter N) and (End Range, Counter N) counter N is how many N has been scanned from the start range forward, and how many N has been scanned from End Range backward.

[32 Bytes start range][8 bytes counter]
[32 Bytes  end  range][8 bytes counter]

With that information the program will be able to restart from the last saved point.

Also i think that i want to add some option to specify how many N do you want to scan for random ranges, actually only one N is begging scanned per random range, so is not good store all those ranges, but if the user request a big number of N ranges per random base maybe in this case will be useful store those ranges.

In this case will be:

[32 Bytes start range][8 bytes counter]
[32 Bytes  end  range][8 bytes counter]
[32 Bytes randomrange][8 bytes counter]
[32 Bytes randomrange][8 bytes counter]
[32 Bytes randomrange][8 bytes counter]
[32 Bytes randomrange][8 bytes counter]

Another thing to take care here is how often the counter is going to be saved?, because file access read and write will take some time, also file access is one thread at the time, so the speed will be affected in the long run, imagine a program running for a month or more the file with some millions of different this will be a problem.

Some other desirable characteristics are going, check the files to see if the range was already checked (in case of random ranges) this will take some time each that a new range value need to be selected.

That is a complicated stuff that is why im not did this in the previous versions, i will do it but i want to do that in the most efficient way.

for the moment i think this will be the best point to start it:

[32 Bytes start range][8 bytes counter]
[32 Bytes  end  range][8 bytes counter]

This will be the easiest way, but without saving random values.

Best regards!

[avtoblesk]

You can also save the points of the scan module of a sequential range every 5 minutes in Dance mode, and other suitable scans. It will turn out that when it starts, it will rely on the initial file of the traversed path, and in the process, fix the traversed path in a new file in some modes (modules) of the program.