Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Available MACs in dropbear
Date: Sat, 25 Oct 2014 17:37:33 +0200	[thread overview]
Message-ID: <CAMZR1YC5Ua92FJo2KwM-sX4_cQm3GtvaihzX7QNTfnZ8ed03Cw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5Zcuw-B6Nyc4gy40eGTVT+ycaXOmWmCDsB64J3p-LdpA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]

Funny thing. Latest dropbear still has these 2 commented out for some
reason. Maybe it's worth checking upstream.

Maciej
On 25 Oct 2014 15:36, "Dave Taht" <dave.taht@gmail.com> wrote:

> I'd argue more in favor of updating to the latest dropbear, pulled anyway.
>
> On Sat, Oct 25, 2014 at 5:31 AM, Maciej Soltysiak <maciej@soltysiak.com>
> wrote:
> > On Fri, Oct 24, 2014 at 8:54 PM, Michael Richardson <mcr@sandelman.ca>
> wrote:
> >>
> >> Maciej Soltysiak <maciej@soltysiak.com> 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
> >>
> >> Yeah, people get very excited over pattern matching of crypto
> algorithms.
> > Well, that may be the case. Here though, I'm more interested in
> introducing
> > HMAC-SHA2s, than eradicating HMAC-MD5 as my setups wouldn't allow it
> anyway.
> >
> > Anyway, Dave, here's the pull request:
> > https://github.com/dtaht/cerowrt-3.10/pull/1
> > And here's the commit I'm suggesting:
> >
> https://github.com/pysiak/cerowrt-3.10/commit/3cac2227700561272e3476f568318c42975bc813
> >
> > The request is to patch a patch unfortunately :-)
> >
> > Can you have a look, please?
> > Maciej Soltysiak
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> Dave Täht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>

[-- Attachment #2: Type: text/html, Size: 2896 bytes --]

      reply	other threads:[~2014-10-25 15:37 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
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 [this message]

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=CAMZR1YC5Ua92FJo2KwM-sX4_cQm3GtvaihzX7QNTfnZ8ed03Cw@mail.gmail.com \
    --to=maciej@soltysiak.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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