Open Bug 264632 Opened 16 years ago Updated 2 years ago

wpad: integrate eTLD service


(Core :: Networking, enhancement, P5)





(Reporter: benc, Unassigned)


(Keywords: helpwanted, Whiteboard: [necko-would-take])

from bug 28998.
------- Additional Comment #88 From Mike Shaver  2004-09-02 10:20 PDT  

I'd happily review a patch to use a whitelist (preferably one that can be stored
in a resource file outside compiled code, for easier updating in the field) for
additional checks, but I'm not going to get to it myself any time soon.  The
current code works for most (virtually all?) installations, and I'm strapped for
time in the 1.0 schedule anyway.

Note that it must be the case that failing to update the WPAD domain whitelist
causes WPAD to fail in a case that it might otherwise succeed, and not open us
up to attacks when a new TLD or sub-TLD is brought online.
Severity: normal → enhancement
Keywords: helpwanted
Target Milestone: --- → Future
shaver: I've read bug 28998, but it's not totally clear - could you tell us
exactly what the current behaviour is? Does it stop searching at the 4th level
for all domains?

Assignee: darin → nobody
QA Contact: benc → networking
Target Milestone: Future → ---

Is there a proper way to modify this bug so it says: wpad needs to be hooked up to effective TLD service?

I'm still getting caught up on what that new stuff does.
benc: Just change the title :-) I think that it would be absolutely right for WPAD to use the Effective TLD service.

Summary: wpad: update service for TLD whitelists → wpad: integrate eTLD service
Whiteboard: [necko-would-take]
Bulk change to priority:
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.