public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason-swarelist@molenda.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: YA change to .ssh/authorized_keys
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <20000508150807.A20941@shell17.ba.best.com> (raw)
In-Reply-To: <20000508180038.A2284@cygnus.com>

On Mon, May 08, 2000 at 06:00:38PM -0400, Chris Faylor wrote:
> It looks like I have another user who needs to upload things to the cygwin
> directory.  This means that his .ssh/authorized_keys file needs to be modified
> to allow more than just cvs access.


Incidentally, this is Yet Another Problem I Didn't Tackle.

Until recently, we'd only had two or three external developers who
needed access only to upload files.  eCos has one and bartv thought
I was a loser for giving the ext person full login access just to
upload files. :-)

I don't know how this should be handled.  anon-ftp-upload is one
possibility (or plaintext passworded ftp upload) with a crontab
that would move the uploaded files to another part of the ftp tree.
The problems with this kind of automated facility are obvious.  I
don't know of any way to allow only scp access, and really you'd
want to allow only scp to one part of the file hierarchy.

Maybe folks on the net have come up with good solutions, or have
settled on methods that involve by-hand intervention of maintainers.
I just punted and gave them full login access.

Jason

WARNING: multiple messages have this Message-ID
From: Jason Molenda <jason-swarelist@molenda.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: YA change to .ssh/authorized_keys
Date: Mon, 08 May 2000 15:09:00 -0000	[thread overview]
Message-ID: <20000508150807.A20941@shell17.ba.best.com> (raw)
Message-ID: <20000508150900.qBJt5RtCPF3a_uTsib-kEVe42IacvbcWhGVwMjukiF8@z> (raw)
In-Reply-To: <20000508180038.A2284@cygnus.com>

On Mon, May 08, 2000 at 06:00:38PM -0400, Chris Faylor wrote:
> It looks like I have another user who needs to upload things to the cygwin
> directory.  This means that his .ssh/authorized_keys file needs to be modified
> to allow more than just cvs access.


Incidentally, this is Yet Another Problem I Didn't Tackle.

Until recently, we'd only had two or three external developers who
needed access only to upload files.  eCos has one and bartv thought
I was a loser for giving the ext person full login access just to
upload files. :-)

I don't know how this should be handled.  anon-ftp-upload is one
possibility (or plaintext passworded ftp upload) with a crontab
that would move the uploaded files to another part of the ftp tree.
The problems with this kind of automated facility are obvious.  I
don't know of any way to allow only scp access, and really you'd
want to allow only scp to one part of the file hierarchy.

Maybe folks on the net have come up with good solutions, or have
settled on methods that involve by-hand intervention of maintainers.
I just punted and gave them full login access.

Jason

  parent reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Chris Faylor
2000-05-08 15:00 ` Chris Faylor
2000-12-30  6:08 ` Jason Molenda [this message]
2000-05-08 15:09   ` Jason Molenda
2000-12-30  6:08   ` Chris Faylor
2000-05-08 15:19     ` Chris Faylor
2000-12-30  6:08 ` Tom Tromey
2000-05-08 15:16   ` Tom Tromey

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=20000508150807.A20941@shell17.ba.best.com \
    --to=jason-swarelist@molenda.com \
    --cc=cgf@cygnus.com \
    --cc=overseers@sourceware.cygnus.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).