similar to: [Bug 1584] New: umask setting in sshd

Hi, I am not on this list so please CC me. Using dovecot-1.2.x it seems we can not configure the location of ssl- parameters.dat.tmp, it is hard coded to be in PKG_STATEDIR: ./src/master/master-settings.c: #define SSL_PARAMETERS_PERM_PATH PKG_STATEDIR"/"SSL_PARAMETERS_FILENAME This can lead to problems when you're running multiple instances on one machine. Apart from that, it

Hi, We want dovecot to listen on a specific ip4 & ipv6 addresses like so: listen = 145.58.1.1, [2a02:458:1::1] But on startup it tells me: Fatal: service(managesieve-login) Can't resolve address [2a02:458:1::1]: Name or service not known Wether it is in the dns or not. If I however change the listen directive to: listen = f.qd.nl where f.qd.nl resolves to an ip4 and ipv6 address

Hi, I am not an this list, I hope it gets through: We just moved from dovecot-1.2.12 to dovecot-2.0.6. One of our users wants his mail directly in his homedir which worked fine so far but with 2.0.6: Nov 09 15:19:25 imap(foo.bar at example.com): Error: user foo.bar at example.com: Initialization failed: Initializing mail storage from mail_location setting failed: No home directory for system

Hello Dovecot users, In the last week two nasty bugs were found in the new Sieve implementation. Primarily, the include extension did not work when a compiled binary was loaded from disk. This is something that is still not tested by the test suite, giving this bug the opportunity to slip through. Also, the value matching implementation would sometimes cause a assertion failure. Other than

Hello Dovecot users, In the last week two nasty bugs were found in the new Sieve implementation. Primarily, the include extension did not work when a compiled binary was loaded from disk. This is something that is still not tested by the test suite, giving this bug the opportunity to slip through. Also, the value matching implementation would sometimes cause a assertion failure. Other than

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,

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)

http://bugzilla.mindrot.org/show_bug.cgi?id=1229 Summary: No way to set default umask for SFTP server Product: Portable OpenSSH Version: 4.3p2 Platform: Other OS/Version: Mac OS X Status: NEW Severity: enhancement Priority: P2 Component: sftp-server AssignedTo: bitbucket at mindrot.org

Will setting the umask that sshd inherits cause any security issues? It would be nice to be able to set this in a system-wide fashion, rather than in .login etc. I'm thinking of Debian, where the setting is per-shell because nobody seems to have thought of doing this. Cheers, Jeremy -- Jeremy Jackson Coplanar Networks (519)897-1516 http://www.coplanar.net

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

> 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

On 7/13/20 4:21 PM, Phoenix, Merka 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 httpd.service script for

Hello, I think i may have found a bug in the "max clients" option in rsyncd.conf [we use rsync-2.5.5; All platforms I tried (Irix-6.5.14 and various linux flavours) show the behaviour explained below] The manpage says: |max connections | The "max connections" option allows you to specify | the maximum number of simultaneous connections you | will allow to

On 7/15/20 2:39 AM, Gianluca Cecchi wrote: > On Wed, Jul 15, 2020 at 2:39 AM Emmett Culley via CentOS <centos at centos.org <mailto:centos at centos.org>> wrote: > > > Thanks for the info.? I hadn't seen that before nor many of the links.? I had seen the suggested systemd fix, but have never been able got them to work. And I've tried many combinations.? Still

> 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

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

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

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)