Subject: Re: AES-CTR not available upon configure ibssh2 1.2.6

Re: AES-CTR not available upon configure ibssh2 1.2.6

From: Peter Stuge <>
Date: Wed, 18 Aug 2010 16:50:16 +0200

A. Mark wrote:
> I'm programming a peer to peer model application,

Then you need to consider if SSH is the best protocol for you.

> my issue now is that I need to send a 128KB buffer securely between
> the two hosts.

What exactly does "securely" mean here?

> I believe the "direct tcp ip" approach of libssh2 is one solution,
> basically sshd acts as a tunnel between the two apps and the data is
> safe. I'm wondering though if this is way too cumbersome.

Yes, it is. But it also depends on the problem you want to solve. You
didn't describe that at all, so we can't really help you.

> If I could simply use the openssl library to create secure sockets
> it may be relatively simple, since all i need to do is send a block
> of data securely between the apps.

This is not simple. You must consider many things, in order to
correctly define "securely".

SSL/TLS and SSH are not some magic "security" layers. You must really
understand the security requirements in the application. Please
describe your requirements, in detail.

Received on 2010-08-18