Daniel Stenberg wrote:
> > I've attached my current git diff master state for review as well as
> > testing.
>
> Here's some quick first questions/notes:
Thanks for checking it out!
> Which axTLS version or versions does this work with?
I've tested it with r250 of the svn repo, which is now
On Mon, 17 Oct 2016, Peter Stuge wrote:
I've attached my current git diff master state for review as well as
testing. It has a couple of things which still need to be done, but is
already functional.
The diff also includes a few unrelated cleanups; a few type issues and not
using RSA if the
Hi,
Daniel Stenberg wrote:
> > Can that date please be pushed two weeks? I'm not sure I can
> > find time to finish the code up completely by the 11th.
>
> Now we're 8 days away from release. I think you need to subit this
> work ASAP if you still think you can get it into the release - so
>
On Mon, 26 Sep 2016, Peter Stuge wrote:
Can that date please be pushed two weeks? I'm not sure I can find time to
finish the code up completely by the 11th.
Now we're 8 days away from release. I think you need to subit this work ASAP
if you still think you can get it into the release - so
On Fri, 14 Oct 2016, Yuriy M. Kaminskiy wrote:
E.g. that libssh2 uses oversized exponent (private key) in DH handshake,
which renders it several times slower than it should?
E.g. that libssh2 fails to verify if received field length fits in buffer
size *everywhere*, and so malicious server
Daniel Stenberg writes:
> I think it is about time we ship another release. The OpenSSL 1.1.0
> support being a major reason I think.
>
> So, please bring up your issues that we should squeeze in before we
> release.
E.g. that libssh2 uses oversized exponent (private key) in DH
On Mon, 26 Sep 2016, Peter Stuge wrote:
I would like to propose that we aim for doing the release on Tuesday
October 11.
Can that date please be pushed two weeks? I'm not sure I can find time to
finish the code up completely by the 11th.
Absolutely! Let's go with October 25th instead. With
Daniel Stenberg wrote:
> So, please bring up your issues that we should squeeze in before we release.
I've implemented axTLS as crypto provider. It's not quite done, but
so far it works with non-key authentication, test on Linux and Windows.
With that there's an all-BSD way to use libssh2
On Fri, 23 Sep 2016, Ben Kibbey wrote:
Support for passphrase authentication when using an identity would be nice
when libssh2 is compiled with libgcrypt. This would also maybe have the
benefit of not requiring both the secret and public ssh key but only the
private key.
That's already
On Fri, Sep 23, 2016 at 11:48:51PM +0200, Daniel Stenberg wrote:
> Hi friends,
>
> I think it is about time we ship another release. The OpenSSL 1.1.0 support
> being a major reason I think.
>
> So, please bring up your issues that we should squeeze in before we release.
Support for passphrase
Hi friends,
I think it is about time we ship another release. The OpenSSL 1.1.0 support
being a major reason I think.
So, please bring up your issues that we should squeeze in before we release.
We have a whole bunch of issues and pull-requests we could use more eyes and
hands on to deal
11 matches
Mail list logo