URL character mask for external protocols

RESOLVED WONTFIX

Status

()

Core
Networking
--
enhancement
RESOLVED WONTFIX
15 years ago
2 years ago

People

(Reporter: benc, Unassigned)

Tracking

({helpwanted})

Trunk
Future
x86
Windows 98
helpwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
Darin and I have spoken about this in the context of telnet:, but I am also
thinking this might be relevant to the new interest that gopher: and finger:
have generated.

If we are going to support URL's that point to external protocol handlers, it
seems that we should provide some facility for masking the URLs, and making
things like illegal characters in DNS and control-characters in interactive
sessions go away.

Darin had a couple examples for telnet, and I think we have good examples in
bugzilla for ftp and gopher as well.

Finger is a pretty notoriously insecure service already, I think I had seen some
really bad hostname parsing in it when I tested it about a year ago as well.
(Reporter)

Updated

15 years ago
Keywords: helpwanted

Updated

15 years ago
Severity: normal → enhancement
Target Milestone: --- → Future
Is finger external?
finger is internal, if enabled - it's an optional extension; but I don't know if
it's enabled by default or not.

Comment 3

15 years ago
finger is disabled by default.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.