Backport #3144: resolv-replace Changes IPAddr.new() Behavior, Degrades IP Validation Rules

• Status: Closed
• Assignee: shyouhei (Shyouhei Urabe)

[dotdotdotPaul (Paul Clegg)]

=begin
By default, calling IPAddr.new("1.2.3.256") results in an ArgumentError exception being raised.

If resolv-replace is require'd, however, the behavior changes; no exception is raised, and an IPAddr object with an IPv4 address of "1.2.3.0" is returned.

This appears to be due to the call to IPSocket.getaddress() being changed to use the Resolv object's getaddress call instead, and it is not raising exceptions on invalid IP addresses the same way.

It seems like the require'ing of resolv-replace should not change the behavior of IPAddr.new(); whether this means the Resolv lib needs to change to be more less forgiving of bogus IP addresses, or the IPAddr lib needs to be less dependent on IPSocket.getaddress(), I'm not sure.
=end

[mame (Yusuke Endoh)]

• Status changed from Open to Closed

=begin
Fixed at r27389. Thanks!

--
Yusuke Endoh [e-mail]
=end

[shyouhei (Shyouhei Urabe)]

• Status changed from Closed to Assigned
• Assignee set to shyouhei (Shyouhei Urabe)

=begin

=end

[shyouhei (Shyouhei Urabe)]

• Status changed from Assigned to Closed
• % Done changed from 0 to 100

=begin
This issue was solved with changeset r30303.
Paul, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

=end