ID: 23306
Comment by: php at ronino dot de
Reported By: alberty at neptunelabs dot de
Status: No Feedback
Bug Type: DBM/DBA related
Operating System: i686-pc-linux-gnu
PHP Version: 4CVS-2003-04-22 (stable)
Assigned To: helly
New Comment:
I can confirm this bug and provide an example (Gentoo with PHP
5.2.6_rc4 here):
$oldUmask = umask(0117);
$dbm = dba_popen("/some/file.dbm", "c");
umask($oldUmask);
For some handlers (tested: gdbm, qdbm), the file permissions always
are 0640 or -rw-r----- no matter what umask is set.
Regards, Ronino
Previous Comments:
------------------------------------------------------------------------
[2003-04-28 11:46:36] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
------------------------------------------------------------------------
[2003-04-22 17:08:23] [EMAIL PROTECTED]
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php
If you can provide more information, feel free to add it
to this bug and change the status back to "Open".
Thank you for your interest in PHP.
Could you post a reproducing script that shows in what way fopen
considers umask and dba does not?
But maybe you try dba_open with gdbm handler which allows a filemask as
a forth parameter.
------------------------------------------------------------------------
[2003-04-22 08:23:22] alberty at neptunelabs dot de
Hi,
dba_open() ignores the umask settings if you create a new database.
I think dba_open should also respect the umask settings, as well as
fopen().
Regards,
Steve
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=23306&edit=1
