Page 1 of 1

AlternateKeyPath

Posted: 2011-02-03, 23:25 UTC
by HBB
TC program folder in my work place server is an exact copy of the TC program folder in my portable disk. By this way, the unexperienced users always use my TC configuration. I frequently update the TC folder in the server by the one in my portable disk.

I have a problem about KeyPath location. The key file location in my work place is different from the one in my portable disk.

Is it possible to add alternative key path location definition into the wincmd.ini such as "AlternateKeyPath=....". By this way, TC can use the available one.

Regards

Posted: 2011-02-04, 01:39 UTC
by petermad
TC program folder in my work place server is an exact copy of the TC program folder in my portable disk
The key file location in my work place is different from the one in my portable disk
These two statements seems contradictory to me.


How about not using any KeyPath= statement in you wincmd.ini at all - then TC will always just use the key file in it's program directory - or is that for some reason not an option for you.

Posted: 2011-02-04, 08:59 UTC
by HBB
petermad :
These two statements seems contradictory to me.
Of course, I mean a copy except KeyPath in wincmd.ini. This is the reason to request AlternateKeyPath for wincmd.ini.

Unfortunately, after copying, I have to change KeyPath manually in each time.

regards

Posted: 2011-02-04, 10:32 UTC
by petermad
But why do you need to use KeyPath in the first place? - is it not an option for you to store the key in TC's program folder?

Posted: 2011-02-04, 15:29 UTC
by HBB
petermad :
is it not an option for you to store the key in TC's program folder?
I am trying to protect the key file. Please look at the topic and my post.

regards

Posted: 2011-02-04, 19:22 UTC
by petermad
Please look at the topic and my post.
Aha - not easy to know when you haven't refered to that topic before, under this topic.

In the other thread you wrote:
This special folder is under a protected folder which is not permitted to be viewed by the users...
But when the experienced users exist in the environment, they can easily obtain the key file by looking the location of the key file in wincmd.ini.
How can the experienced user get access to a file in a protected folder?

Posted: 2011-02-05, 21:37 UTC
by HBB
Petermad :
not easy to know when you haven't refered to that topic before, under this topic.
This topic does not directly refers to another topic. I have pointed it only in order to answer your question.
How can the experienced user get access to a file in a protected folder?
<<< EDITED : The Key file is not directly under the protected folder, it is under the a (special) folder which is under the protected folder. It can be copied by a batch file by knowing the location. It must be reachable because TC needs it. Otherwise, if nobody can access, TC also can not access it.>>>

Here, my suggestion is simply a request to add another definition key (alternateKeyPath) in wincmd.ini. I believe that this will be usefull for some people (like me) :
- who locate Total Commander program files into the portable drive,
- who does not directly put key file into the program file directory,
- who want to access to the key file in two different places (e.g. at home or at work).

-----------------------

In the other topic (not related to this topic), I suggested to encrypt the KeyPath location. Because, I believe that encrypting the key file itself creates difficulties for the users. For this case, users should enter a password in each time to open TC (note that this may be difficult than entering 1-2-3). Maybe, an arrangement similar to LockNote.exe may give an opportunity to define key path location to TC with a password. TC may encrypt this key path location like LockNote.exe. By this way, nobody can access the key path location without knowing the password. I know this is not excellent way to protect key file, but, it is better than the current situation.

regards