Re: [Sandweb-users] Can't create local SSH sandbox session

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi William,

Here is the command:
DEBUG: (SandWeb::Shell) Full command is :
/opt/sfw/bin/sandweb-expect vcs
/opt/sfw/share/sandweb/users/puddle/passwd "cd
'/opt/sfw/share/sandweb/users/puddle/flash//' &&
MESSAGE_FILE="/opt/sfw/share/sandweb/users/puddle/commitmsg"
&& export MESSAGE_FILE &&
CVSEDITOR=/opt/sfw/bin/sandweb-editor && export
CVSEDITOR && SSH_BIN=/opt/csw/bin/ssh && export
SSH_BIN && CVS_RSH=/opt/sfw/bin/sandweb-ssh && export
CVS_RSH && /opt/sfw/bin/cvs -q -d
":ext:puddle@192.168.0.100:/export/home/cvsroot/flash/"
update -P -d 'flash'"

Yes, it's insanely long :) It might be more sane for us to hide this in 
a shell script.. in fact that'd make debugging easier (we could start it 
with #!/bin/sh -x so the output gets into sandweb's debug mode).

Anyway, try pasting everything after "Full command is:" into your web 
user's shell. Make sure it's all on one line, or split it into seperate 
lines in a shell script (can split on &&, && means to run the next 
command only if the previous succeeded).

Driving SSH using expect turned out to be very complex, unfortunately..
I'd like a future version of sandweb to just use the SSH wire protocol 
(I think there are perl modules for this now..). Would be cool to just 
upload your SSH key into sandweb, and not need to configure this shell 
nonsense.

--
Rob

