Closed Bug 124814 Opened 23 years ago Closed 23 years ago

SaveAs saves with permissions 600

Categories

(Core Graveyard :: File Handling, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 124307

People

(Reporter: BenB, Assigned: law)

Details

I see that now (since sometime between Jan 31 and now) SaveAs also saves the
file with 600. Is this due to bug 109088?

Reproduction:
1. On a link, do contextmenu|SaveAs...
2. cd to the download dir
3. ls -l

Actual result:
The downloaded file has permissions:
-rw-------    1 auser    auser      141312 11. Feb 10:17 yourfile

Expected result:
Group can read/write.
Ideally, user-configureable.

Importance:
This prevents me from accessing the file from another account that has
permissions for this group. (I run the browser from a user separate as the rest
of my environment.) In other words, I can download, but I can't do anything with
the file until I manually change permissions.
Shouldn't it be 660 instead of 600?

Ideally, this should be user-configureable. There are different security setups
and needs and some need conflicting permissions.
Bug 107088, not 109088. Sorry.
Shouldn't this depend on the current umask value rather than a preference in
Mozilla?
Duplicate of "Awful permissions for file saving as of recently"

*** This bug has been marked as a duplicate of 124307 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
not a dupe of bug 124307.  this is really a regression resulting from the patch
for bug 124307.  the reporter wants created files to honor his umask setting. 
this seems reasonable if mozilla is creating the file in a location specified by
the user.  ie, it's not reasonable for files created in a temporary directory.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Darin, the bug I duped to _is_ the bug about this issue...

The problem is we create the file in a temp dir and then move it.  Moving
preserves permissions.  :(

*** This bug has been marked as a duplicate of 124307 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.