#1
|
|||
|
|||
Question about local shell on Windows
I recently upgraded my license mostly driven by the support for local shell on Windows. I tried it out today and have a couple of questions.
It defaults to cmd.exe and places me in my user directory. On Windows I use cmder and add executables to its bin folder so that I can access things like hrping or nmap from that console session. This is probably just my own lack of understanding, but if I point SecureCRT new local shell session to the path for cmder executable, it says it is not a valid console application. Does anyone have any suggestions how I might be able to replicate what I do with cmder, but using the local shell support in SecureCRT for Windows? Thank you. |
#2
|
|||
|
|||
Hi dmaker,
Cmder is a terminal application, not a true console application like Powershell/cmd/Bash. As such, SecureCRT currently does not support the use Cmder for local sessions. I have submitted a feature request on your behalf to implement this functionality in SecureCRT. Feature requests are typically prioritized based on a number of factors including, but not limited to, the number of requests and the amount of implementation work required. Should a future release of SecureCRT include this functionality, notification will be posted here. If you prefer direct email notification, send an email to support@vandyke.com and include **"Feature Request - Forum Thread #14006"** in the subject line.
__________________
Thanks, --Brittney VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|