From: Stephen Samuel <samuel@bcgreen.com>
To: linux-newbie <linux-newbie@vger.kernel.org>
Cc: eatley@wowcorp.com
Subject: Re: 2 questions: 1. ssh permissions to 777 and 2. recursively change all directories/files to 777
Date: Mon, 13 Dec 2004 13:54:24 -0800 [thread overview]
Message-ID: <41BE0F90.9030905@bcgreen.com> (raw)
In-Reply-To: <00ac01c4de33$b3b63e20$1f0aa8c0@lanadmin>
Eve Atley wrote:
> First question...
> We have people SSHing into our Linux box from overseas (India to US, company
> access only). But files that are uploaded from these people become read-only
> to anyone else accessing them. We *require* that they be readable/writable
> by this side of the pond (US). How can I set this to occur? Otherwise, this
> method of transferring files will *not* work for us, and perhaps someone can
> point me to another solution.
>
> Second question...
> How can I recursively set all files/directories to 777?
> Chmod -R 777 *.* ... Didn't seem to hit everything.
The problem is that permissions are preserved when using scp.
(i.e. if the file is mode 700 on the source box, it will be
mode 700 on the destination, independant of umask settings).
Your *.* wildcard is a holdover from your DOS days. Not all UNIX
files have a dot in them, but the dot will have to be explicitly
matched since it was explicitly requested.
Chown -R 777 * will catch everything other than files/directories
with a leading dot.
chmod -R 777 . will get EVERYTHING (including resetting the
permissions of the current directory).
You can also use the find command to find files that aren't
readable by others, and only change the permissions on them
(I'll leave that as an exercise for the reader).
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication. Transformation touching
the jewel within each person and bringing it to light.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-12-13 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 17:29 Remote X Little, Chris
2004-04-14 12:01 ` Juan Facundo Suárez
2004-10-13 18:43 ` Setting permissions via SSH upload to 777 Eve Atley
2004-10-13 19:23 ` Ray Olszewski
2004-12-09 21:11 ` 2 questions: 1. ssh permissions to 777 and 2. recursively change all directories/files " Eve Atley
2004-12-09 21:12 ` Jeff Woods
2004-12-09 21:57 ` Ray Olszewski
2004-12-09 22:35 ` Simon Valiquette
2004-12-10 10:37 ` Jim Nelson
2004-12-10 13:53 ` J.
2004-12-10 21:05 ` Jim Nelson
2004-12-10 13:48 ` J.
2004-12-13 21:54 ` Stephen Samuel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41BE0F90.9030905@bcgreen.com \
--to=samuel@bcgreen.com \
--cc=eatley@wowcorp.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox