Consistently use a single notation to refer to SSH protocol versions, as
authorjacob <jacob@cda61777-01e9-0310-a592-d414129be87e>
Thu, 10 Mar 2005 16:36:05 +0000 (16:36 +0000)
committerjacob <jacob@cda61777-01e9-0310-a592-d414129be87e>
Thu, 10 Mar 2005 16:36:05 +0000 (16:36 +0000)
commit2e85c969d67eb14a07314802d4ac5dd63eef660b
tree17d14ad150cc31d59ec12dc994e34439f59a0662
parent07d0323b84c7a00129cccca645db8d222378d33c
Consistently use a single notation to refer to SSH protocol versions, as
discussed. Use Barrett and Silverman's convention of "SSH-1" for SSH protocol
version 1 and "SSH-2" for protocol 2 ("SSH1"/"SSH2" refer to ssh.com
implementations in this scheme). <http://www.snailbook.com/terms.html>

git-svn-id: svn://svn.tartarus.org/sgt/putty@5480 cda61777-01e9-0310-a592-d414129be87e
30 files changed:
cmdgen.c
config.c
contrib/kh2reg.py
doc/config.but
doc/errors.but
doc/faq.but
doc/man-pg.but
doc/man-putt.but
doc/pageant.but
doc/pscp.but
doc/psftp.but
doc/pubkey.but
doc/using.but
import.c
pscp.c
psftp.c
putty.h
ssh.c
ssh.h
sshblowf.c
sshbn.c
sshdes.c
sshpubk.c
sshsha.c
terminal.c
unix/uxcons.c
windows/wincons.c
windows/windlg.c
windows/winpgen.c
windows/winpgnt.c