similar to: [Bug 1675] New: rsync cannot cope with literal IPv6 addresses

Displaying 20 results from an estimated 3000 matches similar to: "[Bug 1675] New: rsync cannot cope with literal IPv6 addresses"

2007 Feb 05
4
DO NOT REPLY [Bug 1675] rsync cannot cope with literal IPv6 addresses
https://bugzilla.samba.org/show_bug.cgi?id=1675 luke-jr+sambabugs@utopios.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luke- | |jr+sambabugs@utopios.org ------- Comment #2 from
2006 Aug 13
5
DO NOT REPLY [Bug 4016] New: literal IPv6 addresses not supported in ssh protocol
https://bugzilla.samba.org/show_bug.cgi?id=4016 Summary: literal IPv6 addresses not supported in ssh protocol Product: rsync Version: 2.6.9 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: david.madore@ens.fr
2009 Jan 27
1
DO NOT REPLY [Bug 6067] New: IPv6 literal addresses broken
https://bugzilla.samba.org/show_bug.cgi?id=6067 Summary: IPv6 literal addresses broken Product: rsync Version: 3.0.4 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: arekm@maven.pl QAContact:
2003 Nov 13
2
IPv6 literal addresses on command line
Hello all, Can anyone give me a hint on how to specify an IPv6 address in an rsync address literal - the colon character is already used to seperate the host name from the remote directory AFAICT... I get, e.g. rsync -Cavb 3ffe:502:420:120::2:/home/cam/dev/proj 3ffe: Unknown host rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code
2010 Mar 09
2
2.0beta3 10876:370ee9717a6c broke listen on literal IPv6 address
Hi, apparently the following change in dovecot hg * New revision (10876:370ee9717a6c) in dovecot Mercurial repository: - config: Forgot to add header file. broke listen = 83.170.6.69, 2001:1b10:1000::110:1:1 mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:29: listen=..:port has been replaced by service {
2009 Nov 24
1
[Bug 1675] New: SSH over Bluetooth support
https://bugzilla.mindrot.org/show_bug.cgi?id=1675 Summary: SSH over Bluetooth support Product: Portable OpenSSH Version: 5.3p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: unassigned-bugs at mindrot.org ReportedBy: dwmw2 at
2011 Apr 27
4
[Bug 1894] New: ssh requests ipv6 addresses even with ipv6 disabled
https://bugzilla.mindrot.org/show_bug.cgi?id=1894 Summary: ssh requests ipv6 addresses even with ipv6 disabled Product: Portable OpenSSH Version: 5.8p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: unassigned-bugs at mindrot.org
2011 Mar 07
0
Bug#617232: logcheck: ignore regexes match ipv4 addresses only, causing false positives with ipv6 addresses.
Package: logcheck Version: 1.3.13 Severity: normal Various files under ignore.d.* use "[0-9.]{7,15}" to match an IPv4 address, e.g., a connection to rsyncd. However, this does not match IPv6 addresses, causing spurious reports. A better regexp might be something like: ([0-9.]{7,15}|[0-9a-f:]{2,39}) -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990,
2007 Jun 13
0
pf does not use IPv6 interface addresses at startups
>Submitter-Id: current-users >Originator: Janos Mohacsi >Organization: NIIF/HUNGARNET >Confidential: no >Synopsis: pf does not use IPv6 interface addresses at startups >Severity: serious >Priority: low >Category: bin >Class: sw-bug >Release: FreeBSD 6.2-STABLE i386 >Environment: System: FreeBSD scone.ki.iif.hu 6.2-STABLE FreeBSD 6.2-STABLE #23: Wed May 9 18:23:24
2005 Jun 30
0
Problem with IPSec tunnel, using IPv6 addresses, .........
Hi All, In the previous mail, I have sent is only the problem that occurs, because of using IPv6 addresses. But the connection works with IPv4 addresses without any problem. Thanx, Mohan. __________________________________________________________ How much free photo storage do you get? Store your friends 'n family snaps for FREE with Yahoo! Photos http://in.photos.yahoo.com
2003 Aug 28
0
[Fwd: [Shorewall-devel] Getting confused by IPv6 addresses]
The versions of the CVS ''firewall'' script in both the /Shorewall and /STABLE threads corrects the problem described in the attached post. These scripts should be installed on the 1.4.7 Beta and 1.4.6c releases respectively. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net -------------- next
2006 Nov 07
1
Bug#397466: logcheck-database: proftpd rules do not support IPv6 addresses with UseReverseDNS off
Package: logcheck-database Version: 1.2.49 Severity: normal Tags: patch Hi, with "UseReverseDNS off" in /etc/proftpd/proftpd.conf the IP is used instead of the hostname: ... (::ffff:aaa.bbb.ccc.ddd[::ffff:aaa.bbb.ccc.ddd]) ... The rules in /etc/logcheck/ignore.d.server/proftpd do not support colons in the hostname. The attached patch fixes this. Greetings, Gregor -- System
2012 Oct 13
0
IPv6 Link Local Addresses
With FreeBSD 9.1-RC2 you can assign the same link local address manually to two different hosts on the same network. The Neighbor Solicitations are not responded to and you end up with non-working addresses. The simple way to reproduce this is to boot two systems on the same network and get the link local for system 1. Shut it off and manually assign that address to system 2. Then boot system
2002 Apr 26
3
[Bug 180] [PATCH] sshd sets no ToS bit on connections with IPv4-mapped IPv6 addresses
http://bugzilla.mindrot.org/show_bug.cgi?id=180 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From djm at mindrot.org 2002-04-26 16:55
2009 Jun 05
1
[Bug 1602] New: ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Summary: ssh: doesn't handle IPv6 addresses with brackets Product: Portable OpenSSH Version: 5.2p1 Platform: All OS/Version: Linux Status: NEW Keywords: low-hanging-fruit Severity: normal Priority: P2 Component: ssh AssignedTo:
2015 Nov 18
0
[Bug 1602] ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.herbert+mindrot at gmail. | |com --- Comment #1
2020 May 15
0
[Bug 1602] ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #6 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Just did some more testing with OpenSSH_8.1p1 Apr 2020. It looks like someone did the work to implement a new ssh://[brackets] syntax except in the case where brackets are actually needed. Baffling. So these now work: ssh ssh://[host.local]:23 ssh
2020 May 16
0
[Bug 1602] ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Marc Herbert <marc.herbert+mindrot at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #7 from Marc Herbert
2020 May 30
0
[Bug 1602] ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 --- Comment #8 from Marc Herbert <marc.herbert+mindrot at gmail.com> --- Fun fact: ssh _does_ produce brackets for IPv6 addresses in .ssh/known_hosts: [review.openstack.org]:29418,[104.130.246.32]:29418 ssh-rsa AAAAB3NzaC1yc2... [review.openstack.org]:29418,[2001:4800:7819:103:be76:4eff:fe04:9229]:29418 ssh-rsa AAAAB3Nza... But it
2020 May 30
0
[Bug 1602] ssh: doesn't handle IPv6 addresses with brackets
https://bugzilla.mindrot.org/show_bug.cgi?id=1602 Darren Tucker <dtucker at dtucker.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at dtucker.net --- Comment #9 from Darren Tucker <dtucker at dtucker.net> --- (In reply to Marc