public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: setting security bits on UNIX
Date: Mon, 25 Apr 2005 20:50:56 -0600 (Mountain Daylight Time)	[thread overview]
Message-ID: <Pine.WNT.4.62.0504252044220.2500@merlin> (raw)
In-Reply-To: <000c01c549e7$7f317d70$c2a9e744@nedelko83f1172>

Ned,
Wehn calculating the number you should pass to chmod, the following information is useful. read
is worth 4, write is worth 2, and execute is worth 1. Adding these gives you a single octal
number which represents the permition. Three of these numbers are used to represent user,
group, and world permitions. Thus rwxr-xr-x would be 755.

The umask command represents the permitions to remove from newly created files. You start with
666 for files and 777 for directories. Most systems use a umask of 022, which results in 644
for files and 755 for directories.

Equal causes can produce very unequal effects.
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7

And so it came to pass that on Mon, 25 Apr 2005, Ned said

> Hi all,
>
> I don't know how to take off protection from one of my files
> Tried umask 022, umask 0, etc, nothing works. The chmod command didn't work either. I don't
know the values that I need to put in.
> The ls -l fileName command should give me:
> -rwxr-xr-x
> but not all dashes as it does now.
> It's an html file that needs to be read and executed by anybody.
> Please help.
>
> Many thanks in advance!
> Ned
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  parent reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Ned
 ` Gregory Nowak
   ` Steve Holmes
   ` Sean McMahon
 ` Joseph C. Lininger [this message]
 ` Ralph W. Reid

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=Pine.WNT.4.62.0504252044220.2500@merlin \
    --to=jbahm@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).