[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #17, sr #104708 (project administration): Sorry for not bean clear :) I mean: since this is a shared directory, with each member having an account instead of using a shared account, other project members can be stuck with bad permissions. sftp tries to respect the permissions of

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #16, sr #104708 (project administration): It appears to be working for me. What were we doing wrong with the permissions? o+w or something? I really didn't do anything to the permissions... I just let the system use its defaults... Thanks, _

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #15, sr #104708 (project administration): I'm working on the download setup. Please use sftp -o port=10022 [EMAIL PROTECTED]:/var/lib/download/cvs You need to be more careful with permissions, btw. Feedback would be appreciated :) _

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #14, sr #104708 (project administration): Okay, great! We'll try not to lock it. :) Thanks again, ___ Reply to this item at: ___

[Savannah-help-public] [sr #104708] Binary download directory.

Update of sr #104708 (project administration): Status: Need Info => Done Open/Closed:Open => Closed ___ Follow-up Comment #13: It will be

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #12, sr #104708 (project administration): One final thought, if you want to take away our direct access to our own authorized_keys file, and it isn't too hard, maintaining it with the same ssh keys that are authorized for CVS access to the cvs project via savannah would work. T

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #11, sr #104708 (project administration): Thanks Sylvain! It looks like it is working, so you can close this. Thanks again! ___ Reply to this item at:

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #10, sr #104708 (project administration): Derek, try: sftp -o port=10022 [EMAIL PROTECTED] Then update ~/.ssh/authorized_keys to suit your needs, and manager ~/cvs/ which points to the download area. Tell me if there's something, or if you think there is a security risk in m

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #9, sr #104708 (project administration): Okay, that sounds simple enough. I assume the sftp account could be equipped to handle multiple uploaders? We currently have 4 people who would like access re CVS task #4844. ___

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #8, sr #104708 (project administration): I would like to get Justin's reply first. The solution I would setup - until Savannah gets the needed upload management and if ftp.gnu.org/non-gnu cannot get directives activated - would be a sftp account, I think.

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #7, sr #104708 (project administration): So, something like the procedure outlined in http://www.gnu.org/prep/maintain/html_node/Automated-Upload-Procedure.html, but upload to ftp://savannah.gnu.org/incoming/savannah/cvs/with-directives or the like? This would work for us.

[Savannah-help-public] [sr #104708] Binary download directory.

Update of sr #104708 (project administration): Status: Wont Do => Need Info Open/Closed: Closed => Open ___ Follow-up Comment #6: I didn't kn

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #5, sr #104708 (project administration): This issue may need to be reopened. Re CVS task #4844, Justin Baugh wrote me back for [EMAIL PROTECTED] saying that the instructions you referred me to were for admininstrating subdirectories of the "gnu" directory of ftp.gnu.org only an

[Savannah-help-public] [sr #104708] Binary download directory.

Update of sr #104708 (project administration): Status:None => Wont Do Open/Closed:Open => Closed ___ Follow-up Comment #4: Ok, thanks.

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #3, sr #104708 (project administration): Hi, You can close this if you like. I am going to request direct access to ftp.gnu.org for several project members, using the [EMAIL PROTECTED] email. Thanks, ___ Reply to this

[Savannah-help-public] [sr #104708] Binary download directory.

Follow-up Comment #2, sr #104708 (project administration): Hrm. ftp.gnu.org/non-gnu/cvs is already a mirror of Savannah in this case. I'm not sure how the current mirroring setup would interoperate with also using the ftp.gnu.org interface. The easiest thing from my end would be if you let me

[Savannah-help-public] [sr #104708] Binary download directory.

Update of sr #104708 (project administration): Assigned to:None => Beuc ___ Follow-up Comment #1: Hi, I remember that CVS has a download area at ftp.gnu.org; ftp.gnu.org accepts a direc

[Savannah-help-public] [sr #104708] Binary download directory.

URL: Summary: Binary download directory. Project: Savannah Administration Submitted by: dprice Submitted on: Wed 10/05/05 at 17:31 Category: Project downlo