Closed
Bug 30853
Opened 26 years ago
Closed 26 years ago
file protections are wrong
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
CLOSED
FIXED
People
(Reporter: colin, Assigned: colin)
Details
When Mozilla creates a file (such as a prefs file or an HTML file from the
editor), the protection on the new file is not what is expected. For a new file
the protection should be the user's default, and for a new version of an
existing file the protection should be inherited from the previous version. In
M14 all files seem to be creatd with S:RWED,O:RWED,G,W protection.
|
Assignee | |
Comment 1•26 years ago
|
||
Mozilla creates new files with 0700 protection, hence the behaviour we see in
M14. I have changed the VMS library to use the user's default, so in M15 and
onwards Mozilla should "do the right thing" on OpenVMS.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•26 years ago
|
Status: RESOLVED → CLOSED
|
|
Assignee | |
Comment 2•26 years ago
|
||
This is an OpenVMS-specific bug, and so QA can't verify its fixed. So I'm
closing, and you'll just have to trust me :-)
|
||
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•