nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-09 17:38:00 +00:00
Code Issues Projects Releases Wiki Activity
pre-0.83
putty-source/windows/help.h

222 lines
12 KiB
C
Raw Permalink Normal View History

The long-awaited config box revamp! I've taken the whole config box to pieces, and put it back together in a new table-driven form. config.c sets up a data structure describing most of the config box; wincfg.c adds in the Windows-specific options (so that config.c can also form the basis for Mac and Unix config boxes). Then winctrls.c contains a shiny new layout engine which consumes that data structure, and windlg.c passes all WM_COMMAND and similar messages to a driver alongside that layout engine. In the process I've sorted out nicer-looking panel titles and finally fixed the list-boxes-are- never-the-right-size bug (turned out to be Windows's fault, of course). I _believe_ it should do everything the old config box did, including context help. Now everyone has to test it thoroughly... [originally from svn r2908]
2003-03-05 22:07:40 +00:00
/*
Rename most of the platform source files. This gets rid of all those annoying 'win', 'ux' and 'gtk' prefixes which made filenames annoying to type and to tab-complete. Also, as with my other recent renaming sprees, I've taken the opportunity to expand and clarify some of the names so that they're not such cryptic abbreviations.
2021-04-23 05:19:05 +00:00
* help.h - define Windows Help context names.
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
* Each definition is simply a string which matches up with the
* section names in the Halibut source, and is used for HTML Help.
The long-awaited config box revamp! I've taken the whole config box to pieces, and put it back together in a new table-driven form. config.c sets up a data structure describing most of the config box; wincfg.c adds in the Windows-specific options (so that config.c can also form the basis for Mac and Unix config boxes). Then winctrls.c contains a shiny new layout engine which consumes that data structure, and windlg.c passes all WM_COMMAND and similar messages to a driver alongside that layout engine. In the process I've sorted out nicer-looking panel titles and finally fixed the list-boxes-are- never-the-right-size bug (turned out to be Windows's fault, of course). I _believe_ it should do everything the old config box did, including context help. Now everyone has to test it thoroughly... [originally from svn r2908]
2003-03-05 22:07:40 +00:00
*/
Add context help to a couple of message boxes. Unfortunately the ones I wanted to get to -- "software caused connection abort" and friends -- are going to be more involved (probably requiring some cross-platform notion of help contexts), and these ones hardly seem worth the effort. Still, I've done it now. Side-effect: Pageant now uses the same `hinst' and `hwnd' globals as everything else. Tested basic functionality. [originally from svn r5417]
2005-03-01 01:16:57 +00:00
/* Maximum length for WINHELP_CTX_foo strings */
Move the MessageBox-with-help function out into winutils.c, although it's still only used for the host key popups. Side-effects: - requested_help is a winstuff.h global - Pageant now defines winstuff.h globals (Also, my previous fix to my improved host-key dialogs only got the "changed" case, not the "unknown" case. Some days I shouldn't be let near a keyboard.) [originally from svn r5415]
2005-03-01 00:00:09 +00:00
#define WINHELP_CTX_MAXLEN 80
The Windows host key dialogs now have a `Help' button that should give appropriate context help, iff the help file is present. (Shame it's prey to `winhelp-crash'.) (I've perpetrated a widening of visibility of `hwnd'; the alternative, putting it into a frontend handle, seemed too likely to cause maintenance trouble if we don't also _use_ that frontend handle everywhere we now use the global `hwnd'.) [originally from svn r5309]
2005-02-15 22:23:47 +00:00
/* These are used in the cross-platform configuration dialog code. */
Make HelpCtx a per-platform type, not an intorptr. Partly, this just seems more sensible, since it may well vary per platform beyond the ability of intorptr to specify. But more immediately it means the definition of the HELPCTX macro doesn't have to use the P() function from dialog.h, which isn't defined in any circumstances outside the config subsystem. And I'm about to want to put a help context well outside that subsystem.
2022-07-05 17:11:54 +00:00
typedef const char *HelpCtx;
#define NULL_HELPCTX NULL
#define HELPCTX(x) WINHELP_CTX_ ## x
The long-awaited config box revamp! I've taken the whole config box to pieces, and put it back together in a new table-driven form. config.c sets up a data structure describing most of the config box; wincfg.c adds in the Windows-specific options (so that config.c can also form the basis for Mac and Unix config boxes). Then winctrls.c contains a shiny new layout engine which consumes that data structure, and windlg.c passes all WM_COMMAND and similar messages to a driver alongside that layout engine. In the process I've sorted out nicer-looking panel titles and finally fixed the list-boxes-are- never-the-right-size bug (turned out to be Windows's fault, of course). I _believe_ it should do everything the old config box did, including context help. Now everyone has to test it thoroughly... [originally from svn r2908]
2003-03-05 22:07:40 +00:00
#define WINHELP_CTX_no_help NULL
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_session_hostname "config-hostname"
#define WINHELP_CTX_session_saved "config-saving"
#define WINHELP_CTX_session_coe "config-closeonexit"
#define WINHELP_CTX_logging_main "config-logging"
#define WINHELP_CTX_logging_filename "config-logfilename"
#define WINHELP_CTX_logging_exists "config-logfileexists"
#define WINHELP_CTX_logging_flush "config-logflush"
#define WINHELP_CTX_logging_header "config-logheader"
#define WINHELP_CTX_logging_ssh_omit_password "config-logssh"
#define WINHELP_CTX_logging_ssh_omit_data "config-logssh"
#define WINHELP_CTX_keyboard_backspace "config-backspace"
#define WINHELP_CTX_keyboard_homeend "config-homeend"
#define WINHELP_CTX_keyboard_funkeys "config-funkeys"
New config option for shifted arrow key handling. This commit introduces a new config option for how to handle shifted arrow keys. In the default mode (SHARROW_APPLICATION), we do what we've always done: Ctrl flips the arrow keys between sending their most usual escape sequences (ESC [ A ... ESC [ D) and sending the 'application cursor keys' sequences (ESC O A ... ESC O D). Whichever of those modes is currently configured, Ctrl+arrow sends the other one. In the new mode (SHARROW_BITMAP), application cursor key mode is unaffected by any shift keys, but the default sequences acquire two numeric arguments. The first argument is 1 (reflecting the fact that a shifted arrow key still notionally moves just 1 character cell); the second is the bitmap (1 for Shift) + (2 for Alt) + (4 for Ctrl), offset by 1. (Except that if _none_ of those modifiers is pressed, both numeric arguments are simply omitted.) The new bitmap mode is what current xterm generates, and also what Windows ConPTY seems to expect. If you start an ordinary Command Prompt and launch into WSL, those are the sequences it will generate for shifted arrow keys; conversely, if you run a Command Prompt within a ConPTY, then these sequences for Ctrl+arrow will have the effect you expect in cmd.exe command-line editing (going backward or forward a word). For that reason, I enable this mode unconditionally when launching Windows pterm.
2021-10-18 19:00:25 +00:00
#define WINHELP_CTX_keyboard_sharrow "config-sharrow"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_keyboard_appkeypad "config-appkeypad"
#define WINHELP_CTX_keyboard_appcursor "config-appcursor"
#define WINHELP_CTX_keyboard_nethack "config-nethack"
#define WINHELP_CTX_keyboard_compose "config-compose"
#define WINHELP_CTX_keyboard_ctrlalt "config-ctrlalt"
#define WINHELP_CTX_features_application "config-features-application"
#define WINHELP_CTX_features_mouse "config-features-mouse"
#define WINHELP_CTX_features_resize "config-features-resize"
#define WINHELP_CTX_features_altscreen "config-features-altscreen"
#define WINHELP_CTX_features_retitle "config-features-retitle"
#define WINHELP_CTX_features_qtitle "config-features-qtitle"
#define WINHELP_CTX_features_dbackspace "config-features-dbackspace"
#define WINHELP_CTX_features_charset "config-features-charset"
#define WINHELP_CTX_features_clearscroll "config-features-clearscroll"
#define WINHELP_CTX_features_arabicshaping "config-features-shaping"
#define WINHELP_CTX_features_bidi "config-features-bidi"
Add a Features checkbox to disable bracketed paste mode. I've had more than one conversation recently in which users have mentioned finding this mode inconvenient. I don't know whether any of them would want to turn it off completely, but it seems likely that _somebody_ will, sooner or later. So here's an option to do that.
2024-08-10 11:11:28 +00:00
#define WINHELP_CTX_features_bracketed_paste "config-features-bracketed-paste"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_terminal_autowrap "config-autowrap"
#define WINHELP_CTX_terminal_decom "config-decom"
#define WINHELP_CTX_terminal_lfhascr "config-crlf"
#define WINHELP_CTX_terminal_crhaslf "config-lfcr"
#define WINHELP_CTX_terminal_bce "config-erase"
#define WINHELP_CTX_terminal_blink "config-blink"
#define WINHELP_CTX_terminal_answerback "config-answerback"
#define WINHELP_CTX_terminal_localecho "config-localecho"
#define WINHELP_CTX_terminal_localedit "config-localedit"
#define WINHELP_CTX_terminal_printing "config-printing"
Add support for the SUPDUP protocol. Based on work by Josh Dersch, with permission.
2019-04-02 10:16:25 +00:00
#define WINHELP_CTX_supdup_location "supdup-location"
#define WINHELP_CTX_supdup_ascii "supdup-ascii"
#define WINHELP_CTX_supdup_more "supdup-more"
#define WINHELP_CTX_supdup_scroll "supdup-scroll"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_bell_style "config-bellstyle"
#define WINHELP_CTX_bell_taskbar "config-belltaskbar"
#define WINHELP_CTX_bell_overload "config-bellovl"
#define WINHELP_CTX_window_size "config-winsize"
#define WINHELP_CTX_window_resize "config-winsizelock"
#define WINHELP_CTX_window_scrollback "config-scrollback"
#define WINHELP_CTX_window_erased "config-erasetoscrollback"
#define WINHELP_CTX_behaviour_closewarn "config-warnonclose"
#define WINHELP_CTX_behaviour_altf4 "config-altf4"
#define WINHELP_CTX_behaviour_altspace "config-altspace"
#define WINHELP_CTX_behaviour_altonly "config-altonly"
#define WINHELP_CTX_behaviour_alwaysontop "config-alwaysontop"
#define WINHELP_CTX_behaviour_altenter "config-fullscreen"
#define WINHELP_CTX_appearance_cursor "config-cursor"
#define WINHELP_CTX_appearance_font "config-font"
#define WINHELP_CTX_appearance_title "config-title"
#define WINHELP_CTX_appearance_hidemouse "config-mouseptr"
#define WINHELP_CTX_appearance_border "config-winborder"
#define WINHELP_CTX_connection_termtype "config-termtype"
#define WINHELP_CTX_connection_termspeed "config-termspeed"
#define WINHELP_CTX_connection_username "config-username"
#define WINHELP_CTX_connection_username_from_env "config-username-from-env"
#define WINHELP_CTX_connection_keepalive "config-keepalive"
#define WINHELP_CTX_connection_nodelay "config-nodelay"
#define WINHELP_CTX_connection_ipversion "config-address-family"
#define WINHELP_CTX_connection_tcpkeepalive "config-tcp-keepalives"
#define WINHELP_CTX_connection_loghost "config-loghost"
#define WINHELP_CTX_proxy_type "config-proxy-type"
#define WINHELP_CTX_proxy_main "config-proxy"
#define WINHELP_CTX_proxy_exclude "config-proxy-exclude"
#define WINHELP_CTX_proxy_dns "config-proxy-dns"
#define WINHELP_CTX_proxy_auth "config-proxy-auth"
#define WINHELP_CTX_proxy_command "config-proxy-command"
#define WINHELP_CTX_proxy_logging "config-proxy-logging"
#define WINHELP_CTX_telnet_environ "config-environ"
#define WINHELP_CTX_telnet_oldenviron "config-oldenviron"
#define WINHELP_CTX_telnet_passive "config-ptelnet"
#define WINHELP_CTX_telnet_specialkeys "config-telnetkey"
#define WINHELP_CTX_telnet_newline "config-telnetnl"
#define WINHELP_CTX_rlogin_localuser "config-rlogin-localuser"
#define WINHELP_CTX_ssh_nopty "config-ssh-pty"
#define WINHELP_CTX_ssh_ttymodes "config-ttymodes"
#define WINHELP_CTX_ssh_noshell "config-ssh-noshell"
#define WINHELP_CTX_ssh_ciphers "config-ssh-encryption"
#define WINHELP_CTX_ssh_protocol "config-ssh-prot"
#define WINHELP_CTX_ssh_command "config-command"
#define WINHELP_CTX_ssh_compress "config-ssh-comp"
#define WINHELP_CTX_ssh_share "config-ssh-sharing"
#define WINHELP_CTX_ssh_kexlist "config-ssh-kex-order"
#define WINHELP_CTX_ssh_hklist "config-ssh-hostkey-order"
Add an option to disable the dynamic host key policy. This mitigates CVE-2020-14002: if you're in the habit of clicking OK to unknown host keys (the TOFU policy - trust on first use), then an active attacker looking to exploit that policy to substitute their own host key in your first connection to a server can use the host key algorithm order in your KEXINIT to (not wholly reliably) detect whether you have a key already stored for this host, and if so, abort their attack to avoid giving themself away. However, for users who _don't_ use the TOFU policy and instead check new host keys out of band, the dynamic policy is more useful. So it's provided as a configurable option.
2020-06-11 14:57:18 +00:00
#define WINHELP_CTX_ssh_hk_known "config-ssh-prefer-known-hostkeys"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_ssh_gssapi_kex_delegation "config-ssh-kex-gssapi-delegation"
#define WINHELP_CTX_ssh_kex_repeat "config-ssh-kex-rekey"
#define WINHELP_CTX_ssh_kex_manual_hostkeys "config-ssh-kex-manual-hostkeys"
Documentation for OpenSSH certificates. Also I've filled in the help contexts in all the new GUI controls.
2022-08-07 11:06:36 +00:00
#define WINHELP_CTX_ssh_kex_cert "config-ssh-kex-cert"
#define WINHELP_CTX_ssh_cert_valid_expr "config-ssh-cert-valid-expr"
#define WINHELP_CTX_ssh_cert_rsa_hash "config-ssh-cert-rsa-hash"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_ssh_auth_bypass "config-ssh-noauth"
New option to reject 'trivial' success of userauth. Suggested by Manfred Kaiser, who also wrote most of this patch (although outlying parts, like documentation and SSH-1 support, are by me). This is a second line of defence against the kind of spoofing attacks in which a malicious or compromised SSH server rushes the client through the userauth phase of SSH without actually requiring any auth inputs (passwords or signatures or whatever), and then at the start of the connection phase it presents something like a spoof prompt, intended to be taken for part of userauth by the user but in fact with some more sinister purpose. Our existing line of defence against this is the trust sigil system, and as far as I know, that's still working. This option allows a bit of extra defence in depth: if you don't expect your SSH server to trivially accept authentication in the first place, then enabling this option will cause PuTTY to disconnect if it unexpectedly does so, without the user having to spot the presence or absence of a fiddly little sigil anywhere. Several types of authentication count as 'trivial'. The obvious one is the SSH-2 "none" method, which clients always try first so that the failure message will tell them what else they can try, and which a server can instead accept in order to authenticate you unconditionally. But there are two other ways to do it that we know of: one is to run keyboard-interactive authentication and send an empty INFO_REQUEST packet containing no actual prompts for the user, and another even weirder one is to send USERAUTH_SUCCESS in response to the user's preliminary *offer* of a public key (instead of sending the usual PK_OK to request an actual signature from the key). This new option detects all of those, by clearing the 'is_trivial_auth' flag only when we send some kind of substantive authentication response (be it a password, a k-i prompt response, a signature, or a GSSAPI token). So even if there's a further path through the userauth maze we haven't spotted, that somehow avoids sending anything substantive, this strategy should still pick it up.
2021-06-19 14:39:15 +00:00
#define WINHELP_CTX_ssh_no_trivial_userauth "config-ssh-notrivialauth"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_ssh_auth_banner "config-ssh-banner"
#define WINHELP_CTX_ssh_auth_privkey "config-ssh-privkey"
New feature: k-i authentication helper plugins. In recent months I've had two requests from different people to build support into PuTTY for automatically handling complicated third-party auth protocols layered on top of keyboard-interactive - the kind of thing where you're asked to enter some auth response, and you have to refer to some external source like a web server to find out what the right response _is_, which is a pain to do by hand, so you'd prefer it to be automated in the SSH client. That seems like a reasonable thing for an end user to want, but I didn't think it was a good idea to build support for specific protocols of that kind directly into PuTTY, where there would no doubt be an ever-lengthening list, and maintenance needed on all of them. So instead, in collaboration with one of my correspondents, I've designed and implemented a protocol to be spoken between PuTTY and a plugin running as a subprocess. The plugin can opt to handle the keyboard-interactive authentication loop on behalf of the user, in which case PuTTY passes on all the INFO_REQUEST packets to it, and lets it make up responses. It can also ask questions of the user if necessary. The protocol spec is provided in a documentation appendix. The entire configuration for the end user consists of providing a full command line to use as the subprocess. In the contrib directory I've provided an example plugin written in Python. It gives a set of fixed responses suitable for getting through Uppity's made-up k-i system, because that was a reasonable thing I already had lying around to test against. But it also provides example code that someone else could pick up and insert their own live response-provider into the middle of, assuming they were happy with it being in Python.
2022-09-01 18:38:46 +00:00
#define WINHELP_CTX_ssh_auth_plugin "config-ssh-authplugin"
Documentation for OpenSSH certificates. Also I've filled in the help contexts in all the new GUI controls.
2022-08-07 11:06:36 +00:00
#define WINHELP_CTX_ssh_auth_cert "config-ssh-cert"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_ssh_auth_agentfwd "config-ssh-agentfwd"
#define WINHELP_CTX_ssh_auth_changeuser "config-ssh-changeuser"
#define WINHELP_CTX_ssh_auth_pageant "config-ssh-tryagent"
#define WINHELP_CTX_ssh_auth_tis "config-ssh-tis"
#define WINHELP_CTX_ssh_auth_ki "config-ssh-ki"
#define WINHELP_CTX_ssh_gssapi "config-ssh-auth-gssapi"
#define WINHELP_CTX_ssh_gssapi_delegation "config-ssh-auth-gssapi-delegation"
#define WINHELP_CTX_ssh_gssapi_libraries "config-ssh-auth-gssapi-libraries"
#define WINHELP_CTX_selection_buttons "config-mouse"
#define WINHELP_CTX_selection_shiftdrag "config-mouseshift"
#define WINHELP_CTX_selection_rect "config-rectselect"
#define WINHELP_CTX_selection_linedraw "config-linedrawpaste"
#define WINHELP_CTX_selection_autocopy "config-selection-autocopy"
#define WINHELP_CTX_selection_clipactions "config-selection-clipactions"
#define WINHELP_CTX_selection_pastectrl "config-paste-ctrl-char"
#define WINHELP_CTX_copy_charclasses "config-charclasses"
#define WINHELP_CTX_copy_rtf "config-rtfcopy"
#define WINHELP_CTX_colours_ansi "config-ansicolour"
#define WINHELP_CTX_colours_xterm256 "config-xtermcolour"
#define WINHELP_CTX_colours_truecolour "config-truecolour"
#define WINHELP_CTX_colours_bold "config-boldcolour"
#define WINHELP_CTX_colours_system "config-syscolour"
#define WINHELP_CTX_colours_logpal "config-logpalette"
#define WINHELP_CTX_colours_config "config-colourcfg"
#define WINHELP_CTX_translation_codepage "config-charset"
#define WINHELP_CTX_translation_cjk_ambig_wide "config-cjk-ambig-wide"
#define WINHELP_CTX_translation_cyrillic "config-cyr"
#define WINHELP_CTX_translation_linedraw "config-linedraw"
#define WINHELP_CTX_translation_utf8linedraw "config-utf8linedraw"
#define WINHELP_CTX_ssh_tunnels_x11 "config-ssh-x11"
#define WINHELP_CTX_ssh_tunnels_x11auth "config-ssh-x11auth"
#define WINHELP_CTX_ssh_tunnels_xauthority "config-ssh-xauthority"
#define WINHELP_CTX_ssh_tunnels_portfwd "config-ssh-portfwd"
#define WINHELP_CTX_ssh_tunnels_portfwd_localhost "config-ssh-portfwd-localhost"
#define WINHELP_CTX_ssh_tunnels_portfwd_ipversion "config-ssh-portfwd-address-family"
#define WINHELP_CTX_ssh_bugs_ignore1 "config-ssh-bug-ignore1"
#define WINHELP_CTX_ssh_bugs_plainpw1 "config-ssh-bug-plainpw1"
#define WINHELP_CTX_ssh_bugs_rsa1 "config-ssh-bug-rsa1"
#define WINHELP_CTX_ssh_bugs_ignore2 "config-ssh-bug-ignore2"
#define WINHELP_CTX_ssh_bugs_hmac2 "config-ssh-bug-hmac2"
#define WINHELP_CTX_ssh_bugs_derivekey2 "config-ssh-bug-derivekey2"
#define WINHELP_CTX_ssh_bugs_rsapad2 "config-ssh-bug-sig"
#define WINHELP_CTX_ssh_bugs_pksessid2 "config-ssh-bug-pksessid2"
#define WINHELP_CTX_ssh_bugs_rekey2 "config-ssh-bug-rekey"
#define WINHELP_CTX_ssh_bugs_maxpkt2 "config-ssh-bug-maxpkt2"
Work around key algorithm naming change in OpenSSH <= 7.7. When you send a "publickey" USERAUTH_REQUEST containing a certified RSA key, and you want to use a SHA-2 based RSA algorithm, modern OpenSSH expects you to send the algorithm string as rsa-sha2-NNN-cert-v01@openssh.com. But 7.7 and earlier didn't recognise those names, and expected the algorithm string in the userauth request packet to be ssh-rsa-cert-v01@... and would then follow it with an rsa-sha2-NNN signature. OpenSSH itself has a bug workaround for its own older versions. Follow suit.
2023-05-04 17:24:18 +00:00
#define WINHELP_CTX_ssh_bugs_rsa_sha2_cert_userauth "config-ssh-bug-rsa-sha2-cert-userauth"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_ssh_bugs_winadj "config-ssh-bug-winadj"
#define WINHELP_CTX_ssh_bugs_chanreq "config-ssh-bug-chanreq"
#define WINHELP_CTX_ssh_bugs_oldgex2 "config-ssh-bug-oldgex2"
Bug workaround to delay sending our SSH greeting. Ian Jackson recently tried to use the recipe in the psusan manpage for talking to UML, and found that the connection was not successfully set up, because at some point during startup, UML read the SSH greeting (ok, the bare-ssh-connection greeting) from its input fd and threw it away. So by the time psusan was run by the guest init process, the greeting wasn't there to be read. Ian's report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991958 I was also able to reproduce this locally, which makes me wonder why I _didn't_ notice it when I originally wrote that part of the psusan man page. It worked for me before, honest! But now it doesn't. Anyway. The ssh verstring module already has a mode switch to decide whether we ought to send our greeting before or after waiting for the other side's greeting (because that decision varies between client and server, and between SSH-1 and SSH-2). So it's easy to implement an override that forces it to 'wait for the server greeting first'. I've added this as yet another bug workaround flag. But unlike all the others, it can't be autodetected from the server's version string, because, of course, we have to act on it _before_ seeing the server's greeting and version string! So it's a manual-only flag. However, I've mentioned it in the UML section of the psusan man page, since that's the place where I _know_ people are likely to need to use this flag.
2021-08-14 09:56:20 +00:00
#define WINHELP_CTX_ssh_bugs_dropstart "config-ssh-bug-dropstart"
New bug workaround: KEXINIT filtering. We've occasionally had reports of SSH servers disconnecting as soon as they receive PuTTY's KEXINIT. I think all such reports have involved the kind of simple ROM-based SSH server software you find in small embedded devices. I've never been able to prove it, but I've always suspected that one possible cause of this is simply that PuTTY's KEXINIT is _too long_, either in number of algorithms listed or in total length (especially given all the ones that end in @very.long.domain.name suffixes). If I'm right about either of those being the cause, then it's just become even more likely to happen, because of all the extra Diffie-Hellman groups and GSSAPI algorithms we just threw into our already-long list in the previous few commits. A workaround I've had in mind for ages is to wait for the server's KEXINIT, and then filter our own down to just the algorithms the server also mentioned. Then our KEXINIT is no longer than that of the server, and hence, presumably fits in whatever buffer it has. So I've implemented that workaround, in anticipation of it being needed in the near future. (Well ... it's not _quite_ true that our KEXINIT is at most the same length as the server. In fact I had to leave in one KEXINIT item that won't match anything in the server's list, namely "ext-info-c" which gates access to SHA-2 based RSA. So if we turn out to support absolutely everything on all the server's lists, then our KEXINIT would be a few bytes longer than the server's, even with this workaround. But that would only cause trouble if the server's outgoing KEXINIT was skating very close to whatever buffer size it has for the incoming one, and I'm guessing that's not very likely.) ((Another possible cause of this kind of disconnection would be a server that simply objects to seeing any KEXINIT string it doesn't know how to speak. But _surely_ no such server would have survived initial testing against any full-featured client at all!))
2022-08-30 17:51:33 +00:00
#define WINHELP_CTX_ssh_bugs_filter_kexinit "config-ssh-bug-filter-kexinit"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_serial_line "config-serial-line"
#define WINHELP_CTX_serial_speed "config-serial-speed"
#define WINHELP_CTX_serial_databits "config-serial-databits"
#define WINHELP_CTX_serial_stopbits "config-serial-stopbits"
#define WINHELP_CTX_serial_parity "config-serial-parity"
#define WINHELP_CTX_serial_flow "config-serial-flow"
Initial support for HTML Help. All the ad-hoc help-file finding code and various calls to WinHelp() have been centralised into a new file winhelp.c, which in turn has been modified to detect a .CHM file as well as .HLP and select between them as appropriate. It explicitly tries to load HHCTRL.OCX and use GetProcAddress, meaning that it _should_ still work correctly on pre-HTML-Help platforms, falling gracefully back to WinHelp, but although I tested this by temporarily renaming my own HHCTRL.OCX I haven't yet been able to test it on a real HTML-Help-free platform. Also in this checkin: a new .but file and docs makefile changes to make it convenient to build the sources for a .CHM. As yet, owing to limitations of Halibut's CHM support, I'm not able to write a .CHM directly, more's the pity. [originally from svn r7000]
2006-12-17 11:16:07 +00:00
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_pageant_general "pageant"
#define WINHELP_CTX_pageant_keylist "pageant-mainwin-keylist"
#define WINHELP_CTX_pageant_addkey "pageant-mainwin-addkey"
#define WINHELP_CTX_pageant_remkey "pageant-mainwin-remkey"
winpgnt: add context help for 'Add Key (encrypted)' button. I wrote a docs section, but forgot to link it to the context help.
2021-04-04 08:34:50 +00:00
#define WINHELP_CTX_pageant_deferred "pageant-deferred-decryption"
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_pgpfingerprints "pgpkeys"
#define WINHELP_CTX_puttygen_general "pubkey-puttygen"
#define WINHELP_CTX_puttygen_keytype "puttygen-keytype"
#define WINHELP_CTX_puttygen_bits "puttygen-strength"
#define WINHELP_CTX_puttygen_generate "puttygen-generate"
#define WINHELP_CTX_puttygen_fingerprint "puttygen-fingerprint"
#define WINHELP_CTX_puttygen_comment "puttygen-comment"
#define WINHELP_CTX_puttygen_passphrase "puttygen-passphrase"
#define WINHELP_CTX_puttygen_savepriv "puttygen-savepriv"
#define WINHELP_CTX_puttygen_savepub "puttygen-savepub"
#define WINHELP_CTX_puttygen_pastekey "puttygen-pastekey"
#define WINHELP_CTX_puttygen_load "puttygen-load"
#define WINHELP_CTX_puttygen_conversions "puttygen-conversions"
winpgen: Context help for PPK params.
2021-04-20 15:06:01 +00:00
#define WINHELP_CTX_puttygen_ppkver "puttygen-save-ppk-version"
#define WINHELP_CTX_puttygen_kdfparam "puttygen-save-passphrase-hashing"
Documentation for OpenSSH certificates. Also I've filled in the help contexts in all the new GUI controls.
2022-08-07 11:06:36 +00:00
#define WINHELP_CTX_errors_cert_mismatch "errors-cert-mismatch"
The Windows host key dialogs now have a `Help' button that should give appropriate context help, iff the help file is present. (Shame it's prey to `winhelp-crash'.) (I've perpetrated a widening of visibility of `hwnd'; the alternative, putting it into a frontend handle, seemed too likely to cause maintenance trouble if we don't also _use_ that frontend handle everywhere we now use the global `hwnd'.) [originally from svn r5309]
2005-02-15 22:23:47 +00:00
/* These are used in Windows-specific bits of the frontend.
* We (ab)use "help context identifiers" (dwContextId) to identify them. */
#define HELPCTXID(x) WINHELP_CTXID_ ## x
Move the MessageBox-with-help function out into winutils.c, although it's still only used for the host key popups. Side-effects: - requested_help is a winstuff.h global - Pageant now defines winstuff.h globals (Also, my previous fix to my improved host-key dialogs only got the "changed" case, not the "unknown" case. Some days I shouldn't be let near a keyboard.) [originally from svn r5415]
2005-03-01 00:00:09 +00:00
#define WINHELP_CTXID_no_help 0
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_errors_hostkey_absent "errors-hostkey-absent"
The Windows host key dialogs now have a `Help' button that should give appropriate context help, iff the help file is present. (Shame it's prey to `winhelp-crash'.) (I've perpetrated a widening of visibility of `hwnd'; the alternative, putting it into a frontend handle, seemed too likely to cause maintenance trouble if we don't also _use_ that frontend handle everywhere we now use the global `hwnd'.) [originally from svn r5309]
2005-02-15 22:23:47 +00:00
#define WINHELP_CTXID_errors_hostkey_absent 1
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_errors_hostkey_changed "errors-hostkey-wrong"
The Windows host key dialogs now have a `Help' button that should give appropriate context help, iff the help file is present. (Shame it's prey to `winhelp-crash'.) (I've perpetrated a widening of visibility of `hwnd'; the alternative, putting it into a frontend handle, seemed too likely to cause maintenance trouble if we don't also _use_ that frontend handle everywhere we now use the global `hwnd'.) [originally from svn r5309]
2005-02-15 22:23:47 +00:00
#define WINHELP_CTXID_errors_hostkey_changed 2
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_errors_cantloadkey "errors-cant-load-key"
Add context help to a couple of message boxes. Unfortunately the ones I wanted to get to -- "software caused connection abort" and friends -- are going to be more involved (probably requiring some cross-platform notion of help contexts), and these ones hardly seem worth the effort. Still, I've done it now. Side-effect: Pageant now uses the same `hinst' and `hwnd' globals as everything else. Tested basic functionality. [originally from svn r5417]
2005-03-01 01:16:57 +00:00
#define WINHELP_CTXID_errors_cantloadkey 3
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_option_cleanup "using-cleanup"
Add context help to a couple of message boxes. Unfortunately the ones I wanted to get to -- "software caused connection abort" and friends -- are going to be more involved (probably requiring some cross-platform notion of help contexts), and these ones hardly seem worth the effort. Still, I've done it now. Side-effect: Pageant now uses the same `hinst' and `hwnd' globals as everything else. Tested basic functionality. [originally from svn r5417]
2005-03-01 01:16:57 +00:00
#define WINHELP_CTXID_option_cleanup 4
Remove most traces of WinHelp support. Remove the 'winhelp-topic' IDs from the Halibut source, and from the code. Now we have one fewer name to think of every time we add a setting. I've left the HELPCTX system in place, with the vague notion that it might be a useful layer of indirection for some future help system on a platform like Mac OS X. (I've left the putty.hlp target in doc/Makefile, if nothing else because this is a convenient test case for Halibut's WinHelp support. But the resulting help file will no longer support context help.)
2019-03-26 00:27:04 +00:00
#define WINHELP_CTX_pgp_fingerprints "pgpkeys"
Try to make our PGP signing more useful: * All the PuTTY tools for Windows and Unix now contain the fingerprints of the Master Keys. The method for accessing them is crude but universal: a new "-pgpfp" command-line option. (Except Unix PuTTYgen, which takes "--pgpfp" just to be awkward.) * Move the key policy discussion from putty-website/keys.html to putty/doc/pgpkeys.but, and autogenerate the former from the latter. Also tweak the text somewhat and include the fingerprints of the Master Keys themselves. (I've merged the existing autogeneration scripts into a single new one; I've left the old scripts and keys.html around until such time as the webmonster reviews the changes and plumbs in the new script; he should remove the old files then.) [originally from svn r5524] [this svn revision also touched putty-website]
2005-03-19 02:26:58 +00:00
#define WINHELP_CTXID_pgp_fingerprints 5
Reference in New Issue Copy Permalink