Closed Bug 281365 Opened 19 years ago Closed 19 years ago

network.enableIDN has no effect

Categories

(Core :: Networking, defect)

1.7 Branch
x86
All
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 261934

People

(Reporter: caspar-mozilla, Assigned: darin.moz)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041222
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041222

I just set network.enableIDN to false.  After setting I tried to reach
http://www.müller.de, which failed.

After restart of Browser I am able to reach that site again.  about:config
shows, that network.enableIDN is still set to false.

I set the parameter in /usr/lib/mozilla/greprefs/all.js which only changed "user
set" to "default" and I was able to reach the above mentioned site.

I set up a new profile and I can still reach the site.

Reproducible: Always

Steps to Reproduce:
1. try to reach http://www.müller.de
2. set network.enableIDN to false
3. retry http://www.müller.de
4. restart mozilla
5. retry http://www.müller.de
Actual Results:  
1. site reachable
3. site not reachable
5. site reachable

Expected Results:  
5. site unreachable

Daniel Bachfeld of Heise Security reproduced this error with firefox.

I set this to confidential due to the fact that it is a workaround against the
phishing problem using different encodings.
Assignee: prefs → darin
Component: Preferences → Networking
Product: Mozilla Application Suite → Core
QA Contact: benc
Version: unspecified → 1.7 Branch
*** Bug 281383 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.7.6?
Flags: blocking-aviary1.0.1?
transferring blocking flags from dupe
Flags: blocking1.7.6?
Flags: blocking1.7.6+
Flags: blocking-aviary1.0.1?
Flags: blocking-aviary1.0.1+
Clearing confidential flag
Group: security
*** Bug 281377 has been marked as a duplicate of this bug. ***
Is works OK on trunk, possibly fixed by the patch in Bug 261934.
Like thousands of people, I've just tested this behavior on Windows instead of
Linux. Specifically, Firefox 1.0 on Windows 98... I'm not sure if this data
should go in this bug, or if the Windows stuff should be a different (but
related) bug. I'm assuming it should all go here; please let me know if I'm wrong.

On Win98, setting enableIDN to "false" works just fine until restart. Upon
restart, the value automatically changes back to "true"! This is, IMO, less
wrong but more surprising than the behavior others have reported.

I changed the variable's value by typing "about: config" in the address bar,
scrolling down to the right line, and hitting "Enter".
Works for me on Win XP with the current 1.0.1 nightly.
this is extra-special important in light of
http://www.shmoo.com/idn/homograph.txt
changing OS to all as this has been seen on windows as well.
OS: Linux → All
network.enableIDN does appear to work correctly on
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050111
*** Bug 281436 has been marked as a duplicate of this bug. ***
I'll take care of landing this on the stable branches.
> I'll take care of landing this on the stable branches.

Doh.. wrong bug :(
The patch in bug 261934 fixes this bug as well.

*** This bug has been marked as a duplicate of 261934 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
*** Bug 281506 has been marked as a duplicate of this bug. ***
patch from bug 261934 checked in, this is fixed on branches.
Status: RESOLVED → VERIFIED
Flags: blocking1.7.6+
Flags: blocking-aviary1.0.1+
You need to log in before you can comment on or make changes to this bug.