From: Maciej Soltysiak <maciej@soltysiak.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Available MACs in dropbear
Date: Fri, 24 Oct 2014 20:40:55 +0200 [thread overview]
Message-ID: <CAMZR1YBZNf_vWL7h5oMZkj+CFw1xxU5dJ17tH7kbQ66_eATKxQ@mail.gmail.com> (raw)
In-Reply-To: <4186.1414173172@sandelman.ca>
On Fri, Oct 24, 2014 at 7:52 PM, Michael Richardson <mcr@sandelman.ca> wrote:
> > 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
>
> 1) MD5 != HMAC-MD5.
That I didn't know, thanks Michael. For some reason bettercrypto.org
people make sure not to use hmac-md5 by suggesting the following:
MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160
I believe I'd be able to connect to if SHA256 or SHA512 was enabled here:
https://github.com/dtaht/cerowrt-3.10/blob/master/package/network/services/dropbear/patches/120-openwrt_options.patch
> 2) SSHv2 is not SSL, and POODLE would be impossible against SSHv2 (or IPsec
> for that matter).
That, I'm aware of, yes.
Best regards,
Maciej
next prev parent reply other threads:[~2014-10-24 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 17:31 Maciej Soltysiak
2014-10-24 17:52 ` Michael Richardson
2014-10-24 18:40 ` Maciej Soltysiak [this message]
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=CAMZR1YBZNf_vWL7h5oMZkj+CFw1xxU5dJ17tH7kbQ66_eATKxQ@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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