Windows to Linux File Transfer (Automatically)

David Bear David.Bear at asu.edu
Fri Oct 22 17:54:50 UTC 2010


On Fri, Oct 22, 2010 at 9:21 AM, sunhux G <sunhux at gmail.com> wrote:

> Hi David
>
> So, with the private+public key pair, we'll be doing something like
>   ssh user at remotehost 'cat remotefile' | dos2unix >> localfile
> if I'm initiating ssh from my Linux box to a remote Windows box?
> Would the above command be equivalent of ftp's get with 'ascii' +
> 'append' feature ? Would this command be equivalent to ftp get with
> ascii & append mode?
>
>
I wouldn't use ssh that way. I would use something like this:

rsync -e ssh -a somelocalfile someuser at someremotehost:/somepath/somefile

I don't think ascii mode has any important meaning when transferring files
from windows to linux when you expect to continue to use the file on
windows. Even then, using a binary transferred file on linux presents little
problems if you use an editor that understands line endings. rsync will find
the differences between the files and transfer those.


> What would be the equivalent command for ftp put with ascii & append
> mode then?  I can't figure this out.  With ftp, this is plain sailing.
>
> Would you be able to provide the equivalent rsync via ssh with ascii
> & append modes built in (kindly provide equivalents for get & put)
>
>
> Thanks
> U
>
>
> On Fri, Oct 22, 2010 at 8:23 AM, David Bear <David.Bear at asu.edu> wrote:
>
> > I don't think 'ascii' mode is important any longer. But if it is and you
> > want 'append' you should consider using rsync over ssh. rsync treats all
> > files as binary -- which has been safe for all use cases I have had when
> > transferring files from windows to linux and back. running rsync over ssh
> > is
> > secure as well -- and you can use ssh public keys to make the connection
> > passwordless and secure. rsync also will only transfer the 'diffs' -- so
> if
> > file a, b, and c have not changed, but d has changed (and only the 15th
> > thru
> > the 60th byte) then only the changes to d will be sent. rsync does not
> > handle ntfs alternate data streams, and sometimes seems to barf on
> unicode
> > file names using asian charactersets.  so you should test well.
> >
> > On Thu, Oct 21, 2010 at 5:59 AM, sunhux G <sunhux at gmail.com> wrote:
> >
> > > pscp or psftp do not support "ASCII" mode transfer which is available
> in
> > > ftp
> > > - this was a shortcoming I faced when transferring files between
> Windows
> > &
> > >  Unix boxes.  pscp/psftp doesn't support "APPEND" mode too while ftp
> > does.
> > >
> > > Having said that ftp does not transfer data as securely as 'scp' or
> > 'sftp'
> > >
> > > winscp supports "ASCII" though & I think if you're transferring a whole
> > > subdirectory of files, winscp will detect which file to be transferred
> in
> > > ASCII & which in Binary.
> > >
> > > U
> > >
> >
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>



-- 
David Bear
College of Public Programs at ASU
602-494-0424



More information about the redhat-list mailing list