[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ECC
[Thread Prev] | [Thread Next]
- Subject: Re: ECC
- From: Dustin Oprea <myselfasunder@xxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Fri, 14 Feb 2014 14:22:28 -0500
- To: libssh <libssh@xxxxxxxxxx>
Yeah. I'm not on the same machine, right now, but it also seems like, even
when I try to connect with an ECDSA certificate, it coerces me into RSA.
Andreas/Aris: What's the state of EC support?
Dustin
On Fri, Feb 14, 2014 at 11:20 AM, Alan Dunn <amdunn@xxxxxxxxx> wrote:
> I don't think you are missing anything; I don't think there's a way to do
> it.
>
> I wrote a patch that adds SSH_BIND_OPTIONS_ECDSAKEY analogously to the
> other two. I added an option to samplesshd to allow this new key type
> as well. But I'm encountering other unexpected problems in using an
> ECDSA key (generated by libssh no less) that lead me to believe that
> maybe more work is necessary than this to have a server ECDSA key.
>
> On Fri, Feb 14, 2014 at 7:55 AM, Dustin Oprea <myselfasunder@xxxxxxxxx>
> wrote:
> > I thought I saw an update about elliptic-curve support, however I don't
> see
> > how to load an EC host-key:
> >
> > enum ssh_bind_options_e {
> > SSH_BIND_OPTIONS_BINDADDR,
> > SSH_BIND_OPTIONS_BINDPORT,
> > SSH_BIND_OPTIONS_BINDPORT_STR,
> > SSH_BIND_OPTIONS_HOSTKEY,
> > SSH_BIND_OPTIONS_DSAKEY,
> > SSH_BIND_OPTIONS_RSAKEY,
> > SSH_BIND_OPTIONS_BANNER,
> > SSH_BIND_OPTIONS_LOG_VERBOSITY,
> > SSH_BIND_OPTIONS_LOG_VERBOSITY_STR
> > };
> >
> > What am I missing?
> >
> >
> >
> > Dustin
>
>
| Re: ECC | Andreas Schneider <asn@xxxxxxxxxxxxxx> |