search

goodjack / scriptno

Automatically exported from code.google.com/p/scriptno
0 stars 0 forks source link

does not parse ipv6-literals properly #131

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. visit http://ipv6-test.com
2. look at the scripts loaded, see "[2001"

What is the expected output? What do you see instead?
"[2001:f00::1]"

What version of the product are you using? On what operating system?
Debian 6/64 bit/chrome 20.0.1132.57

Original issue reported on code.google.com by desoxyrebonukleinsaure@gmail.com on 27 Aug 2012 at 1:47

GoogleCodeExporter commented 8 years ago 
I noticed this recently and saw that this bug was reported two years ago. Since 
IPv6 is getting more widespread, is it possible to give this more priority?

I can add '[2001' and I guess that will work (not tested), but I do not want to 
allow all IPv6-addresses from that range (since I suspect that will happen).

Thanks in advance!

Running Chrome Version 36.0.1985.125 on OS X Mavericks (10.9.4)

Original comment by mholtk...@gmail.com on 24 Sep 2014 at 9:54

GoogleCodeExporter commented 8 years ago 
The problem still exists. 

If we are only allowed to trust the first 16 Bits (e. g. "[2001") it will work 
but the problem is that we are also trust ALL 2001-Adresses which are 112 Bits 
of adress-space - way more than the whole ipv4-adress space available. So 
please add ipv6-support.

Chrome 40.0.2214.93 m, Windows 7, ScriptSafe v1.0.6.18

Original comment by loveisli...@googlemail.com on 29 Jan 2015 at 12:17