We use hosts allow in smb.conf to restrict access to shares. After upgrading to 3.5.1 host allow only functions based on ip addresses and not on names. If we put in the host file the following entry as an exaple ::ffff:10.1.100.12 ntserver.dom.nl Then hosts allow work. It looks like version 3.5.1 uses ipv6 ip addresses Is there a way to use old ipv4 behaviour? System is redhat V4
I think this fixable, by using IPV6_V6ONLY on ipv6 the sockets. And I planed to change that, but I was unsure about the side effects. maybe people rely on that bug in there setups. Volker, Jeremy and Günther what do you think, should be change the behavior?
Can we check for both? Volker
For access checks we could. The problem I see is the %I substitution for things like include = . Where we might need to change the behavior. My preference would be to never represent ipv4 addresses as ipv6 addresses in %I.
(In reply to comment #3) > For access checks we could. > > The problem I see is the %I substitution for things like include = . > Where we might need to change the behavior. > > My preference would be to never represent ipv4 addresses as ipv6 > addresses in %I. Yes. That sounds good. I find it way confusing when %I resolves to ::ffff:10.1.100.12 on ipv4 interfaces.
Created attachment 6524 [details] Patch for v3-5 In 3.6 we have the full fix including usage of IPV6_V6ONLY. (c4c49be416aeac890628c9a9f2fd7975860884d4) For 3.5.x we should only backport the patch with less impact. (62b2083c627abeb8a2fb7e5adc793c630d0d561c)
Comment on attachment 6524 [details] Patch for v3-5 Looks good to me.
Re-assigning to Karolin for inclusion in 3.5.9. Jeremy.
Pushed to v3-5-test, will be included in 3.5.9. Closing out bug report. Thanks!