Differences
This shows you the differences between the selected revisions of the page.
2016-02-28 | 2016-04-01 | ||
agent forwarding link update (martin) | updating from putty doc (martin) | ||
Line 11: | Line 11: | ||
===== Bypassing Authentication ===== | ===== Bypassing Authentication ===== | ||
- | In SSH-2, it is possible to establish a connection without using SSH's mechanisms to identify or authenticate oneself to the server. Some servers may simply require no authentication whatsoever. | + | In SSH-2, it is in principle possible to establish a connection without using SSH's mechanisms to identify or prove who you are to the server. Some servers may simply require no authentication whatsoever. |
- | By default, WinSCP assumes the server requires authentication (most do), and thus must provide a username. If you find you are getting unwanted username prompts, you could try checking //Bypass authentication entirely//. | + | By default, WinSCP assumes the server requires authentication (we've never heard of one that doesn't), and thus must start this process with a username. If you find you are getting username prompts that you cannot answer, you could try enabling //Bypass authentication entirely//. However, most %%SSH%% servers will reject this. |
- | This option only affects SSH-2 connections. SSH-1 connections always require an authentication step. ((&puttydoccite)) | + | This is not the option you want if you have a username and just want WinSCP to remember it; It's also probably not what if you're trying to set up passwordless |
+ | login to a mainstream %%SSH%% server; depending on the server, you probably wanted [[public_key|public-key authentication]] or perhaps [[#gssapi|GSSAPI authentication]]. (These are still forms of authentication, even if you don't have to interact with them.) | ||
+ | |||
+ | This option only affects %%SSH-2%% connections. SSH-1 connections always require an authentication step. ((&puttydoccite)) | ||
===== Authentication Options ===== | ===== Authentication Options ===== |