5501
fSekrit / A version of fSekrit to handle small binaries?
« Last post by 4wd on August 21, 2008, 11:32 PM »Having just found the goodness that is fSekrit, (yeah - I'm kinda slow), I have a request.
I currently use fSekrit just for program serial number info, (I don't keep much of any other personal non-computer related on the computer), but some of the programs I have use more than just a serial number to legitimise the installation.
eg. Daemon Tools Pro Advanced uses small bits of the program code, (I think), as the keyfile - the program just won't work without it. (BTW, prior to v4.11 these 'keyfiles' were ~400kB but are now in the area of 1-2kB.)
What I would like is a way to store these small bits of binary in fSekrit.
My idea is that if I drag'n'drop a keyfile onto fSekrit it will encode it using yenc, (or whatever - chosen just so I could describe it), and place an appropriately named icon in the fSekrit window.
When I need to use the keyfile, I drag the icon to the Desktop or wherever and fSekrit will deyenc(!?) it.
Optionally, if I drag a keyfile that actually contains text data, I would get a popup asking me how I wanted to save it, either just insert as text or as a yenc encoded binary.
An example is the cFosSpeed keyfile which contains lines of text that have name, address, license type, license data, serial number, etc in a file called key.cfosspeed so you just have to double click on it to have it accepted by the program.
Feasible?
I personally wouldn't mind if it was a separate program or having fSekrit operate in one mode or the other, (text/binary).
BTW, I know this is somewhat different than the way fSekrit currently operates in that it currently leaves nothing behind but I'd be happy having to wipe the file myself after I'd used it.
I currently use fSekrit just for program serial number info, (I don't keep much of any other personal non-computer related on the computer), but some of the programs I have use more than just a serial number to legitimise the installation.
eg. Daemon Tools Pro Advanced uses small bits of the program code, (I think), as the keyfile - the program just won't work without it. (BTW, prior to v4.11 these 'keyfiles' were ~400kB but are now in the area of 1-2kB.)
What I would like is a way to store these small bits of binary in fSekrit.
My idea is that if I drag'n'drop a keyfile onto fSekrit it will encode it using yenc, (or whatever - chosen just so I could describe it), and place an appropriately named icon in the fSekrit window.
When I need to use the keyfile, I drag the icon to the Desktop or wherever and fSekrit will deyenc(!?) it.
Optionally, if I drag a keyfile that actually contains text data, I would get a popup asking me how I wanted to save it, either just insert as text or as a yenc encoded binary.
An example is the cFosSpeed keyfile which contains lines of text that have name, address, license type, license data, serial number, etc in a file called key.cfosspeed so you just have to double click on it to have it accepted by the program.
Feasible?
I personally wouldn't mind if it was a separate program or having fSekrit operate in one mode or the other, (text/binary).
BTW, I know this is somewhat different than the way fSekrit currently operates in that it currently leaves nothing behind but I'd be happy having to wipe the file myself after I'd used it.

Recent Posts




