On Friday, October 03, 2014 01:55:29 PM Weedy wrote:
> Based off failed ciphers/macs
> no matching cipher found: client rijndael-...@lysator.liu.se server
> aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes256-cbc
> no matching mac found: client hmac-ripemd160-...@openssh.com server
> hmac-sha
On 27/09/14 01:29 PM, Alive wrote:
> On 27/09/2014 23:34, Weedy wrote:
>> I got bit by this last week when I audited my ssh config and dropped all
>> weak/slow ciphers.
>> Couldn't log into my routers and had to add md5 ciphers and macs back.
>>
> You must rebuild dropbear package cleanly to test t
On 27/09/2014 23:34, Weedy wrote:
> I got bit by this last week when I audited my ssh config and dropped all
> weak/slow ciphers.
> Couldn't log into my routers and had to add md5 ciphers and macs back.
>
You must rebuild dropbear package cleanly to test this patch
Save the patch as file located
I got bit by this last week when I audited my ssh config and dropped all
weak/slow ciphers.
Couldn't log into my routers and had to add md5 ciphers and macs back.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi
On 26/09/2014 10:11, Catalin Patulea wrote:
> What's the motivation for this change?
>
> On Thu, Sep 25, 2014 at 11:43 AM, Alive wrote:
>> X-Patchwork-Id: 6322
>> Message-Id:
>>
>> Is there any chance for my proposed patch to be committed?
>> http://patchwork.openwrt.org/patch/6322/
>>
>> Here i
What's the motivation for this change?
On Thu, Sep 25, 2014 at 11:43 AM, Alive wrote:
> X-Patchwork-Id: 6322
> Message-Id:
>
> Is there any chance for my proposed patch to be committed?
> http://patchwork.openwrt.org/patch/6322/
>
> Here is a brief comparison about binary and package size increa
X-Patchwork-Id: 6322
Message-Id:
Is there any chance for my proposed patch to be committed?
http://patchwork.openwrt.org/patch/6322/
Here is a brief comparison about binary and package size increase.
Tested on AR9330, mips, TL MR3220v2
Before applying sha2-hmac patch
root@OpenWrt:~# du -sh $(wh
> Whats the size increase due to that?
>
> ~ Jow
Here is a brief comparison about binary and package size
Tested on AR9330, mips, TL MR3220v2
Before applying sha2-hmac patch
root@OpenWrt:~# du -sh $(which dropbear)
161.5K /usr/sbin/dropbear
After applying sha2-hmac patch
root@OpenWrt:~# du -sh
Hi.
> Dropbear should support sha2-based message authentication.
> This patch will enable hmac-sha2-256 and hmac-sha2-512.
Whats the size increase due to that?
~ Jow
>
>
> --- a/options.h
> +++ b/options.h
> @@ -128,8 +128,8 @@ much traffic. */
> * which are not the
Dropbear should support sha2-based message authentication.
This patch will enable hmac-sha2-256 and hmac-sha2-512.
--- a/options.h
+++ b/options.h
@@ -128,8 +128,8 @@ much traffic. */
* which are not the standard form. */
#define DROPBEAR_SHA1_HMAC
/*#define DROPBEAR_S
10 matches
Mail list logo