IPv6 Compliance
Bug #1422264 reported by
Ghada El-Zoghbi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Mahara: 15.04
DB: any
Browser: any
OS: any
Currently, Mahara is not compliant with the IPv6 protocol.
Some places that need to change (where IP addresses are validated/checked):
- SAML auth - validate URL Syntax (preg_match for IPv6 also).
- DB: table - host.ipaddress needs to cater for 128 bit address.
- Peer bootstrap:
1) preg-match should also include IPv6 format;
2) use of PHP function gethostbyname().
- Zend third part library - current version only supports IPv4. We currently use version 1.10.6.
MNET heavily relise on Zend.
The latest Zend is on version 3. But there is a release for 1.12.11 - which still doesn't support IPv6 (as far as I can tell).
Changed in mahara: | |
milestone: | none → 15.04.0 |
importance: | Undecided → Medium |
tags: | added: mnet |
Changed in mahara: | |
status: | New → Confirmed |
Changed in mahara: | |
milestone: | 15.04.0 → 15.04.1 |
no longer affects: | mahara/1.8 |
no longer affects: | mahara/1.9 |
no longer affects: | mahara/1.10 |
Changed in mahara: | |
milestone: | 16.10.1 → 17.04.0 |
no longer affects: | mahara/16.10 |
no longer affects: | mahara/16.04 |
no longer affects: | mahara/15.04 |
no longer affects: | mahara/15.10 |
Changed in mahara: | |
milestone: | 17.04.0 → 17.10.0 |
Changed in mahara: | |
milestone: | 17.10.0 → 18.04.0 |
Changed in mahara: | |
milestone: | 18.04.0 → 18.10.0 |
Changed in mahara: | |
milestone: | 18.10.0 → 19.04.0 |
Changed in mahara: | |
milestone: | 19.04.0 → none |
Changed in mahara: | |
importance: | Medium → Wishlist |
To post a comment you must log in.
It's 2015, we really should support IPv6! :)
Probably the biggest problem out of the cases listed above is the "HOST.IPADDRESS" column. If the IP address of an MNet host comes back as IPv6, this bug would prevent it from being useable.
In the other cases, it's only a problem if you're accessing a server by its IP address instead of by a hostname. If you're doing admin type stuff, and the server you need to connect to doesn't have a hostname for some reason, there is the workaround of assigning the IP a hostname in the /etc/hosts file.
I guess there's also the scenario where you are a user trying to specify an IP address, like maybe putting one in for the URL of an RSS feed. But that seems like it should be somewhat rarer. There are not that many web servers that are only identified by IP address.