From: Maciej Soltysiak <maciej@soltysiak.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Available MACs in dropbear
Date: Fri, 24 Oct 2014 19:31:05 +0200 [thread overview]
Message-ID: <CAMZR1YA9vEOm2h51zz+ZWV8RXQPjfFvJGSKmo-jtiQAb6XZevw@mail.gmail.com> (raw)
Hi list,
For some reason dropbear doesn't have modern MACs for SSH. On cero
3.10.36 I've got Dropbear SSH client v2013.59:
root@cerowrt:/etc# ssh -m help
ssh: Available MACs:
hmac-sha1-96,hmac-sha1,hmac-md5
(MD5 BTW...)
However, dropbear since v2013.56 has support for sha2
(https://matt.ucc.asn.au/dropbear/CHANGES):
Added hmac-sha2-256 and hmac-sha2-512 support (off by default, use options.h)
It might be that we don't have it enabled in the cero build.
The reason why it hurts me is that I have servers configured according
to bettercrypto.org and I can't connect from cero (rare occasions, but
they happen). I get:
ssh: Connection to user@server.com:22 exited: No matching algo mac c->s
I apologize for not looking at github, but I'm really low on time :-((
Do we have sha2 in dropbear in later cero versions or do we have to
modify the build?
I wonder what openwrt has configured...
Best regards,
Maciej
next reply other threads:[~2014-10-24 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 17:31 Maciej Soltysiak [this message]
2014-10-24 17:52 ` Michael Richardson
2014-10-24 18:40 ` Maciej Soltysiak
2014-10-24 18:54 ` Michael Richardson
2014-10-25 12:31 ` Maciej Soltysiak
2014-10-25 13:36 ` Dave Taht
2014-10-25 15:37 ` Maciej Soltysiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMZR1YA9vEOm2h51zz+ZWV8RXQPjfFvJGSKmo-jtiQAb6XZevw@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox