[Mono-bugs] [Bug 42706][Wis] Changed - File Creation Perms debate: what should be a good default?

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 20 Jan 2004 16:02:17 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by miguel@ximian.com.


--- shadow/42706	2003-05-10 05:54:21.000000000 -0400
+++ shadow/42706.tmp.24811	2004-01-20 16:02:17.000000000 -0500
@@ -1,22 +1,22 @@
 Bug#: 42706
 Product: Mono/Class Libraries
 Version: unspecified
-OS: Red Hat 8.0
+OS: Red Hat 9.0
 OS Details: 
-Status: RESOLVED   
-Resolution: FIXED
+Status: REOPENED   
 Severity: Unknown
 Priority: Wishlist
 Component: System
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: giuseppe.greco@agamura.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
-Summary: File.Copy( ) and File Permissions
+Summary: File Creation Perms debate: what should be a good default?
 To reproduce the problem, just write a small
 C# program like this:
 using System;
 using System.IO;
@@ -62,6 +62,17 @@
 I've committed a fix based on this patch to CVS.
 ------- Additional Comments From gonzalo@ximian.com  2003-05-10 05:54 -------
 I put the g_asserts because, as the handlers are just opened, they
 must be found by _wapi_lookup_handler.
+------- Additional Comments From giuseppe.greco@agamura.com  2003-09-25 01:31 -------
+The problem is still there. When creating new files,
+they always have permission 600 instead of 664.
+------- Additional Comments From miguel@ximian.com  2004-01-20 16:02 -------
+The question is whether this is a good default or not.
+Given .NET lack of permission's support on the API, I feel this is a
+good default.   POSIX-y?  Maybe not.