similar to: how to make umask changes permanent

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,

On 7/21/20 9:59 AM, Simon Matter wrote: >> 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

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 that doesn't seem to make

> 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

We have a problem whereby Nautilus is not using the umask setting defined by the user (e.g. when creating directories via the the 'Places' menu). The umask used by Nautilus is 022, but the shell umask (in our case) is set to 002 A quick search seems to suggest that this a common problem, and various methods are suggested to 'fix' this - the only way that appears to work on

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 httpd.service script for systemd.? And that

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

> 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

Normal users umask is 022 set in /etc/bashrc Obviously I can change that value to 002 but that would affect all files created by each user. Is it possible to set a different umask on nfs mounts only so that user created files have a umask of 002 on files saved onto that mount? man mount shows this is possible on some filesystems but man nfs doesn't suggest that this is possible. Craig

Am 15.07.20 um 20:02 schrieb Emmett Culley via CentOS: > 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

Hi, The R-admin manual says: "If installing packages on a Unix-alike to be used by other users, ensure that the system umask is set to give sufficient permissions (see also Sys.umask in R). (To a large extent this is unnecessary in recent versions of R, which install packages as if umask = 022.)" I want install.packages() to honor my umask which is 002. I can't find a way to do

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

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

Thank you for answering. I am testing Samba 3.0.1Pre1 on RH9 . MS Word 97 keeps opening already opened files without sending any warning as it would normally do when accessing W2K servers. Same program , same files behave differently with Samba and W2K. However, I found that Powerpoint is nevertheless able to sense correctly the situation by always giving such warnings - " test.ppt is

Hello, I've been trying to setup a site library that allows the users to manage the R packages themselves, but am having an issue with permissions. As seen below, when installing a package using install.packages, the umask used is always 022. Instead, I would like it to be 002, allowing any user to update packages that were installed by another user. Can someone explain how to get

Hey folks-- When ssh creates a known_hosts file for a user, it disregards the currently-set umask, and can actually turn on mode bits that the user has explicitly masked. While i'm happy to have ssh make files *more* secure than my umask (in situations where that's reasonable, like the creation of new ssh keys, etc), i'm not sure that i see the point in ssh making the files more open

Hi, Does anyone know how to set umask such that nautilus actually obeys it? I have umask 002 added to the end of .bashrc, and if I touch a file from a gnome terminal, I correctly get -rw-rw-r--. However if I right click in a nautilus window and "create document" then "empty file" I end up with -rw------ which is obviously going to be a royal pita for group working! --

Normally, in the !UseLogin case on a system with login classes, the umask is set implicitly by the first setusercontext() call in do_setusercontext() in session.c. However, FreeBSD treats the umask differently from other login settings: unless running with the target user's UID, it will only apply the value from /etc/login.conf, not that from the user's ~/.login.conf. The patch below

I have the same problem as Daniel Westphal, packages are always installed with umask 022, I'd like 002. Any solution so far? Thank you. Francois [[alternative HTML version deleted]]