Command line access with RestrictInterface=2 [2]

Bug reports will be moved here when the described bug has been fixed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
User avatar
Flint
Power Member
Power Member
Posts: 3487
Joined: 2003-10-27, 09:25 UTC
Location: Antalya, Turkey
Contact:

Command line access with RestrictInterface=2 [2]

Post by *Flint »

The continuation of this thread.

1. Press Ctrl+E: the cursor moves to the hidden command line and becomes invisible. If you have a menu item or a button on the buttonbar with the command cm_FocusCmdLine, it becomes "selected".
2. Type e.g. cmd (you have to do it blindly, but the autocomplete drop-down list is shown!), press Enter.
3. cmd.exe is started.

Of course, if you call cm_NextCommand or cm_PrevCommand from the menu the result is the same as above: you access the command line, though invisibly.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 10.52 / Win10 x64
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48130
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Thanks, I will just intercept the calls to ExecuteCommandLine, this way it will be impossible to start it even if the user somehow manages to place any commands into it.
Author of Total Commander
https://www.ghisler.com
User avatar
Flint
Power Member
Power Member
Posts: 3487
Joined: 2003-10-27, 09:25 UTC
Location: Antalya, Turkey
Contact:

Post by *Flint »

Fixed in pb4.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 10.52 / Win10 x64
Post Reply