From forrest-dev-return-2257-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org Fri Aug 16 10:01:40 2002 Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 42453 invoked by uid 500); 16 Aug 2002 10:01:37 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 42443 invoked from network); 16 Aug 2002 10:01:36 -0000 Received: from www2.kc.aoindustries.com (209.15.201.84) by daedalus.apache.org with SMTP; 16 Aug 2002 10:01:36 -0000 Received: from ROSINANTE (stat88-15.adsl.xs4all.be [195.144.88.15]) by www2.kc.aoindustries.com (8.11.6/8.11.0) with SMTP id g7GA1ni11879 for ; Fri, 16 Aug 2002 05:01:49 -0500 From: "Marc Portier" To: Subject: RE: cvs commit: xml-forrest/src/documentation/content/xdocs/community/howto/cvs-ssh howto-cvs-ssh.xml Date: Fri, 16 Aug 2002 12:01:49 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: > > > > Added the line (%chmod 700 ~/.ssh) in > > > described ssh setup > > > > on remote host. > > > > Tests proved the drwx------ setting to be an > > > absolute must > > > > to get things working. > > > > > > Can't remember that I've ever used this command > > > during setup of SSH. > > > > > > > maybe your umask covered it? > > tests showed the need for the drwx------ and > this makes it > > independent of how the umask is set I guess. > > > > mmmm, I have to give in: there is more to it... > > on cvs.apache server it works regardless of the > settings on > > the .ssh :-( > > Yes, I've tried it on cvs.apache.org only. > Obviously I didn't do the full range test on all servers around. I did some more now, also on cvs.apache.org and it looks like 700 is a bit to picky, a simple: chmod go-w .ssh should do the job (I just tried the chmod go+w .ssh on cvs.apache and after that it prompts for the pwd again... DON'T TRY THIS AT HOME UNLESS YOU STILL REMEMBER THAT PASSWORD YOU NEVER USE :-) so it is less version/platform dependent than my previous message implied, I guess) letting it at the even more restrictive 700 doesn't look like bad practice (although 755, 744, 745 and 754 would work as well) regards, -marc= > > > > sorry for stepping in so bluntly, > > mmm, the change makes it work on more > environments, but he > > wording could be made intellectually more correct maybe? > > I'm doing some more tests first now... > > No problems. > If your setting covers mine too and works in more > environments then let's > leave it as you've changed. I suspect that it > depends on the SSH version > used on the server. > > Konstantin >