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

Add some extra documentation: filled in the Getting Started chapter,

Browse Source 
added an introduction to public key authentication, and made a
couple of changes in intro.but. Transatlantic flights have some uses
after all.

[originally from svn r1146]
This commit is contained in:
Simon Tatham
2001-06-15 19:31:10 +00:00
parent 56aa28467b
commit 35bdd95a56
3 changed files with 192 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/intro.but
View File

@ -49,7 +49,7 @@ be accessed using Telnet.
You probably do \e{not} want to use SSH, Telnet or Rlogin if:
\b you only use Windows machines. Windows machines have their own
\b you only use Windows. Windows computers have their own
ways of networking between themselves, and unless you are doing
something fairly unusual, you will not need to use any of these
remote login protocols.
@ -75,8 +75,9 @@ it has been a constant source of security problems.
\b SSH and Rlogin both allow you to log in to the server without
having to type a password. (Rlogin's method of doing this is
insecure, and can allow an attacker to access your account on the
server. SSH's method is much more secure, and typically requires the
attacker to have gained access to your actual client machine.)
server. SSH's method is much more secure, and typically breaking the
security requires the attacker to have gained access to your actual
client machine.)
\b SSH allows you to connect to the server and automatically send a
command, so that the server will run that command and then
@ -90,5 +91,3 @@ administrator to install it.
If you are behind a good firewall, it is more likely to be safe to
use Telnet or Rlogin, but we still recommend you use SSH.
\# perhaps a section on terminal emulation?