public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doctor Bill <docbill@gmail.com>
To: Cygwin List <cygwin@cygwin.com>
Subject: Re: File permission problem
Date: Fri, 24 Sep 2004 13:20:00 -0000	[thread overview]
Message-ID: <23bcb87004092405365a8d802f@mail.gmail.com> (raw)
In-Reply-To: <6.1.0.6.0.20040923225120.03ee4aa8@pop.prospeed.net>

I think about a year ago there was a patch added to the cygwin core to
allow you to use 'umask' to change apparent permissions on a FAT32
partition.  The idea was you could then do something like:

umask 077; ssh foo.bar.com

I do not know if this code is still in the cygwin libraries, and if it
will solve your problem.

                             Bill



On Thu, 23 Sep 2004 22:52:21 -0400, Larry Hall
<lh-no-personal-replies-please@cygwin.com> wrote:
> At 09:59 PM 9/23/2004, you wrote:
> >Dear all,
> >
> >    I have try to generate a private key file so that I don't need
> >to enter password everytime I "ssh" to a remote machine. However, "ssh"
> >complaints me about the permission of key file. I don't know why "chmod"
> >always return 666 or 444 even I want to change the file to 600 or 400.
> >
> >    Does anymore have idea? Thanks.
> 
> 
> Does this describe your situation?
> 
> Why doesn't chmod work?
> <http://cygwin.com/faq/faq_toc.html#TOC41>
> 
> --
> Larry Hall                              http://www.rfk.com
> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> 838 Washington Street                   (508) 893-9889 - FAX
> Holliston, MA 01746                     
> 
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2004-09-24 12:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  2:53 jackylam
     [not found] ` <6334E09627481B4AA5C8DE1E69E19D3B013BA6EB@SSLEXCHANGE.solom onsystech.com>
2004-09-24  3:31   ` Larry Hall
2004-09-24 13:20     ` Doctor Bill [this message]
2004-09-24 13:37       ` Doctor Bill
2004-09-24  5:19 jackylam
2004-09-24  5:22 ` Peter Rehley
2004-09-24  7:21 jackylam
2004-09-24  9:31 ` Brian Dessent
2004-09-24  9:31   ` Corinna Vinschen
2004-09-24  9:47     ` Brian Dessent
2004-09-24 12:42       ` Corinna Vinschen
2004-09-24 14:51         ` Andrew DeFaria
2004-09-24 14:58           ` Christopher Faylor
2004-09-24 15:08             ` Andrew DeFaria
2004-09-24 15:19               ` Corinna Vinschen
2004-09-24 16:41                 ` Andrew DeFaria
2004-09-24 14:59           ` Doctor Bill
2004-09-24 15:09             ` Corinna Vinschen
2004-09-24  8:35 jackylam
2004-09-24 16:26 Hughes, Bill
2007-11-28  0:57 file " Win Tong
2007-11-28  1:07 ` Larry Hall (Cygwin)
2016-04-16  1:16 Barry Gold
2016-04-16 20:38 ` Marco Atzeri

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=23bcb87004092405365a8d802f@mail.gmail.com \
    --to=docbill@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).