All of lore.kernel.org
 help / color / mirror / Atom feed
From: fork0@t-online.de (Alex Riesen)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Salikh Zakirov <Salikh.Zakirov@Intel.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-receive-pack needs to set umask(2)
Date: Mon, 29 May 2006 23:28:30 +0200	[thread overview]
Message-ID: <20060529212830.GA4074@limbo.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0605290956190.5623@g5.osdl.org>

Linus Torvalds, Mon, May 29, 2006 19:00:42 +0200:
> 
> I realize that you already found the solution (Core.SharedRepository), 
> but:
> 
> On Mon, 29 May 2006, Salikh Zakirov wrote:
> > 
> > 2) I have 'umask 002' in my ~/.profile. Somehow, it does not help,
> > because ~/.profile is not read on non-interactive SSH sessions
> > (to verify that, just try to do 'ssh somehost umask')
> 
> The ".profile" thing is indeed read only for interactive tasks.
> 
> So use ".bashrc" instead.
> 

Will not work:

$ man bash
...
       When  an  interactive  shell  that is not a login shell is
       started, bash reads and executes commands from  ~/.bashrc,
       if  that  file exists. ...

Besides, not everyone has bash as their login shell.

Reading man sshd:

     $HOME/.ssh/rc
             If this file exists, it is run with /bin/sh after reading the
             environment files but before starting the user's shell or com­
             mand.  It must not produce any output on stdout; stderr must be
             used instead.  If X11 forwarding is in use, it will receive the
             "proto cookie" pair in its standard input (and DISPLAY in its
             environment).  The script must call xauth(1) because sshd will
             not run xauth automatically to add X11 cookies.
and

     /etc/ssh/sshrc
             Like $HOME/.ssh/rc.  This can be used to specify machine-specific
             login-time initializations globally.  This file should be
             writable only by root, and should be world-readable.


This guaranteed to work (at least for ssh).

  reply	other threads:[~2006-05-29 21:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28 21:31 [PATCH] git-receive-pack needs to set umask(2) Michael Richardson
2006-05-28 22:00 ` Jakub Narebski
2006-05-29  7:13   ` Johannes Schindelin
2006-05-29 11:28     ` Salikh Zakirov
2006-05-29 11:33       ` Shawn Pearce
2006-05-29 17:00       ` Linus Torvalds
2006-05-29 21:28         ` Alex Riesen [this message]
2006-05-29 21:50           ` Johannes Schindelin
2006-05-28 22:06 ` Petr Baudis
2006-05-29 16:03   ` Michael Richardson
  -- strict thread matches above, loose matches on Subject: below --
2006-05-29 12:07 Zakirov, Salikh

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=20060529212830.GA4074@limbo.home \
    --to=fork0@t-online.de \
    --cc=Salikh.Zakirov@Intel.com \
    --cc=fork0@users.sourceforge.net \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.