William Pool (Puddle) wrote:
> Yes, Sun's SSH version is based off of OpenSSH.
> 
> Now, I enabled debugging, but when trying to connect
> to the sandbox repository using SSH.  The window comes
> up, but it's white with no-output.  
> 
> When I kill the webserver uid sshd sessions then I get
> error output.  
> 
> Doesn't provide any ssh commands though.
> 
> DEBUG: (main) Repo name: flash
> DEBUG: (main) Repo root: /export/home/cvsroot/flash/
> DEBUG: (main) VCS sandbox:
> /opt/sfw/share/sandweb/users/puddle/flash//
> DEBUG: (main) Repo type: CVS
> DEBUG: (main) Filename(s): flash
> DEBUG: (SandWeb::Repository) Performing update
> operation
> DEBUG: (SandWeb::Repository) Params: prune 1 clobber 0
> directories 1 file flash
> DEBUG: (SandWeb::Repository::cvs) Performing update
> operation
> DEBUG: (SandWeb::Repository::cvs) Params: update -P -d
> DEBUG: (SandWeb::Repository::cvs) File: flash
> DEBUG: (SandWeb::Repository::cvs) Creating Shell
> object
> DEBUG: (SandWeb::Shell) VCS call to Unix shell
> DEBUG: (SandWeb::Shell) VCS command is : cd
> '/opt/sfw/share/sandweb/users/puddle/flash//' &&
> MESSAGE_FILE="/opt/sfw/share/sandweb/users/puddle/commitmsg"
> && export MESSAGE_FILE &&
> CVSEDITOR=/opt/sfw/bin/sandweb-editor && export
> CVSEDITOR && SSH_BIN=/opt/csw/bin/ssh && export
> SSH_BIN && CVS_RSH=/opt/sfw/bin/sandweb-ssh && export
> CVS_RSH && /opt/sfw/bin/cvs -q -d
> ":ext:puddle@192.168.0.100:/export/home/cvsroot/flash/"
> update -P -d 'flash'
> DEBUG: (SandWeb::Shell) Using VCS username/password
> DEBUG: (SandWeb::Shell) Full command is :
> /opt/sfw/bin/sandweb-expect vcs
> /opt/sfw/share/sandweb/users/puddle/passwd "cd
> '/opt/sfw/share/sandweb/users/puddle/flash//' &&
> MESSAGE_FILE="/opt/sfw/share/sandweb/users/puddle/commitmsg"
> && export MESSAGE_FILE &&
> CVSEDITOR=/opt/sfw/bin/sandweb-editor && export
> CVSEDITOR && SSH_BIN=/opt/csw/bin/ssh && export
> SSH_BIN && CVS_RSH=/opt/sfw/bin/sandweb-ssh && export
> CVS_RSH && /opt/sfw/bin/cvs -q -d
> ":ext:puddle@192.168.0.100:/export/home/cvsroot/flash/"
> update -P -d 'flash'"
> DEBUG: (SandWeb::Shell) VCS call to Unix shell
> DEBUG: (SandWeb::Shell) VCS command is : rm
> "/opt/sfw/share/sandweb/users/puddle/passwd"
> DEBUG: (SandWeb::Shell) Not using VCS
> username/password
> 
> Now, a ps grep of the ssh processes running from
> sandweb are:
> 
> webservd  5885  5884   0 16:58:26 pts/3       0:00
> /usr/bin/bash /opt/sfw/bin/sandweb-ssh -l puddle
> 192.168.0.100 cvs server
> 
> webservd  5886  5885   0 16:58:26 pts/3       0:00
> /opt/csw/bin/ssh -q -oStrictHostKeyChecking no -l 
> puddle 192.168.0.100 cvs serv
> 
> webservd   484   483   0   Aug 24 pts/2       0:00
> /usr/bin/bash /opt/sfw/bin/sandweb-ssh -l puddle
> 192.168.0.100 cvs server
> 
> webservd   485   484   0   Aug 24 pts/2       0:00
> /opt/csw/bin/ssh -q -oStrictHostKeyChecking no -l
> puddle 192.168.0.100 cvs server
> 
> When I try to run the ssh command of pid 485 (that I
> believe is passing the sandweb-ssh commands I get:
> 
> Okay, after doing a man sshd_config and on sshd I
> don't see anything about the 'StrictHostKeyChecking'
> option.  
> 
> It was bombing on it as well via the command line.  I
> commented that out (sandweb-ssh) and added just :
> 
> # Here's the main action of this script
> # $SSH_BIN -q -o'StrictHostKeyChecking no' $SSH_ARGS
> $SSH_BIN -q $SSH_ARGS
> 
> Try to check-out again, the same problem white box
> comes up no debug/output.  Watch the server processes
> ssh just hangs.
> 
> When I do a grep of the processes now I get:
> 
> webservd  6051  6050   0 17:15:33 pts/2       0:00
> /usr/bin/bash /opt/sfw/bin/sandweb-ssh -l puddle
> 192.168.0.100 cvs server
> 
> webservd  6052  6051   0 17:15:33 pts/2       0:00
> /opt/csw/bin/ssh -q -l puddle 192.168.0.100 cvs server
> 
> webservd  6050  6047   0 17:15:33 pts/2       0:00
> /opt/sfw/bin/cvs -q -d
> :ext:puddle@192.168.0.100:/export/home/cvsroot/flash/
> ch
> 
> I try it via the command line:
> 
> $ ssh -q -l puddle 192.168.0.100 cvs server
> Password:
> ksh: cvs:  not found
> $
> 
> Which I thought looked weird to the 'cvs server' after
> the ssh command.
> 
> Hope this helps some.
> 
> --- Rob Helmer <ro...@ro...> wrote:
> 
> 
>>Hi William,
>>
>>William Pool (Puddle) wrote:
>>
>>>When I setup a local sandbox using SSH to the
>>
>>actual
>>
>>>machine the SSH session brings up the checkout
>>
>>window
>>
>>>but it's white and nothing appears, then
>>
>>eventually
>>
>>>times out.  The SSH processes on the machine
>>
>>itself
>>
>>>never time-out and just linger.
>>>
>>>So, I'm trying to access the CVS Respository local
>>
>>to
>>
>>>the sandbox machine using SSH so I can use UNIX
>>>permissions on the files.
>>>
>>>Local sandbox setup works, but trying to avoid the
>>>webserver ID owning the files.
>>
>>Try turning on debug in the sandweb.cfg, you will
>>see the output of the 
>>command being used. You can su to your web server
>>user and try running 
>>it to see if you can track down the problem.
>>
>>I'll bet it's something like we're not catching the
>>Sun SSH's password 
>>prompt - this is based on OpenSSH right?
>>
>>
>>--
>>Rob
>>
>>
>>
> 
> -------------------------------------------------------
> 
>>SF.Net email is Sponsored by the Better Software
>>Conference & EXPO
>>September 19-22, 2005 * San Francisco, CA *
>>Development Lifecycle Practices
>>Agile & Plan-Driven Development * Managing Projects
>>& Teams * Testing & QA
>>Security * Process Improvement & Measurement *
>>http://www.sqe.com/bsce5sf
>>_______________________________________________
>>Sandweb-users mailing list
>>San...@li...
>>
> 
> https://lists.sourceforge.net/lists/listinfo/sandweb-users
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Sandweb-users mailing list
> San...@li...
> https://lists.sourceforge.net/lists/listinfo/sandweb-users
> 