transferring file in binary mode

[kknegi]

Hi, we are using OPenSSH version of "3.7.1p1" for remote execution between unix and windows. here we are using SFTP for transferring files from windows to unix box. But the files which gets transferred to unix side contains junk characters as there is no provision of binary transmission in sftp. can anyone help us in this regard as how to eradicate the junk char while transmission of files. Regards, Kishore

[Jeremy C. Reed]

> we are using OPenSSH version of  "3.7.1p1" for remote execution between unix
> and windows.
>
> here we are using SFTP for transferring files from windows to unix box.
>
> But the files which gets transferred to unix side contains junk characters
> as there is no provision of binary transmission in sftp.

I think you have this opposite. It is always transferred in binary as
there is not any "ascii" conversion (like in ftp clients).

> can anyone help us in this regard as how to eradicate the junk char while
> transmission of files.

Search for dos2unix or use perl or awk or tr or sed. Google can quickly
find examples:
http://kb.iu.edu/data/acux.htm
http://www.vasudevaservice.com/documentation/how-to/converting_dos_and_unix_text_files

If that is not what you are referring to, please provide some more details
or examples.

(By the way, it seems like this list is way slow for me. Sometimes I don't
see emails for days.)

[secure.shell]

you're prolly talkin' about windows EOL \r\n (u'll see your "junk" char as ^M) if so
perl -i -pe 's/\r$//g' filename will clean it

On Thu, Dec 14, 2006 at 01:10:20PM -0600, Jeremy C. Reed wrote:

> X-Original-To: secure.shell@...
> Delivered-To: secure.shell@...
> Mailing-List: contact secureshell-help@...; run by ezmlm
> Precedence: bulk
> List-Post: <mailto:secureshell@...>
> List-Help: <mailto:secureshell-help@...>
> List-Unsubscribe: <mailto:secureshell-unsubscribe@...>
> List-Subscribe: <mailto:secureshell-subscribe@...>
> Resent-Sender: listbounce@...
> Errors-To: listbounce@...
> Delivered-To: mailing list secureshell@...
> Delivered-To: moderator for secureshell@...
> Date: Thu, 14 Dec 2006 13:10:20 -0600 (CST)
> From: "Jeremy C. Reed" <reed@...>
> To: kknegi <kishore-singh.negi@...>
> Cc: secureshell@...,
> secureshell-return-9151@...
> Subject: Re: transferring file in binary mode
> In-Reply-To: <7871042.post@...>
> Resent-Message-Id: <20061215144306.9E514237289@...>
> Resent-Date: Fri, 15 Dec 2006 07:43:06 -0700 (MST)
> Resent-From: secureshell-return-9153@...
>
> > we are using OPenSSH version of  "3.7.1p1" for remote execution between unix
> > and windows.
> >
> > here we are using SFTP for transferring files from windows to unix box.
> >
> > But the files which gets transferred to unix side contains junk characters
> > as there is no provision of binary transmission in sftp.
>
> I think you have this opposite. It is always transferred in binary as
> there is not any "ascii" conversion (like in ftp clients).
>
> > can anyone help us in this regard as how to eradicate the junk char while
> > transmission of files.
>
> Search for dos2unix or use perl or awk or tr or sed. Google can quickly
> find examples:
> http://kb.iu.edu/data/acux.htm
> http://www.vasudevaservice.com/documentation/how-to/converting_dos_and_unix_text_files
>
> If that is not what you are referring to, please provide some more details
> or examples.
>
> (By the way, it seems like this list is way slow for me. Sometimes I don't
> see emails for days.)

--

[Jeff Sadowski]

No recent versions of windows I have encountered issues with UNICODE
like for example exporting registry
You can look at
http://billposer.org/Software/uni2ascii.html
But for registry exports it still doesn't work


On 12/15/06, secure.shell
<secure.shell@...> wrote:

>
> you're prolly talkin' about windows EOL \r\n (u'll see your "junk" char as ^M) if so
> perl -i -pe 's/\r$//g' filename will clean it
>
> On Thu, Dec 14, 2006 at 01:10:20PM -0600, Jeremy C. Reed wrote:
> > X-Original-To: secure.shell@...
> > Delivered-To: secure.shell@...
> > Mailing-List: contact secureshell-help@...; run by ezmlm
> > Precedence: bulk
> > List-Post: <mailto:secureshell@...>
> > List-Help: <mailto:secureshell-help@...>
> > List-Unsubscribe: <mailto:secureshell-unsubscribe@...>
> > List-Subscribe: <mailto:secureshell-subscribe@...>
> > Resent-Sender: listbounce@...
> > Errors-To: listbounce@...
> > Delivered-To: mailing list secureshell@...
> > Delivered-To: moderator for secureshell@...
> > Date: Thu, 14 Dec 2006 13:10:20 -0600 (CST)
> > From: "Jeremy C. Reed" <reed@...>
> > To: kknegi <kishore-singh.negi@...>
> > Cc: secureshell@...,
> >       secureshell-return-9151@...
> > Subject: Re: transferring file in binary mode
> > In-Reply-To: <7871042.post@...>
> > Resent-Message-Id: <20061215144306.9E514237289@...>
> > Resent-Date: Fri, 15 Dec 2006 07:43:06 -0700 (MST)
> > Resent-From: secureshell-return-9153@...
> >
> > > we are using OPenSSH version of  "3.7.1p1" for remote execution between unix
> > > and windows.
> > >
> > > here we are using SFTP for transferring files from windows to unix box.
> > >
> > > But the files which gets transferred to unix side contains junk characters
> > > as there is no provision of binary transmission in sftp.
> >
> > I think you have this opposite. It is always transferred in binary as
> > there is not any "ascii" conversion (like in ftp clients).
> >
> > > can anyone help us in this regard as how to eradicate the junk char while
> > > transmission of files.
> >
> > Search for dos2unix or use perl or awk or tr or sed. Google can quickly
> > find examples:
> > http://kb.iu.edu/data/acux.htm
> > http://www.vasudevaservice.com/documentation/how-to/converting_dos_and_unix_text_files
> >
> > If that is not what you are referring to, please provide some more details
> > or examples.
> >
> > (By the way, it seems like this list is way slow for me. Sometimes I don't
> > see emails for days.)
>
> --
>
>

[Jeff Sadowski]

Oh for registry I used the following my registry export was named test.reg
cat test.reg |sed s/\0//
properly viewed my expected output

On 12/18/06, Jeff Sadowski <jeff.sadowski@...> wrote:

> No recent versions of windows I have encountered issues with UNICODE
> like for example exporting registry
> You can look at
> http://billposer.org/Software/uni2ascii.html
> But for registry exports it still doesn't work
>
>
> On 12/15/06, secure.shell
> <secure.shell@...> wrote:
> >
> > you're prolly talkin' about windows EOL \r\n (u'll see your "junk" char as ^M) if so
> > perl -i -pe 's/\r$//g' filename will clean it
> >
> > On Thu, Dec 14, 2006 at 01:10:20PM -0600, Jeremy C. Reed wrote:
> > > X-Original-To: secure.shell@...
> > > Delivered-To: secure.shell@...
> > > Mailing-List: contact secureshell-help@...; run by ezmlm
> > > Precedence: bulk
> > > List-Post: <mailto:secureshell@...>
> > > List-Help: <mailto:secureshell-help@...>
> > > List-Unsubscribe: <mailto:secureshell-unsubscribe@...>
> > > List-Subscribe: <mailto:secureshell-subscribe@...>
> > > Resent-Sender: listbounce@...
> > > Errors-To: listbounce@...
> > > Delivered-To: mailing list secureshell@...
> > > Delivered-To: moderator for secureshell@...
> > > Date: Thu, 14 Dec 2006 13:10:20 -0600 (CST)
> > > From: "Jeremy C. Reed" <reed@...>
> > > To: kknegi <kishore-singh.negi@...>
> > > Cc: secureshell@...,
> > >       secureshell-return-9151@...
> > > Subject: Re: transferring file in binary mode
> > > In-Reply-To: <7871042.post@...>
> > > Resent-Message-Id: <20061215144306.9E514237289@...>
> > > Resent-Date: Fri, 15 Dec 2006 07:43:06 -0700 (MST)
> > > Resent-From: secureshell-return-9153@...
> > >
> > > > we are using OPenSSH version of  "3.7.1p1" for remote execution between unix
> > > > and windows.
> > > >
> > > > here we are using SFTP for transferring files from windows to unix box.
> > > >
> > > > But the files which gets transferred to unix side contains junk characters
> > > > as there is no provision of binary transmission in sftp.
> > >
> > > I think you have this opposite. It is always transferred in binary as
> > > there is not any "ascii" conversion (like in ftp clients).
> > >
> > > > can anyone help us in this regard as how to eradicate the junk char while
> > > > transmission of files.
> > >
> > > Search for dos2unix or use perl or awk or tr or sed. Google can quickly
> > > find examples:
> > > http://kb.iu.edu/data/acux.htm
> > > http://www.vasudevaservice.com/documentation/how-to/converting_dos_and_unix_text_files
> > >
> > > If that is not what you are referring to, please provide some more details
> > > or examples.
> > >
> > > (By the way, it seems like this list is way slow for me. Sometimes I don't
> > > see emails for days.)
> >
> > --
> >
> >
>