Closed Bug 255238 Opened 21 years ago Closed 21 years ago

creating a new profile in firefox (via profile manager) doesn't salt directory name

Categories

(Toolkit :: Startup and Profile System, defect)

defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: Brade, Assigned: benjamin)

References

Details

(Keywords: fixed-aviary1.0, Whiteboard: [have patch] in 256076)

I've been doing lots of testing with seamonkey and firefox builds lately. I noticed that new profiles I created with firefox 0.9.3 on Windows do not have salted directory names. Steps: * run firefox with profile manager * delete all existing profiles * create a new profile naming it: default * notice that the directory is named "default"
Flags: blocking-aviary1.0+
btw: blocking-aviary1.0 + is per shaver (via bsmedberg)
Yeah, I've been meaning to fix this. It essentially involves adding salting to http://lxr.mozilla.org/aviarybranch/source/toolkit/profile/content/createProfileWizard.js#80 and http://lxr.mozilla.org/aviarybranch/source/toolkit/profile/content/createProfileWizard.js#141 (will need a little regexp-love there to replace the ==).
Status: NEW → ASSIGNED
We should make salting less annyoing by using default-xxxxxxxx/ instead of default/xxxxxxxx.slt/
Yeah, we already do that for the default profile. This bug only affects profile created from the UI.
Re: jesse's comment 3: Firefox already went with something like what you suggest, but because of 8.3 mapping constraints, the combined profile+salt directory name has only 3(!) chars of salt. That's bug 256076. We need to fix that bug and this one for 1.0PR1. /be
Depends on: 256076
Flags: blocking-aviary1.0PR+
Why does 8.3 matter? Is it because an attacker could bypass the salt using "Defaul~1" otherwise?
Patch in 256076 covers this as well.
Whiteboard: [have patch] in 256076
Fixed on trunk and branch
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Keywords: fixed-aviary1.0
Resolution: --- → FIXED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.