Content-type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN"
Content-disposition: inline

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 23, 2005 at 03:10:45PM +1000, openssh-unix-dev-request@mindrot.=
org wrote:
> Date: Fri, 19 Aug 2005 17:56:19 +1000
> From: Darren Tucker
> Subject: Re: OpenSSH sget/sput suggestion
> To: CRX Driver
> Cc: openssh-unix-dev@mindrot.org
> Message-ID: <430590A3.1090506@zip.com.au>
> Content-Type: text/plain; charset=3DISO-8859-1
> CRX Driver wrote:
> >>>Imagine this:
> >>>
> >>>ssh user@machine.com
> >>>cd /home/user
> >>>ls
> >>>rm junk
> >>>sget logfile

> >=20
> >>You can already do this with sftp.

> >=20
> > You can file browse with sftp, but you cannot run programs, kill proces=

> > and then grab a file all while already on-line through an existing ssh.

> See also the related discussion earlier on this list:
> http://marc.theaimsgroup.com/?l=3Dop...16732631189&w=


Regarding the above thread and the above linked thread...

Having the "ssh -MS ..." is nice, but is NOT the same feature. I've been
meaning to impliment the feature referenced in the above thread for over a
year now.

There's no reason I shouldn't be able to be in the middle of some work on a
shell and put or get a file - though instead of making a ~S, I would have
implimented it in the ~C cli interface.

For example, it would be great to be doing something on a remote box, reali=
I need the 4-line script in my local ~/bin and do a ~C, sput ~/bin/script,
quit, ./script.

Or have some long shell-pipeline and then redirect it to a file and then do=
sget file, quit, and continue working.

Phil Dibowitz

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.4.0 (SunOS)



Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

openssh-unix-dev mailing list