On Tue, Jun 30, 2020 at 8:09 PM Aris Adamantiadis wrote:
>
> Hi Felipe,
>
> In SSH, all authentication schemes are signature-based. Specifically
> user authentication is based on signing the master hash that's derived
> from key exchange (i.e. everything that was shared by peers + shared
> secret)
On Tue, Jun 30, 2020 at 1:59 AM Felipe Gasper wrote:
>
> Hello,
>
> I want to rig up a simple authentication based on SSH keys but over a
> preexisting TLS connection.
>
> Since TLS already handles the encryption, would the authentication be
> as simple as verifying a decode of a
On Thu, Jan 16, 2020 at 4:29 PM Andreas Schneider wrote:
>
> On Thursday, 16 January 2020 14:40:50 CET g4-l...@tonarchiv.ch wrote:
> > Hi there,
> >
> > cmake detects pthreads and compiling goes well. But on linking, there
> > are unresolved references:
> >
> > CMakeFiles/ssh.dir/objects.a(pthread
On Fri, 2018-09-21 at 15:11 +0200, Aris Adamantiadis wrote:
> Hi Nikos,
>
> I share your point of view over group exchange. I even made some
> (poor)
> research myself on how bad parameters in /etc/moduli could make SSH
> key
> exchanges trivially breakable. Like you said, it boils down to
> convi
On Mon, 2018-09-10 at 17:26 +0200, Aris Adamantiadis wrote:
> Hi Anderson,
>
> Thanks for your contribution. I am not particularly fond of hardcoded
> DH
> groups such as group14 or group16, especially since we have
> dh-group-exchange now. Is it needed to connect to some device that
> has group16
On Tue, Aug 21, 2018 at 4:50 PM, Anderson Sasaki wrote:
> - Original Message -
>> From: "Antonio Rojas"
>> To: libssh@libssh.org
>> Sent: Tuesday, August 21, 2018 4:08:43 PM
>> Subject: Re: libssh 0.8.1 breaks amarok
>>
>> El martes, 21 de agosto de 2018 15:26:13 (CEST) Andreas Schneider
Hi,
In the context Fedora we are looking at various ways for applications
to get a reasonable and adjustable default policy for crypto ciphers
and parameters. Our goal is to be able to disable ciphers system-wide
when necessary, without going through all possible applications. So far
we have succe
/merge_requests/4
From d261370f7a24e6137c6ce76ca977cd899d39b57f Mon Sep 17 00:00:00 2001
From: Nikos Mavrogiannopoulos
Date: Fri, 29 Jun 2018 16:29:34 +0200
Subject: [PATCH] .gitlab-ci.yml: added build for mips platform
This tests multiple items, (1) cross compilation, (2) compilation
on debian and (3) CI
On Tue, 2018-04-17 at 18:02 +0200, Andreas Schneider wrote:
> On Friday, 13 April 2018 10:53:12 CEST Nikos Mavrogiannopoulos wrote:
> > Hi,
>
> Hi Nikos,
>
> > These small fixes are needed for running the testsuite under
> > docker
> > and under centos
Hi,
These small fixes are needed for running the testsuite under docker
and under centos7.
regards,
Nikos
From a3e50b74d4af5711b4a4ade95cca5f291b70e2a2 Mon Sep 17 00:00:00 2001
From: Nikos Mavrogiannopoulos
Date: Thu, 12 Apr 2018 17:03:06 +0200
Subject: [PATCH 1/2
On Wed, 2017-12-20 at 12:27 +0100, Aris Adamantiadis wrote:
> Hi Nikos,
>
> Libssh by itself is threadsafe. The requirements here are for the
> backends. Openssl and libgcrypt (older versions) are far from being
> transparent, for the same reason as we did: forcing usage of one of
> the
> differe
On Wed, 2017-12-20 at 10:38 +0100, Andreas Schneider wrote:
> On Tuesday, 12 December 2017 01:25:58 CET Ахриев Альберт wrote:
> > Dear All,
> >
> > As a newcomer I am struggling to understand how to use libssh in
> > multithreaded environment.
> >
> > Very simple question: if application create
On Tue, 2017-11-14 at 12:31 +0100, Andreas Schneider wrote:
> On Tuesday, 14 November 2017 12:08:06 CET Nikos Mavrogiannopoulos
> wrote:
> > Hi,
>
> Hi,
>
> > While adding support of libssh to curl, I stumbled on the
> > sftp_async_read_begin and sftp_async_rea
Hi,
While adding support of libssh to curl, I stumbled on the
sftp_async_read_begin and sftp_async_read APIs. Both accept file
size as uint32_t instead of size_t. In SCP or the other SFTP APIs,
there is no such limitation. Is that limitation intentional?
Would it make sense to try to work around
On Tue, 2017-10-31 at 10:07 +0200, Nikolay wrote:
> Hi, Nikos.
>
> Unfortunately, libssh is not completely non-blocking. It only has
> non-blocking mode for a set of calls.
I realized that as the scp subsystem fails to work when the session is
put in non-blocking mode. In the curl patch I put th
Hi,
I have send a pull request to curl [0] to use libssh as an SCP back-
end, however there is an open issue with non-blocking mode on the new
code.
libssh2 supports non-blocking mode on read and writes, and provides a
function for the caller to determine whether it should wait on the
descriptor
16 matches
Mail list logo
