Description of problem: ----------------------- The rsync program allows to restrict the origin of connections to an rsync server instance by using the "hosts allow" directive in the rsyncd.conf configuration file (or an other configuration file, as the case may be). See rsyncd.conf(5). The man page indicates that IPv4 or IPv6 addresses can be used as values to "hosts allow". However, if one uses an IPv4 address A.B.C.D as value (on a system where IPv6 is enabled but not actively used) then the address of the connecting client is not recognized. For example: In case of "hosts allow = 88.207.188.205" the logfile say: ---------- forward name lookup for ip-88-207-188-205.dyn.luxdsl.pt.lu failed: Name or service not known rsync denied on module mayas-twiki-snapshot from unknown (::ffff:88.207.188.205) ---------- However, In case of "hosts allow = ::ffff:88.207.188.205" the logfile say: ---------- forward name lookup for ip-88-207-188-205.dyn.luxdsl.pt.lu failed: Name or service not known rsync allowed access on module mayas-twiki-snapshot from unknown (::ffff:88.207.188.205) ---------- ...which is nice. So the workaround is straightforward. Note: I did not find an rsync bugzilla entry concerning this problem. Version-Release number of selected component (if applicable): rsync-2.6.3-1 How reproducible: Always
Just moved this to RHL5. hosts allow = ::ffff:88.207.188.205 will now fail but hosts allow = 88.207.188.205 will succeed
Could you please provide reference to RHEL5 bug if one exists? Since there is only one more release of RHEL4 planned and it will be focused on performance and security, this bug most likely won't be fixed in RHEL4.
Hi There doesn't seem to be any (as it actually works in RHEL5). Well, this bug can probably be disregarded as there are no "Me Too"s to it, right? Also, it's old.
Yes, that's my opinion as well. Thanks for cooperation, I'm closing this bug as WONTFIX.