Bug 76673 – mailer saves attachments with mode 600, doesn't use umask

Bug 76673 - mailer saves attachments with mode 600, doesn't use umask

Summary:	mailer saves attachments with mode 600, doesn't use umask

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	evolution (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-10-24 16:36 EDT by Don Himelrick
Modified:	2008-05-01 11:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-10-24 16:36:22 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Don Himelrick 2002-10-24 16:36:16 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
All attachments are saved as mode 600 instead of using the default umask setting
of 002 and creating them as 660.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Save attachment and move it to public location.
2.
3.
	

Actual Results:  Other users cannot read the attachments.

Expected Results:  File should have group read permissions so others in the
group can read it.

Additional info:

Comment 1 Jeremy Katz 2002-10-25 11:32:57 EDT

This is an intentional design decision, and one shared by most MUAs.  It's much
better to be restrictive in what you save and require explicitly changing the
permissions than to have somebody inadvertently leave mail world readable on a
network filesystem.

Note You need to log in before you can comment on or make changes to this bug.