You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In your Readme you write "The emulator does use "rsh" or "telnet", because historical Unix systems do not support the secure ssh protocol, and because ssh does not allow using a virtual emulator such as tek4010 for security reasons."
I appreciate that it would be a significant restructuring, but have you considered wrapping the Tektronix input and output filtering around code based on the unix 'script' command instead? 'script' without the logging (or even if you keep the logging for debugging purposes) gives you a very accessible place to intercept keyboard input and tty output - and all linux commands work as normal within 'script', so there would be no need to prohibit the use of ssh for connections to some other system that may be generating Tektronix-like output.
(I've been doing something similar to enable a linux shell to use a Vectrex vector display, so I know this can work)
The only downside of this approach is that it is only as portable as the version of 'script' that you base it on, so it may be more appropriate as an addition to the existing mechanism rather than a replacement for it as I doubt it would work under windows or BSD.
tek4010 can wrap any linux application. Not just telnet and rsh, as long as the application does not prohibit it for security reasons. You seem to have experience with script. I suggest that you just try it. with a simple example.
In your Readme you write "The emulator does use "rsh" or "telnet", because historical Unix systems do not support the secure ssh protocol, and because ssh does not allow using a virtual emulator such as tek4010 for security reasons."
I appreciate that it would be a significant restructuring, but have you considered wrapping the Tektronix input and output filtering around code based on the unix 'script' command instead? 'script' without the logging (or even if you keep the logging for debugging purposes) gives you a very accessible place to intercept keyboard input and tty output - and all linux commands work as normal within 'script', so there would be no need to prohibit the use of ssh for connections to some other system that may be generating Tektronix-like output.
Script for debian linux (which compiles easily on the Raspberry Pi for example) can be found at:
wget http://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.38/util-linux-2.38.tar.gz
(I've been doing something similar to enable a linux shell to use a Vectrex vector display, so I know this can work)
The only downside of this approach is that it is only as portable as the version of 'script' that you base it on, so it may be more appropriate as an addition to the existing mechanism rather than a replacement for it as I doubt it would work under windows or BSD.
regards,
Graham Toal gtoal@gtoal.com
The text was updated successfully, but these errors were encountered: