From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Molenda To: Chris Faylor Cc: overseers@sourceware.cygnus.com Subject: Re: YA change to .ssh/authorized_keys Date: Sat, 30 Dec 2000 06:08:00 -0000 Message-id: <20000508150807.A20941@shell17.ba.best.com> References: <20000508180038.A2284@cygnus.com> X-SW-Source: 2000/msg00482.html 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Molenda To: Chris Faylor Cc: overseers@sourceware.cygnus.com Subject: Re: YA change to .ssh/authorized_keys Date: Mon, 08 May 2000 15:09:00 -0000 Message-ID: <20000508150807.A20941@shell17.ba.best.com> References: <20000508180038.A2284@cygnus.com> X-SW-Source: 2000-q2/msg00175.html Message-ID: <20000508150900.qBJt5RtCPF3a_uTsib-kEVe42IacvbcWhGVwMjukiF8@z> 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