Closed Bug 129038 Opened 23 years ago Closed 13 years ago

mozilla has "U;" in useragent when PSM is not installed

Categories

(Core Graveyard :: Security: UI, defect, P3)

Product:
Core Graveyard
Component:
Security: UI
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
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
Priority: -- → P3
Target Milestone: --- → Future
Blocks: 71569
I agree: See bug 224340 for an official real-life case !
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
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 → ---
Product: PSM → Core
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 → ---
QA Contact: junruh → ui
Version: psm1.01 → 1.0 Branch
Version: 1.0 Branch → Trunk
Since the encryption strength has been removed from the UA-string, does this still need to be addressed?
I bet it doesn't matter now.
Depends on: 572668
Wontfix?
marking wontfix
Status: REOPENED → RESOLVED
Closed: 19 years ago → 13 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.