Support ipv6 network addresses in proton pass.
In the areas I work and at home, much of my network stack and equipment is built on IPV6. Proton pass currently reads ipv6 addresses as invalid urls which makes retrieving credentials for direct connections quite inconvenient. This would be an immense QOL feature for myself, and potentially many others that interact with IPV6 networks.
Even something as simple as http://[fe80::1]
does not work.
-
Kevin Nadjarian commented
It's imposible to enter an IPv6 address it's recognised as faulty by Proton Pass
e.g https://[###:###:###:####:###:###:###:####]/ui/system/shell ( I changed the digit for hashtags.)According to Proton this is an expected behaviour. this doesn't seems right to me.
-
Mick O commented
I've had a similar experience. What make this into a bug and worse is the Android client supports IPv6 and you can save IPv6 entries, yet if you then try to edit those entries on the web, chrome or the macOS client, either of those clients won't allow you to save any updates without deleting the IPv6 entry added by the Android client. I'm told the this is a "feature" - it's very frustrating especially given the lack of empathy from the support and development teams on this issue. This is basic stuff.