Not logging all key strokes? [5]
Not logging all key strokes?
Friday, July 21, 2006 4:17 AM - Mark
Hi,
When I log to a file I see everything I type, even if I type backspace because of typing errors.
Is there any way to only log the text I send/receive from the remote server?
Also sometimes the logged text opens up as HEX in my text editor (pspad). Is that because control characters are included in the text? How can I stop that so that they all open up as text?
For example, this is one log:
### BEGIN LOG - DATE: 060720, TIME: 211128 ###
woops ls
~ # ### END LOG - DATE: 060720, TIME: 211152 ###
When I just should see the command 'ls'.
When I log to a file I see everything I type, even if I type backspace because of typing errors.
Is there any way to only log the text I send/receive from the remote server?
Also sometimes the logged text opens up as HEX in my text editor (pspad). Is that because control characters are included in the text? How can I stop that so that they all open up as text?
For example, this is one log:
### BEGIN LOG - DATE: 060720, TIME: 211128 ###
woops ls
~ # ### END LOG - DATE: 060720, TIME: 211152 ###
When I just should see the command 'ls'.
Re: Not logging all key strokes?
Friday, July 21, 2006 4:49 PM - Support
Hello Mark,
Xshell stores control characters as well as printable characters entered by user. There is no way to remove control characters at this version.
In future release, we are planning to add an option to not store non-printable characters.
Thanks for your feedback.
--
Technical Support
Xshell stores control characters as well as printable characters entered by user. There is no way to remove control characters at this version.
In future release, we are planning to add an option to not store non-printable characters.
Thanks for your feedback.
--
Technical Support
Re: Not logging all key strokes?
Thursday, March 14, 2013 12:16 AM - hao
This problem does not seem to fix this? (XSHELL 4 Build0125)
and why different from the terminal display and log file?
ex.
Xshell:
*A:S21X# file dir
Volume in drive cf3 on slot A has no label.
Volume in drive cf3 on slot A is formatted as FAT32.
Directory of cf3:\
01/03/2000 09:41p 1988896 boot.ldr
01/01/2000 12:00a 541 bof.cfg
log file:
*A:S21X# file dir
Volume in drive cf3 on slot A has no label.
Volume in drive cf3 on slot A is formatted as FAT32.
Directory of cf3:\
01/03/2000 09:41p 1988896 boot.ldr
01/01/2000 12:00a 541 bof.cfg
and why different from the terminal display and log file?
ex.
Xshell:
*A:S21X# file dir
Volume in drive cf3 on slot A has no label.
Volume in drive cf3 on slot A is formatted as FAT32.
Directory of cf3:\
01/03/2000 09:41p 1988896 boot.ldr
01/01/2000 12:00a 541 bof.cfg
log file:
*A:S21X# file dir
Volume in drive cf3 on slot A has no label.
Volume in drive cf3 on slot A is formatted as FAT32.
Directory of cf3:\
01/03/2000 09:41p 1988896 boot.ldr
01/01/2000 12:00a 541 bof.cfg
Re: Not logging all key strokes?
Thursday, March 14, 2013 1:06 AM - Support
Could you tell us the following information?
1. What is the name and version of the server you are connecting to?
2. What is the connection method?
3. Can you provide us with a test account so that we can try to duplicate the problem from our end?
---
Technical Support
1. What is the name and version of the server you are connecting to?
2. What is the connection method?
3. Can you provide us with a test account so that we can try to duplicate the problem from our end?
---
Technical Support
Re: Not logging all key strokes?
Thursday, March 14, 2013 2:13 AM - hao
1.alucatel-lucent router or other router/switch.
2. ssh or serial
3. sorry, I can't.
SecureCRT not have this problem in the same device.
2. ssh or serial
3. sorry, I can't.
SecureCRT not have this problem in the same device.
Re: Not logging all key strokes?
Sunday, March 17, 2013 11:20 PM - Support
In the Advanced > Logging, select Log printable text only option and try again.
If the problem persists, please send us the log file and screenshots of the following Xshell property pager?
1. Terminal > Advanced
2. Terminal > VT Mode
---
Technical Support
If the problem persists, please send us the log file and screenshots of the following Xshell property pager?
1. Terminal > Advanced
2. Terminal > VT Mode
---
Technical Support
Previous views: 221