Peter Stuge | 2 Jul 2010 09:35
Picon

Re: libssh2: Ported to UC Linux ?

Hi Paul,

Paul Romero wrote:
> First, thank you for the quick and detailed reply and be assured
> the difference between SSH and SASL is clear to me.

Great!

> Also, I must emphasize that my interest is in the SSH-2 component
> subset required to support SFTP rather than SSH.

Ah, sorry for being a bit sloppy with terminology. These days SSH
version 1 is not in wide use anymore, so I tend to put SSH = SSH
version 2 always. libssh2 only supports SSH version 2.

> I think the SASL version of  libgcrypt meets the minimum libssh2
> requirements, and that AES and RIJNDAEL are the same.

That's correct.

> Also, I assume that libssh2 can use DES and 3DES interchangeably.

They are distinct algorithms, and SSH requires 3DES. Several
algorithms are OPTIONAL in the standard, including AES/RIJNDAEL,
although it is listed as RECOMMENDED and aes128-ctr, aes192-ctr and
aes256-ctr is likely to become REQUIRED in the future so I always
strongly recommend that they be included.

> It appears most SFTP  implementations also use the following:
> Diffie Hellman-SHA1, Blowfish, Twofish,  HMAC-SHA1 and HMAC-MD5.
(Continue reading)

Paul Romero | 2 Jul 2010 17:10

Re: libssh2: Ported to UC Linux ?

Hi Peter:

What you wrote seems clear to me.   However,  let me describe
the host and target environment again to insure we understand
each other.

The GNL ELF tool chain is used to cross-compile the target executable,
which includes the entire UC Linux OS, and the applications
in the host environment.  The executable is then converted into
an S19 format file and downloaded to the target environment.

The host is just an i686  Debian Linux system.
The target is an M5249 Coldfire processor.
The important target settings are as follows:

ARCH=m68knommu
CROSS_COMPILE=m68k-elf-

Does this make sense to you ?

Best Regards,

Paul R.

Peter Stuge wrote:

> Hi Paul,
>
> Paul Romero wrote:
> > First, thank you for the quick and detailed reply and be assured
(Continue reading)

Peter Stuge | 2 Jul 2010 23:57
Picon

Re: libssh2: Ported to UC Linux ?

Hi,

Paul Romero wrote:
> What you wrote seems clear to me.   However,  let me describe
> the host and target environment again to insure we understand
> each other.

I don't know if we need to. :) I described a general recipe for how
to cross-compile libssh2 so that you could do it regardless of your
platform. I guessed at the particular tuple, and it even turned out
to be what you are using.

> The important target settings are as follows:
> 
> ARCH=m68knommu
> CROSS_COMPILE=m68k-elf-
> 
> Does this make sense to you ?

See the email I wrote before:

> > Make sure the toolchain programs are included in your PATH, and use
> > the --host=tuple parameter when configuring libssh2. Substitute tuple
> > with the prefix for your toolchain, so if your toolchain provides
> > m68k-elf-gcc, then run configure --host=m68k-elf and include the
> > library paths needed.

You should use exactly the host tuple I wrote in the last mail, make
sure to not include the trailing - that you included in the
CROSS_COMPILE variable above.
(Continue reading)

Paul Romero | 3 Jul 2010 19:18

Re: libssh2: Ported to UC Linux ?

Hi Peter:

Thank you for the clarification.  I am now confident I understand
what you wrote in your previous E-Mail messages. Incidentally,
the libssh2 package compiles without problems in the Debian
Linux environment.

Best Regards,

Paul R.

Peter Stuge wrote:

> Hi,
>
> Paul Romero wrote:
> > What you wrote seems clear to me.   However,  let me describe
> > the host and target environment again to insure we understand
> > each other.
>
> I don't know if we need to. :) I described a general recipe for how
> to cross-compile libssh2 so that you could do it regardless of your
> platform. I guessed at the particular tuple, and it even turned out
> to be what you are using.
>
> > The important target settings are as follows:
> >
> > ARCH=m68knommu
> > CROSS_COMPILE=m68k-elf-
> >
(Continue reading)


Gmane