nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-01 03:22:48 -05:00
Code Issues Projects Releases Wiki Activity

New option to allow use of the local OS username for login to the remote side

Browse Source 
if we have no better ideas, with UI shamelessly stolen from Quest PuTTY.

Off by default, which effectively reverts the change to using the local
username by default that came in with GSSAPI support in r8138. Anyone wanting
seamless single sign-on will need to set the new option. (The previous
default behaviour was getting in the way in ad-hoc scenarios.)

Note that the PSCP and Unix-Plink behaviour of using the local username by
default have remained unchanged throughout; they are not affected by the new
option. Not sure if that's the Right Thing.

[originally from svn r8324]
[r8138 == de5dd9d65c]
This commit is contained in:
Jacob Nevins
2008-11-24 17:51:42 +00:00
parent c9326ad81b
commit dc896b79af
8 changed files with 96 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/config.but
View File

@ -1788,6 +1788,22 @@ it explicitly every time. (Some Telnet servers don't support this.)
In this box you can type that user name.
\S{config-username-from-env} \q{Use of system username}
\cfg{winhelp-topic}{connection.usernamefromenv}
When the previous box (\k{config-username}) is left blank, by default,
PuTTY will prompt for a username at the time you make a connection.
In some environments, such as large corporate networks with \i{single
sign-on}, a more sensible default may be to use the name of the user
logged in to the local operating system (if any). This control allows
you to change the default behaviour.
The current system username is displayed in the dialog as a
convenience. It is not saved in the configuration; if a saved session
is later used by a different user, that user's name will be used.
\S{config-termtype} \q{\ii{Terminal-type} string}
\cfg{winhelp-topic}{connection.termtype}