|
PuTTY IPv6
URL: http://unfix.org/projects/ipv6/
Yet another PuTTY IPv6 patch has been released. Some of the changes:
Fixed IPv6 addresses (3ffe:8114::1) being entered as hostnames.
Added Auto|IPv4|IPv6 combobox to the config settings allowing one to choose which Address Family to use.
Added -4, -6, -ipv4 and -ipv6 options to the commandline options.
Tunnels can now be requested to be IPv4 only or IPv6 only.
PuTTY IPv6
Another update, fixing the vulnerability fixed in 0.55 and bringing it current with the CVS of 2004-08-25:
8<----------
PuTTY IPv6 has been updated to the current 2004-08-25 CVS. This thus brings it up to par to the 0.55 version which fixes a vulnerability Additionally scp now also supports eg. jeroen@[2001:db8::2]:blaat.txt as a format. Binaries, patch and zip are of course available from the page.
----------->8
http://unfix.org/projects/ipv6/
PuTTY IPv6
![[se]](/s/countries/se.gif) Shadow Hawkins on Saturday, 04 September 2004 12:33:03
Will there be a updated version against latest stable release? It fixes a security issue.
PuTTY IPv6
Read the thread and check the website....
PuTTY IPv6
![[si]](/s/countries/si.gif) Shadow Hawkins on Thursday, 03 June 2010 19:13:14
Reviving this thread, since my question fits the subject.
Has anyone successfully deployed IPv6 SSH tunnels over IPv6 with putty?
I have a problem with putty recognizing IPv6 address/port pair in the destination field (Config:Connection/SSH/Tunnels).
I also tried poderosa, another free ssh client, and it also fails to establish IPv6 over IPv6 tunnel. IPv4 over IPv6 works fine in both.
PuTTY IPv6
![[us]](/s/countries/us.gif) Shadow Hawkins on Saturday, 31 July 2010 10:01:15
My first thought was to tell you that you need to enclose literal IPv6 addresses in brackets [], but then I tried making IPv6 tunnels work for :3389 and :22 which I've done lots in IPv6 and couldn't make them work in the few minutes I tried. I tried with PuTTY 0.6 .
PuTTY IPv6
Shadow Hawkins on Thursday, 25 November 2010 12:25:01
To answer my own question, it is possible to do it with a workaround.
Entering an IPv6 address seems impossible even with current builds, but if you enter a hostname it works. Just enter the destination as hostname6:port . Note that this hostname6 must resolve into IPv6 address on the ssh server and does not need to resolve on the ssh client.
I have tested this and it works with IPv6 and IPv4 as transport.
PuTTY IPv6
![[fr]](/s/countries/fr.gif) Shadow Hawkins on Tuesday, 30 November 2010 14:50:07
There is a known bug : PuTTY bug ipv6-literals
"summary: Better handling of literal IPv6 addresses"
and some comments from Jeroen here : http://unfix.org/projects/ipv6/
"Command line IPv6 addresses would require quite a lot of changes in the parsing code breaking backward compatibility"
For my own use, I started to write a patch for plink some years ago (www.ip6.fr, in french). Now, I've got a complete patch for putty/plink/pscp and co (SVN version around 11/22/2010). For me, It works fine with ipv6 literal adresses even for ssh tunnels. Also, I've got patched version of filezilla 3.3.5.1 to make socks 5 proxying with ipv6 literal addresses.
Before publishing it and submitting to the Putty team, it would be great to have some more tests.
PuTTY IPv6
Updated version dated on the CVS of 2003-07-25 can be found again at Unfix IPv6 Projects
|
![[ch]](/s/countries/ch.gif)
on Monday, 03 March 2003 03:58:43
Posting is only allowed when you are