777 = everybody can execute and alter everything. That is for sure not what you want. However, it would go as follows (escaping like bash):
Better do the following (everybody can read, only owner can alter or execute):
If some cgi needs to write to some location beneath htdocs change ownership of those files/directories to the user used by your webserver to run cgis (normally apache, httpd oder nobody).
Quote:
Originally Posted by thehaapyappy
sorry, I don't understand that - what does that mean and where do I put that?
Put that into command line - it will display help about chmod command. Use "man find" to find out what above does in detail.
Hi,
I am setting up an area on a unix server where multiple people will be editing web pages. Can anyone tell me how to set it up the directory and subdirectories so that when a user creates a new file, it defaults to permissions of 664 or 775?
I've tried using umask but from what I can... (1 Reply)
Hi,
I am a Unix Admin. I have to give the permissions to a user for creating new file in a directory in HP-Ux 11.11 system since he cannot able to create a new file in the directory.
Thanks in advance.
Mike (3 Replies)
Hi,
I'm in the process of writing a system (in Java) where a user can register to become a member of a website.
When they register, a collection of directories and files get created by the application.
For example if a user with the name 'fred' registered they would get the following
drwxr-xr-x... (0 Replies)
Hi all,
I have user called "Z". The home directory is /home/Z. I have another directory /home/Z/OP. Within /home/Z/OP, i have 2 directories
/home/Z/OP/OP1 and /home/Z/OP2.
I want to restrict access for Z to only access
/home/Z/OP and
/home/Z/OP1 and
/home/Z/OP2.
What kind of... (4 Replies)
I'm trying to setup a directory structure for my staff which enables them full access to files in the directories with their name, and have access to anything in the shared directory. The directory structure looks like this:
root@www10 # ls -l
total 56
drwxr-xr-x 7 internal internal 4096... (3 Replies)
What would be a practical way of making sure files I upload to/edit in a particular directory on a server always have the correct group permissions?
I'm forgetful, so I try to automate things like chgrp'ing the files when I'm done. I could write a script to be run by cron. Is that the only way,... (2 Replies)
Hi,
I have written a shell script which calls a java program which reads properties from a configuration file and writes to a log file for each session.However the customer wants that the user should not be able to open/edit the configuration file or the log files meaning they should not... (4 Replies)
I've got a number of people sending files to me in different directory structures, and users on many different groups who need access to these incoming paths.
My problem is that umask assumes a default of 666 for files. No execute bit, meaning that my users can't even see the incoming folders.... (2 Replies)
Trying to figure out the best method of security for oracle user accounts. In Solaris 10 they are set as regular users but have nologin set forcing the dev's to login as themselves and then su to the oracle users.
In Solaris11 we have the option of making it a role because RBAC is enabled but... (1 Reply)
I'm working in a linux server where wrappers are executed by multiple users of different groups. The log and output files are created with 554 permissions by default. This is stopping other users to run the wrappers unless the log and output files are deleted or given 777 permission. Setting SUID... (1 Reply)
Discussion started by: praveenpa
1 Replies
LEARN ABOUT OSF1
dh_fixperms
DH_FIXPERMS(1) Debhelper DH_FIXPERMS(1)NAME
dh_fixperms - fix permissions of files in package build directories
SYNOPSIS
dh_fixperms [debhelperoptions] [-Xitem]
DESCRIPTION
dh_fixperms is a debhelper program that is responsible for setting the permissions of files and directories in package build directories to
a sane state -- a state that complies with Debian policy.
dh_fixperms makes all files in usr/share/doc in the package build directory (excluding files in the examples/ directory) be mode 644. It
also changes the permissions of all man pages to mode 644. It removes group and other write permission from all files. It removes execute
permissions from any libraries, headers, Perl modules, or desktop files that have it set. It makes all files in the standard bin and sbin
directories, usr/games/ and etc/init.d executable (since v4). Finally, it removes the setuid and setgid bits from all files in the package.
When the Rules-Requires-Root field has the (effective) value of binary-targets, dh_fixperms will also reset the ownership of all paths to
"root:root".
OPTIONS -Xitem, --exclude item
Exclude files that contain item anywhere in their filename from having their permissions changed. You may use this option multiple
times to build up a list of things to exclude.
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_FIXPERMS(1)