similar to: umask setting

If a user doesn't have a ~/mail directory and logs in, the directory is created for them. However, it is created with insecure permissions, 0770 (full group access). The problem is this bit in src/lib-storage/index/mbox/mbox-storage.c: #define CREATE_MODE 0770 /* umask() should limit it more */ The code then uses CREATE_MODE as an argument to mkdir_parents(), but mkdir_parents()

Hi, after deciding to use Dovecot 2.0.8 as a postfix LDA using mysql DB I'm running into some issues. I started to follow, http://wiki.dovecot.org/HowTo/DovecotLDAPostfixAdminMySQL but noticed that the auth settings on the config changed, after looking through the dovecot wiki I think I have that issue fixed. However I still can't get the SQL part to work right, below is what I have on the

Hey all, We have the following set in /etc/profile : umask 0002 so that it will affect all users. That should create all files as 664 and all directories as 775 if I'm not mistaken. Well I logged into the machine after this was set and just created a file as one of the users who complained about permissions settings on files. And this is what I saw: [user1 at qa_host ~]$ ls -l test_qa

I'm running OpenSSH 5.1p1 on openSUSE 10.3 (i586) and I want to setup chroot jails for certain SFTP-only users. I use the following lines in my sshd_config file: Match Group sftponly ChrootDirectory /home/chroot-%u ForceCommand internal-sftp It works great. The problem is that some of my users need umask 002 for their uploads. I tried a few ways to achieve this: * set umask in sshrc,

https://bugzilla.mindrot.org/show_bug.cgi?id=1584 Summary: umask setting in sshd Product: Portable OpenSSH Version: 5.2p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: leo.baltus at omroep.nl

Using dovecot 1.0rc15, together with postfix and dovecot-lda. umask is set to 0007. This should ensure directories and files get created with read/write permissions for both user and group. However, dovecot-lda writes files with 600 permissions, instead of 660. So dovecot does not seem to respect the umask configuration property for local mail delivery. In my particular case, I have

I recently posted about problems I've been having with dovecot-shared and umask in RC15 (using Solaris 9). I've now been able to distill what I'm experiencing into these two separate points: 1. dovecot-uidlist and message files never inherit the dovecot-shared group 2. With umask=0007 these files are created with mode 600 instead of 660: dovecot-uidlist, dovecot.index,

We currently set sb->s_flags |= MS_POSIXACL unconditionally, which is incorrect -- it tells the VFS that it shouldn''t set umask because we will, yet we don''t set it ourselves if we aren''t using POSIX ACLs, so the umask ends up ignored. Signed-off-by: Chris Ball <cjb@laptop.org> --- fs/btrfs/super.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)

Since Linux 4.7, the process umask is available in /proc/<pid>/status. See: https://github.com/torvalds/linux/commit/3e42979e65dace1f9268dd5440e5ab096b8dee59 Use this value if available, else fall back to the existing codepath for Linux <= 4.6 and other Unix. --- src/umask.c | 86 +++++++++++++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 78 insertions(+), 8

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm very happy with Dovecot and wish the best for its continued development. It's a true testament to brilliant componentised design and Unix philosophy. Configuration made easy because of the way the file is parsed and a single point of startup make it ridiculously straightforward (and lovely) to administer. But of course, we all

> On 7/13/20 6:40 PM, Emmett Culley via CentOS wrote: >> I need to set the umask for apache to 002.? I've tried every idea I've >> found on the internet, but nothing make a difference.? Most suggest that >> I put "umask 002" in /etc/sysconfig/httpd, but that doesn't seem to make >> a difference.? Other's suggest adding something to the

I need to set the umask for apache to 002. I've tried every idea I've found on the internet, but nothing make a difference. Most suggest that I put "umask 002" in /etc/sysconfig/httpd, but that doesn't seem to make a difference. Other's suggest adding something to the httpd.service script for systemd. And that doesn't make any difference. Any suggestion from

> On 7/19/20 10:41 PM, Simon Matter via CentOS wrote: >>> On 7/13/20 6:40 PM, Emmett Culley via CentOS wrote: >>>> I need to set the umask for apache to 002.? I've tried every idea I've >>>> found on the internet, but nothing make a difference.? Most suggest >>>> that >>>> I put "umask 002" in /etc/sysconfig/httpd, but

So any files that are uploaded through my form are getting the following mode: -rw------- I need them to have: -rw-r--r-- I''ve tried setting the umask in a script file called set_umask.rb as follows: File.umask(022) and then starting mongrel using: mongrel_rails start -m config/mime.types -S set_umask.rb but it doesn''t seem to change the mode that the files are created

Hi all, Currently, umask takes effect when we create device file via mknod, as bellow commands show: ><fs> mknod-b 0760 8 1 /dev/sdf ><fs> ll /dev/sdf brwxr----- 1 root root 8, 1 Apr 15 11:10 /sysroot/dev/sdf But I wonder whether it is reasonable? For mknod(1), when we use option -m mode, we set file permission bits to MODE, not a=rw - umask. Should this also be applicable

I have another small feature suggestion, it should not cause such a stir as the whole "file list" issue (I kind of wish I never said anything about it :) ). What about adding a "UMASK" setting to rsync (for use on the command line and/or perhaps rsyncd.conf)? I realize that it may be a problem/conflict with -p, but I think it could be a useful feature. -- Aaron W Morris

I have a situation where if a user is over quota and sending through postfix I get an error, now this error only happens if the user is over quota, otherwise it works with no problem. However if sending using /usr/local/libexec/dovecot/dovecot-lda it works every time even if overquota, any ideas? I just can't seem to figure this one out. TIA, Paul Using mail command Dec 21

Hello, I have noticed that the -u parameter to the sftp-server or internal-sftp subsystem is not working correctly. For openssh-5.6p1 I believe that the problem lies in this code, starting at line 1414 in sftp-server.c: ---------------------------------------------------------- case 'u': mask = (mode_t)strtonum(optarg, 0, 0777, &errmsg); if (errmsg != NULL)

After upgrading to 8.1.1911, bcc-tools and bpftrace seem to be broken. Current package versions I have: bpftrace-0.9-3.el8.x86_64 and bcc-tools-0.8.0-4.el8.x86_64 Both of these seem to be pulling in LLVM version 7, rather than the version 8 that is in 8.1.1911: [root at localhost ~]# bpftrace bpftrace: error while loading shared libraries: libclangFrontend.so.7: cannot open shared object file:

Two servers, each have normal user umask values of 0077 and root umask values on 0022. On the first server (CentOS 5.4 i386) running sudo 1.6.9pl7-5 (from base), here are the results of touching a file as a user, as root and as a user sudoing to root: user: touch file - result is 600 root: touch file - result is 644 user: sudo touch file - result is 644 On the second server (CentOS x86-64)