Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 55183 - dos2unix mangles file permissions
dos2unix mangles file permissions
Product: Red Hat Linux
Classification: Retired
Component: dos2unix (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
Aaron Brown
Depends On:
  Show dependency treegraph
Reported: 2001-10-26 14:46 EDT by Bob Farmer
Modified: 2007-04-18 12:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-19 20:35:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:195 low SHIPPED_LIVE dos2unix and unix2dos bug fix update 2005-05-19 00:00:00 EDT

  None (edit)
Description Bob Farmer 2001-10-26 14:46:41 EDT
Description of problem:
dos2unix, when running in "old file mode", always changes the permissions
on the file it runs on to 600. 

How reproducible:

Steps to Reproduce:
1. echo test >a.txt
2. chmod 666 a.txt
3. dos2unix a.txt
4. ls -al a.txt	

Actual Results:  a.txt now has permissions 600

Expected Results:  a.txt's permissions should remain the same.  I can think
of no legitimate reason why dos2unix should modify them.  The behavior
isn't documented either.
Comment 1 Mike A. Harris 2003-05-21 11:29:47 EDT

*** This bug has been marked as a duplicate of 91331 ***
Comment 2 Tim Powers 2005-05-19 20:35:30 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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