Create key map for a list of sectors

[ikarus23]

Until now it is only possible to create the key map for a range of sectors.

This is also needed to be more efficient. If the user chooses to write only the first and the last sector of an dump with e.g. 16 sectors, the key map for all 16 sectors will be created. That's baaad...

[systemcrash]

I wanted to add something to this idea: namely, the ability to use key-files that can specify which sectors they apply to, which should accelerate, or obviate key-mapping. The idea is to specify which key-files to use for reading/writing dumps. If using specified Keys on targeted sectors does not work, the default behaviour should be to fall back to building key-maps as it does today, on a per key/sector basis. e.g. say the user specifies targeted keys for 0A, 0B and 1B, but needs to read 0A, 0B 1A, 1B, 2A 2B. Those keys could be tried for the other sectors as necessary, especially if there are no other keys in the file.

Today it goes something like

#this is a comment
FFFFFFFFFFFF

It could be extended to something like one of the following - whichever best suits the internal workings:

#this is a comment
#keys start without a # comment, and end with optional colon then number to specify
#at which sectors they should be used and optionally Key A/B in brackets ( )
FFFFFFFFFFFF:0-1(A,B)

Or

#this is a comment
#keys start without a # comment
FFFFFFFFFFFF:0A,0B,1A,1B,7A,7B

or

#this is a comment
#keys start without a # comment
FFFFFFFFFFFF;A:1,2,3,4,5,6,7;B1,2,3,4,5,6,7

or

#this is a comment
#keys start without a # comment
FFFFFFFFFFFF;A:1-7,8,9;B1-7,10,12

[ikarus23]

First of all: Thanks for your thoughts on key files with mapping information. I had something like this in my head for a long time... even more: I want a "quick dump" feature!

Because this issue is dedicated to improve the key mapping process, I created a new issue for the
quick dump feature. Part of this quick dump feature will be to implement key files with mapping information.

Please see issue: #43