Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 990048 [details]
patch

Description of problem:
Currently when setting up a shared sftp upload space between multiple users/logins, you can force a proper umask with the -u switch. This requires
that the file at the origin has wide-permissions to start with. In some
cases, users are not skilled enough to set the permissions to be correct (sigh).
While this could be solved via file/dir ACLs, it is also not entirely trivial
in most environments.

A simple solution would be to add a force_file_perm option to sftp
which could be used for this.

I shall attach a patch that was taken from https://bugzilla.mindrot.org/show_bug.cgi?id=1844 and massaged it for RHEL 6.7

I smoke-tested it and it works as expected. I.e. setting the following:
Match User testrpm
       ForceCommand internal-sftp -m 777

Gives all files created via sftp by user testrpm of 777

I chose the simplest one to cover this specific use case, but anything that
covers this, will do (i.e. we could expand it to cover folders as well, if
it makes sense)

I think what has been NACKed a long time ago via BZ 859238 was much bigger
in scope, hence this BZ

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1335.html