[SERVER-15835] Ipv6 address parsing still accepts ambiguous strings Created: 28/Oct/14  Updated: 27/Oct/15  Resolved: 29/Oct/14

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 2.8.0-rc0

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Done Votes: 0
Labels: 28qa, pull-request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-5436 IPv6 address ambiguity in HostPort sy... Closed
is related to DOCS-1947 Document: IPv6 address ambiguity in H... Closed
Operating System: ALL
Participants:

 Description   

e.g.
HostAndPort("124d:efg:34") will succeed as host "124d:efg" on port 34, but should fail. To get that host/port combo, we should require the [] format: HostAndPort("[124d:efg]:34")



 Comments   
Comment by Githook User [ 28/Oct/14 ]

Author:

{u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'cswanson310@gmail.com'}

Message: SERVER-15835 Require brackets around hostname for ipv6 addresses

Closes #842

Signed-off-by: Benety Goh <benety@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/05bb8e47cabe6ebe025b4cc94027124816f25c3a

Comment by Charlie Swanson [ 28/Oct/14 ]

thanks!

Comment by Bernie Hackett [ 28/Oct/14 ]

See https://www.ietf.org/rfc/rfc2732.txt

Generated at Thu Feb 08 03:39:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.