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

Version number and other tweakings prior to the 0.58 release.

Browse Source 
[originally from svn r5598]
This commit is contained in:
Simon Tatham
2005-04-05 19:36:25 +00:00
parent 989185f35e
commit 398ec35fe1
8 changed files with 17 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/faq.but
View File

@ -1013,10 +1013,8 @@ leave. You can do that automatically, by running the command
the currently logged-in user on \i{multi-user systems}.)
If PuTTY was installed from the installer package, it will also
appear in \q{Add/Remove Programs}.
\#{XXX-REMOVE-BEFORE-RELEASE - replace with: Older versions of the uninstaller do not}
Uninstallation does not currently
remove the above-mentioned registry entries and file.
appear in \q{Add/Remove Programs}. Older versions of the uninstaller
do not remove the above-mentioned registry entries and file.
\S{faq-dsa}{Question} How come PuTTY now supports \i{DSA}, when the
website used to say how insecure it was?

12
doc/pgpkeys.but
View File

@ -12,13 +12,11 @@ accurate idea of what each signature guarantees.
This description is provided as both a web page on the PuTTY site, and
an appendix in the PuTTY manual.
As of the next release, all of the PuTTY executables will contain
\#{XXX-REMOVE-BEFORE-RELEASE: fix this up for forthcoming release
As of release 0.58, all of the PuTTY executables contain}
fingerprint material (usually accessed via the \i\c{-pgpfp}
command-line option), such that if you have an executable you trust,
you can use it to establish a trust path, for instance to a newer
version downloaded from the Internet.
As of release 0.58, all of the PuTTY executables contain fingerprint
material (usually accessed via the \i\c{-pgpfp} command-line
option), such that if you have an executable you trust, you can use
it to establish a trust path, for instance to a newer version
downloaded from the Internet.
(Note that none of the keys, signatures, etc mentioned here have
anything to do with keys used with SSH - they are purely for verifying

2
doc/plink.but
View File

@ -43,7 +43,7 @@ use Plink:
\c Z:\sysosd>plink
\c PuTTY Link: command-line connection utility
\c Release 0.XX
\c Release 0.58
\c Usage: plink [options] [user@]host [command]
\c ("host" can also be a PuTTY saved session name)
\c Options:

2
doc/pscp.but
View File

@ -41,7 +41,7 @@ use PSCP:
\c Z:\owendadmin>pscp
\c PuTTY Secure Copy client
\c Release 0.XX
\c Release 0.58
\c Usage: pscp [options] [user@]host:source target
\c pscp [options] source [source...] [user@]host:target
\c pscp [options] -ls [user@]host:filespec