Closed
Bug 129038
Opened 22 years ago
Closed 12 years ago
mozilla has "U;" in useragent when PSM is not installed
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bugzilla, Unassigned)
References
Details
(Whiteboard: [kerh-coz])
Isn't it wrong that the user agent string is Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8+) Gecko/20020304 when PSM is not installed. shouldn't it be: Mozilla/5.0 (Windows; N; Windows NT 5.0; en-US; rv:0.9.8+) Gecko/20020304 according to: http://www.mozilla.org/build/revised-user-agent-strings.html * N for no security * U for strong security * I for weak security 20020304
Updated•22 years ago
|
Priority: -- → P3
Target Milestone: --- → Future
Comment 1•21 years ago
|
||
I agree: See bug 224340 for an official real-life case !
Comment 3•20 years ago
|
||
Mass change "Future" target milestone to "--" on bugs that now are assigned to nobody. Those targets reflected the prioritization of past PSM management. Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
Comment 4•19 years ago
|
||
PSM is no longer optional, but contained in the builds by default. Is it still possible to compile Mozilla without crypto? If yes: we should fix this bug If no: this bug is invalid
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
Whiteboard: [kerh-coz]
(In reply to comment #4) > Is it still possible to compile Mozilla without crypto? Yes. > If yes: we should fix this bug
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Updated•17 years ago
|
QA Contact: junruh → ui
Comment 6•14 years ago
|
||
Since the encryption strength has been removed from the UA-string, does this still need to be addressed?
Comment 7•14 years ago
|
||
I bet it doesn't matter now.
Comment 9•12 years ago
|
||
marking wontfix
Status: REOPENED → RESOLVED
Closed: 19 years ago → 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•