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

Switch chiark URLs to https.

Browse Source
This commit is contained in:
Simon Tatham 2017-05-07 16:29:01 +01:00
parent ad694a4941
commit 6ea9d36ae9
21 changed files with 47 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Buildscr
View File

@ -172,7 +172,7 @@ delegate windows
# provide a 'more info' URL, and an optional -n option to provide a # provide a 'more info' URL, and an optional -n option to provide a
# program name, and that it can take multiple .exe filename # program name, and that it can take multiple .exe filename
# arguments and sign them all in place. # arguments and sign them all in place.
ifneq "$(winsigncode)" "" in putty/windows do $(winsigncode) -i http://www.chiark.greenend.org.uk/~sgtatham/putty/ build*/*.exe ifneq "$(winsigncode)" "" in putty/windows do $(winsigncode) -i https://www.chiark.greenend.org.uk/~sgtatham/putty/ build*/*.exe
# Ignore exit code from hhc, in favour of seeing whether the .chm # Ignore exit code from hhc, in favour of seeing whether the .chm
# file was created. (Yuck; but hhc appears to return non-zero # file was created. (Yuck; but hhc appears to return non-zero
@ -187,7 +187,7 @@ delegate windows
in putty/windows with innosetup do/win iscc putty.iss in putty/windows with innosetup do/win iscc putty.iss
# Sign the installers. # Sign the installers.
ifneq "$(winsigncode)" "" in putty/windows do $(winsigncode) -i http://www.chiark.greenend.org.uk/~sgtatham/putty/ -n "PuTTY Installer" installer32.msi installer64.msi Output/installer.exe ifneq "$(winsigncode)" "" in putty/windows do $(winsigncode) -i https://www.chiark.greenend.org.uk/~sgtatham/putty/ -n "PuTTY Installer" installer32.msi installer64.msi Output/installer.exe
# Finished Windows builds. # Finished Windows builds.
return putty/windows/buildold/*.exe return putty/windows/buildold/*.exe

4
README
View File

@ -127,11 +127,11 @@ Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc' `man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory using `doc/Makefile'. If you aren't using one of our subdirectory using `doc/Makefile'. If you aren't using one of our
source snapshots, you'll need to do this yourself. Halibut can be source snapshots, you'll need to do this yourself. Halibut can be
found at <http://www.chiark.greenend.org.uk/~sgtatham/halibut/>. found at <https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is The PuTTY home web site is
http://www.chiark.greenend.org.uk/~sgtatham/putty/ https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line Feedback section of the web site before doing so. Sending one-line

2
contrib/cygtermd/README
View File

@ -8,4 +8,4 @@ install it in Cygwin's /bin, and configure PuTTY to use it as a local
proxy process. For detailed instructions, see the PuTTY Wishlist page proxy process. For detailed instructions, see the PuTTY Wishlist page
at at
http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/cygwin-terminal-window.html https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/cygwin-terminal-window.html

2
doc/blurb.but
View File

@ -7,7 +7,7 @@
\cfg{xhtml-leaf-contains-contents}{true} \cfg{xhtml-leaf-contains-contents}{true}
\cfg{xhtml-body-end}{<p>If you want to provide feedback on this manual \cfg{xhtml-body-end}{<p>If you want to provide feedback on this manual
or on the PuTTY tools themselves, see the or on the PuTTY tools themselves, see the
<a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html">Feedback <a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html">Feedback
page</a>.</p>} page</a>.</p>}
\cfg{html-template-fragment}{%k}{%b} \cfg{html-template-fragment}{%k}{%b}

18
doc/faq.but
View File

@ -27,18 +27,18 @@ else.
\I{supported features}In general, if you want to know if PuTTY supports \I{supported features}In general, if you want to know if PuTTY supports
a particular feature, you should look for it on the a particular feature, you should look for it on the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}{PuTTY web site}. \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/}{PuTTY web site}.
In particular: In particular:
\b try the \b try the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{changes \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{changes
page}, and see if you can find the feature on there. If a feature is page}, and see if you can find the feature on there. If a feature is
listed there, it's been implemented. If it's listed as a change made listed there, it's been implemented. If it's listed as a change made
\e{since} the latest version, it should be available in the \e{since} the latest version, it should be available in the
development snapshots, in which case testing will be very welcome. development snapshots, in which case testing will be very welcome.
\b try the \b try the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist
page}, and see if you can find the feature there. If it's on there, page}, and see if you can find the feature there. If it's on there,
and not in the \q{Recently fixed} section, it probably \e{hasn't} been and not in the \q{Recently fixed} section, it probably \e{hasn't} been
implemented. implemented.
@ -54,7 +54,7 @@ version 0.52.
\cw{ssh.com} SSH-2 private key files? \cw{ssh.com} SSH-2 private key files?
PuTTY doesn't support this natively (see PuTTY doesn't support this natively (see
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/key-formats-natively.html}{the wishlist entry} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/key-formats-natively.html}{the wishlist entry}
for reasons why not), but as of 0.53 for reasons why not), but as of 0.53
PuTTYgen can convert both OpenSSH and \cw{ssh.com} private key PuTTYgen can convert both OpenSSH and \cw{ssh.com} private key
files into PuTTY's format. files into PuTTY's format.
@ -236,7 +236,7 @@ port, or any other port of PuTTY, they were mistaken. We don't.
There are some third-party ports to various platforms, mentioned There are some third-party ports to various platforms, mentioned
on the on the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/links.html}{Links page of our website}. \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/links.html}{Links page of our website}.
\S{faq-unix}{Question} \I{Unix version}Is there a port to Unix? \S{faq-unix}{Question} \I{Unix version}Is there a port to Unix?
@ -323,7 +323,7 @@ for, it might be a long time before any of us get round to learning
a new system and doing the port for that. a new system and doing the port for that.
However, some of the work has been done by other people; see the However, some of the work has been done by other people; see the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/links.html}{Links page of our website} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/links.html}{Links page of our website}
for various third-party ports. for various third-party ports.
\S{faq-iphone}{Question} Will there be a port to the iPhone? \S{faq-iphone}{Question} Will there be a port to the iPhone?
@ -351,7 +351,7 @@ Most of the code cleanup work would be a good thing to happen in
general, so if anyone feels like helping, we wouldn't say no. general, so if anyone feels like helping, we wouldn't say no.
See also See also
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/dll-frontend.html}{the wishlist entry}. \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/dll-frontend.html}{the wishlist entry}.
\S{faq-vb}{Question} Is the SSH or Telnet code available as a Visual \S{faq-vb}{Question} Is the SSH or Telnet code available as a Visual
Basic component? Basic component?
@ -891,7 +891,7 @@ us \q{I wanted the F1 key to send \c{^[[11~}, but instead it's
sending \c{^[OP}, can this be done?}, or something similar. sending \c{^[OP}, can this be done?}, or something similar.
You should still read the You should still read the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html}{Feedback \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/feedback.html}{Feedback
page} on the PuTTY website (also provided as \k{feedback} in the page} on the PuTTY website (also provided as \k{feedback} in the
manual), and follow the guidelines contained in that. manual), and follow the guidelines contained in that.
@ -1060,7 +1060,7 @@ still. We do not recommend it.)
This is caused by a bug in certain versions of \i{Windows XP} which This is caused by a bug in certain versions of \i{Windows XP} which
is triggered by PuTTY 0.58. This was fixed in 0.59. The is triggered by PuTTY 0.58. This was fixed in 0.59. The
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/xp-wont-run}{\q{xp-wont-run}} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/xp-wont-run}{\q{xp-wont-run}}
entry in PuTTY's wishlist has more details. entry in PuTTY's wishlist has more details.
\S{faq-system32}{Question} When I put 32-bit PuTTY in \S{faq-system32}{Question} When I put 32-bit PuTTY in

18
doc/feedback.but
View File

@ -112,7 +112,7 @@ If you think you have found a bug in PuTTY, your first steps should
be: be:
\b Check the \b Check the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist
page} on the PuTTY website, and see if we already know about the page} on the PuTTY website, and see if we already know about the
problem. If we do, it is almost certainly not necessary to mail us problem. If we do, it is almost certainly not necessary to mail us
about it, unless you think you have extra information that might be about it, unless you think you have extra information that might be
@ -121,12 +121,12 @@ specific extra information about a particular bug, the Wishlist page
will say so.) will say so.)
\b Check the \b Check the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{Change \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{Change
Log} on the PuTTY website, and see if we have already fixed the bug Log} on the PuTTY website, and see if we have already fixed the bug
in the \i{development snapshots}. in the \i{development snapshots}.
\b Check the \b Check the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html}{FAQ} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html}{FAQ}
on the PuTTY website (also provided as \k{faq} in the manual), and on the PuTTY website (also provided as \k{faq} in the manual), and
see if it answers your question. The FAQ lists the most common see if it answers your question. The FAQ lists the most common
things which people think are bugs, but which aren't bugs. things which people think are bugs, but which aren't bugs.
@ -188,7 +188,7 @@ you haven't supplied us with full information about the actual bug,
then we won't be able to find a better solution. then we won't be able to find a better solution.
\b \b
\W{http://www.chiark.greenend.org.uk/~sgtatham/bugs.html}\cw{http://www.chiark.greenend.org.uk/~sgtatham/bugs.html} \W{https://www.chiark.greenend.org.uk/~sgtatham/bugs.html}\cw{https://www.chiark.greenend.org.uk/~sgtatham/bugs.html}
is an article on how to report bugs effectively in general. If your is an article on how to report bugs effectively in general. If your
bug report is \e{particularly} unclear, we may ask you to go away, bug report is \e{particularly} unclear, we may ask you to go away,
read this article, and then report the bug again. read this article, and then report the bug again.
@ -224,14 +224,14 @@ If you want to request a new feature in PuTTY, the very first things
you should do are: you should do are:
\b Check the \b Check the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist
page} on the PuTTY website, and see if your feature is already on page} on the PuTTY website, and see if your feature is already on
the list. If it is, it probably won't achieve very much to repeat the list. If it is, it probably won't achieve very much to repeat
the request. (But see \k{feedback-feature-priority} if you want to the request. (But see \k{feedback-feature-priority} if you want to
persuade us to give your particular feature higher priority.) persuade us to give your particular feature higher priority.)
\b Check the Wishlist and \b Check the Wishlist and
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{Change \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{Change
Log} on the PuTTY website, and see if we have already added your Log} on the PuTTY website, and see if we have already added your
feature in the development snapshots. If it isn't clear, download feature in the development snapshots. If it isn't clear, download
the latest development snapshot and see if the feature is present. the latest development snapshot and see if the feature is present.
@ -350,7 +350,7 @@ Of course, if the web site has some other error (Connection Refused,
If you want to report a problem with our web site, check that you're If you want to report a problem with our web site, check that you're
looking at our \e{real} web site and not a mirror. The real web site looking at our \e{real} web site and not a mirror. The real web site
is at is at
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}\c{http://www.chiark.greenend.org.uk/~sgtatham/putty/}; \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/}\c{https://www.chiark.greenend.org.uk/~sgtatham/putty/};
if that's not where you're reading this, then don't report the if that's not where you're reading this, then don't report the
problem to us until you've checked that it's really a problem with problem to us until you've checked that it's really a problem with
the main site. If it's only a problem with the mirror, you should the main site. If it's only a problem with the mirror, you should
@ -399,7 +399,7 @@ setting up a mirror. You already have permission.
If the mirror is in a country where we don't already have plenty of If the mirror is in a country where we don't already have plenty of
mirrors, we may be willing to add it to the list on our mirrors, we may be willing to add it to the list on our
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/mirrors.html}{mirrors \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/mirrors.html}{mirrors
page}. Read the guidelines on that page, make sure your mirror page}. Read the guidelines on that page, make sure your mirror
works, and email us the information listed at the bottom of the works, and email us the information listed at the bottom of the
page. page.
@ -414,7 +414,7 @@ to be a cheap way to gain search rankings.
If you have technical questions about the process of mirroring, then If you have technical questions about the process of mirroring, then
you might want to mail us before setting up the mirror (see also the you might want to mail us before setting up the mirror (see also the
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/mirrors.html#guidelines}{guidelines on the Mirrors page}); \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/mirrors.html#guidelines}{guidelines on the Mirrors page});
but if you just want to ask for permission, you don't need to. You but if you just want to ask for permission, you don't need to. You
already have permission. already have permission.

2
doc/man-pl.but
View File

@ -260,7 +260,7 @@ exists, nonzero otherwise.
For more information on plink, it's probably best to go and look at For more information on plink, it's probably best to go and look at
the manual on the PuTTY web page: the manual on the PuTTY web page:
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{http://www.chiark.greenend.org.uk/~sgtatham/putty/} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{https://www.chiark.greenend.org.uk/~sgtatham/putty/}
\S{plink-manpage-bugs} BUGS \S{plink-manpage-bugs} BUGS

2
doc/man-pscp.but
View File

@ -174,7 +174,7 @@ encrypted packet data.
For more information on \cw{pscp} it's probably best to go and look at For more information on \cw{pscp} it's probably best to go and look at
the manual on the PuTTY web page: the manual on the PuTTY web page:
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{http://www.chiark.greenend.org.uk/~sgtatham/putty/} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{https://www.chiark.greenend.org.uk/~sgtatham/putty/}
\S{pscp-manpage-bugs} BUGS \S{pscp-manpage-bugs} BUGS

2
doc/man-psft.but
View File

@ -159,7 +159,7 @@ at the \cw{psftp>} prompt.
For more information on \cw{psftp} it's probably best to go and look at For more information on \cw{psftp} it's probably best to go and look at
the manual on the PuTTY web page: the manual on the PuTTY web page:
\cw{http://www.chiark.greenend.org.uk/~sgtatham/putty/} \cw{https://www.chiark.greenend.org.uk/~sgtatham/putty/}
\S{psftp-manpage-bugs} BUGS \S{psftp-manpage-bugs} BUGS

2
doc/man-ptel.but
View File

@ -208,7 +208,7 @@ your home directory.
For more information on PuTTY and PuTTYtel, it's probably best to go For more information on PuTTY and PuTTYtel, it's probably best to go
and look at the manual on the web page: and look at the manual on the web page:
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{http://www.chiark.greenend.org.uk/~sgtatham/putty/} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{https://www.chiark.greenend.org.uk/~sgtatham/putty/}
\S{puttytel-manpage-bugs} BUGS \S{puttytel-manpage-bugs} BUGS

2
doc/man-putt.but
View File

@ -321,7 +321,7 @@ your home directory.
For more information on PuTTY, it's probably best to go and look at For more information on PuTTY, it's probably best to go and look at
the manual on the web page: the manual on the web page:
\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{http://www.chiark.greenend.org.uk/~sgtatham/putty/} \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/}\cw{https://www.chiark.greenend.org.uk/~sgtatham/putty/}
\S{putty-manpage-bugs} BUGS \S{putty-manpage-bugs} BUGS

20
doc/pgpkeys.but
View File

@ -53,19 +53,19 @@ The current issue of those keys are available for download from the
PuTTY website, and are also available on PGP keyservers using the key PuTTY website, and are also available on PGP keyservers using the key
IDs listed below. IDs listed below.
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/master-2015.asc}{\s{Master Key}} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/master-2015.asc}{\s{Master Key}}
\dd RSA, 4096-bit. Key ID: \cw{4096R/04676F7C} (long version: \dd RSA, 4096-bit. Key ID: \cw{4096R/04676F7C} (long version:
\cw{4096R/AB585DC604676F7C}). Fingerprint: \cw{4096R/AB585DC604676F7C}). Fingerprint:
\cw{440D\_E3B5\_B7A1\_CA85\_B3CC\_\_1718\_AB58\_5DC6\_0467\_6F7C} \cw{440D\_E3B5\_B7A1\_CA85\_B3CC\_\_1718\_AB58\_5DC6\_0467\_6F7C}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/release-2015.asc}{\s{Release Key}} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/release-2015.asc}{\s{Release Key}}
\dd RSA, 2048-bit. Key ID: \cw{2048R/B43434E4} (long version: \dd RSA, 2048-bit. Key ID: \cw{2048R/B43434E4} (long version:
\cw{2048R/9DFE2648B43434E4}). Fingerprint: \cw{2048R/9DFE2648B43434E4}). Fingerprint:
\cw{0054\_DDAA\_8ADA\_15D2\_768A\_\_6DE7\_9DFE\_2648\_B434\_34E4} \cw{0054\_DDAA\_8ADA\_15D2\_768A\_\_6DE7\_9DFE\_2648\_B434\_34E4}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/contact-2016.asc}{\s{Secure Contact Key}} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/contact-2016.asc}{\s{Secure Contact Key}}
\dd RSA, 2048-bit. Main key ID: \cw{2048R/8A0AF00B} (long version: \dd RSA, 2048-bit. Main key ID: \cw{2048R/8A0AF00B} (long version:
\cw{2048R/C4FCAAD08A0AF00B}). Encryption subkey ID: \cw{2048R/C4FCAAD08A0AF00B}). Encryption subkey ID:
@ -73,7 +73,7 @@ IDs listed below.
Fingerprint: Fingerprint:
\cw{8A26\_250E\_763F\_E359\_75F3\_\_118F\_C4FC\_AAD0\_8A0A\_F00B} \cw{8A26\_250E\_763F\_E359\_75F3\_\_118F\_C4FC\_AAD0\_8A0A\_F00B}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/snapshot-2015.asc}{\s{Snapshot Key}} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/snapshot-2015.asc}{\s{Snapshot Key}}
\dd RSA, 2048-bit. Key ID: \cw{2048R/D15F7E8A} (long version: \dd RSA, 2048-bit. Key ID: \cw{2048R/D15F7E8A} (long version:
\cw{2048R/EEF20295D15F7E8A}). Fingerprint: \cw{2048R/EEF20295D15F7E8A}). Fingerprint:
@ -179,37 +179,37 @@ Releases prior to the rollover are signed with the old Release Keys.
For completeness, those old keys are given here: For completeness, those old keys are given here:
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/master-rsa.asc}{\s{Master Key} (original RSA)} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/master-rsa.asc}{\s{Master Key} (original RSA)}
\dd RSA, 1024-bit. Key ID: \cw{1024R/1E34AC41} (long version: \dd RSA, 1024-bit. Key ID: \cw{1024R/1E34AC41} (long version:
\cw{1024R/9D5877BF1E34AC41}). Fingerprint: \cw{1024R/9D5877BF1E34AC41}). Fingerprint:
\cw{8F\_15\_97\_DA\_25\_30\_AB\_0D\_\_88\_D1\_92\_54\_11\_CF\_0C\_4C} \cw{8F\_15\_97\_DA\_25\_30\_AB\_0D\_\_88\_D1\_92\_54\_11\_CF\_0C\_4C}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/master-dsa.asc}{\s{Master Key} (original DSA)} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/master-dsa.asc}{\s{Master Key} (original DSA)}
\dd DSA, 1024-bit. Key ID: \cw{1024D/6A93B34E} (long version: \dd DSA, 1024-bit. Key ID: \cw{1024D/6A93B34E} (long version:
\cw{1024D/4F5E6DF56A93B34E}). Fingerprint: \cw{1024D/4F5E6DF56A93B34E}). Fingerprint:
\cw{313C\_3E76\_4B74\_C2C5\_F2AE\_\_83A8\_4F5E\_6DF5\_6A93\_B34E} \cw{313C\_3E76\_4B74\_C2C5\_F2AE\_\_83A8\_4F5E\_6DF5\_6A93\_B34E}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/release-rsa.asc}{\s{Release Key} (original RSA)} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/release-rsa.asc}{\s{Release Key} (original RSA)}
\dd RSA, 1024-bit. Key ID: \cw{1024R/B41CAE29} (long version: \dd RSA, 1024-bit. Key ID: \cw{1024R/B41CAE29} (long version:
\cw{1024R/EF39CCC0B41CAE29}). Fingerprint: \cw{1024R/EF39CCC0B41CAE29}). Fingerprint:
\cw{AE\_65\_D3\_F7\_85\_D3\_18\_E0\_\_3B\_0C\_9B\_02\_FF\_3A\_81\_FE} \cw{AE\_65\_D3\_F7\_85\_D3\_18\_E0\_\_3B\_0C\_9B\_02\_FF\_3A\_81\_FE}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/release-dsa.asc}{\s{Release Key} (original DSA)} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/release-dsa.asc}{\s{Release Key} (original DSA)}
\dd DSA, 1024-bit. Key ID: \cw{1024D/08B0A90B} (long version: \dd DSA, 1024-bit. Key ID: \cw{1024D/08B0A90B} (long version:
\cw{1024D/FECD6F3F08B0A90B}). Fingerprint: \cw{1024D/FECD6F3F08B0A90B}). Fingerprint:
\cw{00B1\_1009\_38E6\_9800\_6518\_\_F0AB\_FECD\_6F3F\_08B0\_A90B} \cw{00B1\_1009\_38E6\_9800\_6518\_\_F0AB\_FECD\_6F3F\_08B0\_A90B}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/snapshot-rsa.asc}{\s{Snapshot Key} (original RSA)} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/snapshot-rsa.asc}{\s{Snapshot Key} (original RSA)}
\dd RSA, 1024-bit. Key ID: \cw{1024R/32B903A9} (long version: \dd RSA, 1024-bit. Key ID: \cw{1024R/32B903A9} (long version:
\cw{1024R/FAAED21532B903A9}). Fingerprint: \cw{1024R/FAAED21532B903A9}). Fingerprint:
\cw{86\_8B\_1F\_79\_9C\_F4\_7F\_BD\_\_8B\_1B\_D7\_8E\_C6\_4E\_4C\_03} \cw{86\_8B\_1F\_79\_9C\_F4\_7F\_BD\_\_8B\_1B\_D7\_8E\_C6\_4E\_4C\_03}
\dt \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/keys/snapshot-dsa.asc}{\s{Snapshot Key} (original DSA)} \dt \W{https://www.chiark.greenend.org.uk/~sgtatham/putty/keys/snapshot-dsa.asc}{\s{Snapshot Key} (original DSA)}
\dd DSA, 1024-bit. Key ID: \cw{1024D/7D3E4A00} (long version: \dd DSA, 1024-bit. Key ID: \cw{1024D/7D3E4A00} (long version:
\cw{1024D/165E56F77D3E4A00}). Fingerprint: \cw{1024D/165E56F77D3E4A00}). Fingerprint:

2
doc/udp.but
View File

@ -331,7 +331,7 @@ local state structures \c{s} or \c{st} in each function, or the
backend-wide structure \c{ssh}. backend-wide structure \c{ssh}.
See See
\W{http://www.chiark.greenend.org.uk/~sgtatham/coroutines.html}\c{http://www.chiark.greenend.org.uk/~sgtatham/coroutines.html} \W{https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html}\c{https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html}
for a more in-depth discussion of what these macros are for and how for a more in-depth discussion of what these macros are for and how
they work. they work.

2
ssh.c
View File

@ -303,7 +303,7 @@ enum {
* macros look impenetrable to you, you might find it helpful to * macros look impenetrable to you, you might find it helpful to
* read * read
* *
* http://www.chiark.greenend.org.uk/~sgtatham/coroutines.html * https://www.chiark.greenend.org.uk/~sgtatham/coroutines.html
* *
* which explains the theory behind these macros. * which explains the theory behind these macros.
* *

2
windows/README-msi.txt
View File

@ -35,7 +35,7 @@ What do I do if it doesn't work?
The PuTTY home web site is The PuTTY home web site is
http://www.chiark.greenend.org.uk/~sgtatham/putty/ https://www.chiark.greenend.org.uk/~sgtatham/putty/
Here you will find our list of known bugs and pending feature Here you will find our list of known bugs and pending feature
requests. If your problem is not listed in there, or in the FAQ, or requests. If your problem is not listed in there, or in the FAQ, or

2
windows/README.txt
View File

@ -29,7 +29,7 @@ What do I do if it doesn't work?
The PuTTY home web site is The PuTTY home web site is
http://www.chiark.greenend.org.uk/~sgtatham/putty/ https://www.chiark.greenend.org.uk/~sgtatham/putty/
Here you will find our list of known bugs and pending feature Here you will find our list of known bugs and pending feature
requests. If your problem is not listed in there, or in the FAQ, or requests. If your problem is not listed in there, or in the FAQ, or

2
windows/putty.iss
View File

@ -19,7 +19,7 @@ VersionInfoTextVersion=Release 0.69
AppVersion=0.69 AppVersion=0.69
VersionInfoVersion=0.69.0.0 VersionInfoVersion=0.69.0.0
AppPublisher=Simon Tatham AppPublisher=Simon Tatham
AppPublisherURL=http://www.chiark.greenend.org.uk/~sgtatham/putty/ AppPublisherURL=https://www.chiark.greenend.org.uk/~sgtatham/putty/
AppReadmeFile={app}\README.txt AppReadmeFile={app}\README.txt
DefaultDirName={pf}\PuTTY DefaultDirName={pf}\PuTTY
DefaultGroupName=PuTTY DefaultGroupName=PuTTY

BIN
windows/website.url
View File

Binary file not shown.

2
windows/windlg.c
View File

@ -227,7 +227,7 @@ static INT_PTR CALLBACK AboutProc(HWND hwnd, UINT msg,
case IDA_WEB: case IDA_WEB:
/* Load web browser */ /* Load web browser */
ShellExecute(hwnd, "open", ShellExecute(hwnd, "open",
"http://www.chiark.greenend.org.uk/~sgtatham/putty/", "https://www.chiark.greenend.org.uk/~sgtatham/putty/",
0, 0, SW_SHOWDEFAULT); 0, 0, SW_SHOWDEFAULT);
return 0; return 0;
} }

2
windows/winpgen.c
View File

@ -322,7 +322,7 @@ static INT_PTR CALLBACK AboutProc(HWND hwnd, UINT msg,
case 102: case 102:
/* Load web browser */ /* Load web browser */
ShellExecute(hwnd, "open", ShellExecute(hwnd, "open",
"http://www.chiark.greenend.org.uk/~sgtatham/putty/", "https://www.chiark.greenend.org.uk/~sgtatham/putty/",
0, 0, SW_SHOWDEFAULT); 0, 0, SW_SHOWDEFAULT);
return 0; return 0;
} }

2
windows/winpgnt.c
View File

@ -178,7 +178,7 @@ static INT_PTR CALLBACK AboutProc(HWND hwnd, UINT msg,
case 102: case 102:
/* Load web browser */ /* Load web browser */
ShellExecute(hwnd, "open", ShellExecute(hwnd, "open",
"http://www.chiark.greenend.org.uk/~sgtatham/putty/", "https://www.chiark.greenend.org.uk/~sgtatham/putty/",
0, 0, SW_SHOWDEFAULT); 0, 0, SW_SHOWDEFAULT);
return 0; return 0;
} }