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

I added more detail to the `Authentication failed at PuTTY X11

Browse Source 
proxy' error message some time ago, but forgot to change the wording
in the error messages chapter.

[originally from svn r4235]
This commit is contained in:
Simon Tatham 2004-05-20 12:48:19 +00:00
parent d18cd16ca1
commit fdcdecace9
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/errors.but
View File

@ -1,4 +1,4 @@
\versionid $Id: errors.but,v 1.7 2003/07/12 13:25:43 jacob Exp $ \versionid $Id: errors.but,v 1.8 2004/05/20 12:48:19 simon Exp $
\C{errors} Common error messages \C{errors} Common error messages
@ -188,11 +188,11 @@ panel (see \k{config-ssh-bug-derivekey2}).
Another known server problem which can cause this error is described Another known server problem which can cause this error is described
in \k{faq-openssh-bad-openssl} in the FAQ. in \k{faq-openssh-bad-openssl} in the FAQ.
\H{errors-x11-proxy} \q{Authentication failed at PuTTY X11 proxy} \H{errors-x11-proxy} \q{PuTTY X11 proxy: \e{various errors}}
This error is reported when PuTTY is doing X forwarding. It is sent This family of errors are reported when PuTTY is doing X forwarding.
back to the X application running on the SSH server, which will They are sent back to the X application running on the SSH server,
usually report the error to the user. which will usually report the error to the user.
When PuTTY enables X forwarding (see \k{using-x-forwarding}) it When PuTTY enables X forwarding (see \k{using-x-forwarding}) it
creates a virtual X display running on the SSH server. This display creates a virtual X display running on the SSH server. This display
@ -203,10 +203,10 @@ details it needs to enable clients to connect, and the server should
put this mechanism in place automatically, so your X applications put this mechanism in place automatically, so your X applications
should just work. should just work.
A common reason why people see this message is because they used SSH A common reason why people see one of these messages is because they
to log in as one user (let's say \q{fred}), and then used the Unix used SSH to log in as one user (let's say \q{fred}), and then used
\c{su} command to become another user (typically \q{root}). The the Unix \c{su} command to become another user (typically \q{root}).
original user, \q{fred}, has access to the X authentication data The original user, \q{fred}, has access to the X authentication data
provided by the SSH server, and can run X applications which are provided by the SSH server, and can run X applications which are
forwarded over the SSH connection. However, the second user forwarded over the SSH connection. However, the second user
(\q{root}) does not automatically have the authentication data (\q{root}) does not automatically have the authentication data