Closed
Bug 30277
Opened 25 years ago
Closed 25 years ago
Users cannot update bookmarks in Win2K NTFS installs.
Categories
(SeaMonkey :: Installer, defect, P3)
Tracking
(Not tracked)
M16
People
(Reporter: kberk.spamaway, Assigned: ssu0262)
Details
(Whiteboard: [nsbeta2-])
Windows 2000 has more restrictive default NTFS permissions than did Windows NT4.
The Mozilla M14 Installer is not updating the NTFS permissions so that normal
domain users can save changes to their Mozilla User Profile.
If administrators were to grant their users "Power User" level of access, this
would not be a problem. But most administrators I know will not do that. They
would rather use IE and have a more secure network.
There are probably not many Win2K users that will run the Beta of Mozilla.
Probably not enough to justify making this a beta1 bug, but it should be a beta2
bug (if there is a beta 2).
I tested this on a system installed with Windows 2K Professional, not on a
system upgraded from NT4. I don't know if the Win2K installer will reset the
permissions on a system it is upgrading. Therefore you may only be able to
duplicate this problem on non-upgrade instalations of Win2K.
Please modify the Win32 installer to properly set NTFS permissions in Win2K.
I'll see what I can do. Cc:ing selmer in case the profile manager is still
creating the users50 folder. Profile Manager would also need to set the correct
permissions.
Status: NEW → ASSIGNED
Target Milestone: M15
Comment 2•25 years ago
|
||
Yes, profile manager needs to worry about this too. Probably needs another
bug...
Putting on [nsbeta2-] radar. Definitely want to fix beta before final release.
But would not hold beta2 for this. Putting on nsbeta3 radar.
this looks like a duplicate of bug #6464 in which the profile manager should be
using the Os's default user area, not create it's own.
*** This bug has been marked as a duplicate of 6464 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•