Skip to content

New command to lock key definitions - #578

Merged
davidrg merged 4 commits into
masterfrom
udk-lock
Oct 26, 2026
Merged

davidrg merged 4 commits into
masterfrom
udk-lock

Conversation

@davidrg

@davidrg davidrg commented Oct 26, 2026

Copy link
Copy Markdown
Owner

This setting exists on the VT220 and up, and now it exists on Kermit 95 as well!

Kermit 95 actually already had this setting, it just wasn't under the users control. It could be set to ON via DECUDK with no way for the user to reset it to OFF. This also meant that the user couldn't easily set it to ON themselves in the interest of security. This problem is now resolved!

And in the interests of security this setting also now applies to other DECUDK-like functions in other terminal emulations, and defaults to ON unlike previous versions of K95 and real DEC terminals (and presumably unlike on real HP, WYSE, TVI and SCO terminals too).

As this is one of a number of settings whose default doesn't match a real terminal, and one that also doesn't match previous versions of K95, I figured it was time to add a page to the manual describing Kermit 95s VT220 emulation. This includes all settings that are known to have different defaults as well as all other settings that are equivalent to some option in the VT220s setup menus.

The setting itself already existed in Kermit 95 but no command was provided to control it. It could only be set to ON via DECUDK. Unlike on real terminals, the user had no ability to reset it back to OFF.

The new command gives the user control over this setting. The setting has also been extended to affect DECUDL-equivalent functions in other emulations in the interests of security.

And in the interests of security this setting now defaults to ON in order to prevent the host from making unexpected changes to the keymap.
This covers all the known ways in which Kermit 95s VT220 emulation differs from the real thing. In particular, the freshly added setting to lock key definitions whose default differs from that of a real VT220.
@davidrg
davidrg merged commit 82d3301 into master Oct 26, 2026
32 checks passed
@davidrg
davidrg deleted the udk-lock branch October 26, 2026 21:00
@j4james

j4james commented Oct 26, 2026

Copy link
Copy Markdown

@davidrg I haven't had a chance to test with this commit yet, but before I forget, there was an issue I noticed when testing before: if you lock the UDK definitions, and then do a soft reset, Kermit both clears and unlocks the definitions which I believe is incorrect (see STD 070-4, page 32). I think a hard reset is supposed to clear and unlock, but even then, that's only if the UDK functionality was unlocked to start with. If the user has intentionally locked it in the settings, it shouldn't be possible to unlock from the host.

@davidrg

davidrg commented Oct 26, 2026

Copy link
Copy Markdown
Owner Author

Good catch! I'd only just noticed a few minutes ago that UDKs were being unlocked by a reset. I'm preparing another PR to switch the K95 terminal type over to having UDKs mapped by default pre-initialised with what xterm sends, so I'll fix that up over there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants