|
Archive for the 'SSH' Category
Wednesday, May 2nd, 2007
Currently port forwarding in TinyTERM Plus does local-to-remote and remote-to-local forwarding. Century Software, Inc., has had a request to use TinyTERM Plus as a sort of “go-between” from the SSH server to another system, encrypting on the way. This would requires a third, indirect port forwarding option be added to TinyTERM Plus.
CR 729
Posted in SSH | Comments Off on Indirect Mode for Port Forwarding
Wednesday, May 2nd, 2007
Century Software, Inc., has had a request for RSA SecurID support in TinyTERM Plus. This has not been implemented thus far.
CR 713
Posted in SSH | Comments Off on RSA SecurID
Wednesday, May 2nd, 2007
The SSH protocol includes an option to display an introductory message or “banner” prior to login. This is not yet implemented in TinyTERM Plus.
CR 712
Posted in SSH | Comments Off on SSH Banner
Wednesday, May 2nd, 2007
Century Software, Inc., has had a request for keyboard-interactive authentication for SSH. This would allow standard login and password prompts over an SSH connection. It has not been implemented thus far.
CR 698
Posted in Login, SSH | Comments Off on Keyboard-Interactive Authentication
Monday, April 30th, 2007
The SSH2 protocol includes the ClientAliveInterval and ClientAliveCountMax options. The sshd_config man page describes both:
ClientAliveInterval
Sets a timeout interval in seconds after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The default is 0, indicating that these messages will not be sent to the client. This option applies to protocol version 2 only.
ClientAliveCountMax
Sets the number of client alive messages which may be sent without sshd receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from TCPKeepAlive. The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.
TinyTERM Plus responds to the keepalive packets sent when ClientAliveInterval is non-zero. Thus, it does not automatically get disconnected when idle.
CR 653, added in version 4.8.1
Posted in SSH | Comments Off on ClientAliveInterval
Monday, April 30th, 2007
Century Software, Inc., has had a request to add an option to port forwarding that would allow the remote system to assign TCP ports dynamically. Currently port forwarding can only use assigned TCP ports.
CR 643
Posted in SSH, TCP/IP | Comments Off on Dynamic Port Allocation for Port Forwarding
Friday, April 27th, 2007
When the user’s password has expired, SSH disconnects with a “login refused” message. The SSH protocol allows for the opportunity to change the password, but this is not implemented in TinyTERM Plus.
CR 562
Posted in SSH | Comments Off on SSH Doesn’t Prompt on Expired Password
Friday, April 27th, 2007
Century Software, Inc., has had a request to add AES (advanced encryption standard) 64-, 128-, 192- and 256-bit encryption to TinyTERM Plus. This was implemented in TinyTERM version 4.65.4985, available August 2011.
CR 527
Posted in SSH | Comments Off on AES Encryption
Thursday, April 26th, 2007
Once you connect TinyTERM via SSH, some system memory is tied up until you restart Windows. In TinyTERM Plus 4.31, this was reduced to about 15 kb that becomes unavailable, but the problem has not been eliminated.
CR 426
Posted in SSH | Comments Off on SSH Memory Leak
Thursday, April 26th, 2007
Century Software, Inc., has had a request to add PKI capability to SSH. It has not been implemented thus far.
Public Key Infrastructure (PKI) is a system where digital certificates are used to increase the reliability and scalability of authentication. Using certificate authentication requires that certificates are first created with certification authority (CA) software. Full details are available from ssh.com.
CR 343
Posted in SSH | Comments Off on PKI for SSH
|