Re: [OpenWrt-Devel] openwrt-devel Digest, Vol 103, Issue 58

2014-07-14 Thread Alive4Ever
On Monday, July 14, 2014 12:00:01 PM openwrt-devel-requ...@lists.openwrt.org wrote: > The OpenWrt developers are proud to announce the first release > candidate of OpenWrt Barrier Breaker. Glad to know that Barrier Breaker will be ready to rock. Would it possible to include my ticket #17028 here? I

[OpenWrt-Devel] [PATCH] [package] dropbear: updated to version 2014.64

2014-08-03 Thread Alive4Ever
Integrate latest dropbear release to base system (2014.64) diff --git a/package/network/services/dropbear/Makefile b/package/network/services/dropbear/Makefile index b2bd8cc..d1f0cff 100644 --- a/package/network/services/dropbear/Makefile +++ b/package/network/services/dropbear/Makefile @@ -8,14 +

[OpenWrt-Devel] Compilation errors on Ubuntu 14.04 64-bit.

2014-08-04 Thread Alive4Ever
I can't compile current Openwrt on Ubuntu 14.04 64bit. Latest commit from git log is commit f99433ba8bb4777a868b955d8e33d7d9e29b5065 Author: blogic Date: Sun Aug 3 11:13:58 2014 + firmware-utils: made mkdir615h1 work for all Senao- produced devices as mksen Signed-off-by: Fore

Re: [OpenWrt-Devel] [PATCH] [package] dropbear: updated to version 2014.64

2014-08-04 Thread Alive4Ever
Some included patch series are broken and cannot be applied automatically for version 2014.64. Manual work is needed for these patches to apply cleanly. 110-change_user.patch 130-ssh_ignore_o_and_x_args.patch 140-disable_assert.patch This patch will fix them all to apply cleanly to version 20

Re: [OpenWrt-Devel] [PATCH] [package] dropbear: updated to version 2014.64

2014-08-04 Thread Alive4Ever
It seems that my mua is using word wrap and destroying the patch. Here is unwrapped patch to fix failed hunks. Signed-off-by: Alif Ahmad diff --git a/package/network/services/dropbear/Makefile b/package/network/services/dropbear/Makefile index b2bd8cc..d1f0cff 100644 --- a/package/network/serv

[OpenWrt-Devel] Picocom should be re-included in packages.

2014-08-12 Thread Alive4Ever
On latest Openwrt commits, picocom is missing. Formerly, picocom was available on Utilities/Terminal section of menuconfig. I think picocom should be re-included, because it's very handy and usable for serial diagnostics, especially on systems with only 4 MB of flash, such as TL MR3220. Compar

[OpenWrt-Devel] Request for including xz-utils in the packages

2014-08-15 Thread Alive4Ever
I've been navigating through the package list and I did not find xz-utils in the packages section. Since xz archives are gaining popularity, it would be better to package xz-utils and xz-embedded for Openwrt. They should be available under menuconfig on Utilities/Compression. Busybox has xz co

[OpenWrt-Devel] Including git revision commit hash and svn revision id on release announcement.

2014-08-27 Thread Alive4Ever
Hello developers. Probably you are annoyed by people asking which revision is Barrier Breaker RC3 or similar, because they want to be able to compile the specific release theirselves. To address this issue, I think it would be better to add git revision commit hash for each Openwrt release announ

[OpenWrt-Devel] [Bug: Busybox 1.22.1] false return 0 instead of 1 with '--help' switch.

2014-08-29 Thread Alive4ever
I'm using an embedded system with busybox v1.22.1, running Openwrt Chaos Chalmer r42321, mips24k AR9330 When I call 'busybox false --help', the return status is zero. I think it has nothing todo with openwrt, because it's the output of busybox, not the problem on openwrt performance. I feel it'

[OpenWrt-Devel] [Bug: Busybox 1.22.1] false return 0 instead of 1 with '--help' switch.

2014-08-30 Thread Alive4ever
I'm using an embedded system with busybox v1.22.1, running Openwrt Chaos Chalmer r42321, mips24k AR9330 When I call 'busybox false --help', the return status is zero. I think it has nothing todo with openwrt, because it's the output of busybox, not the problem on openwrt performance. I feel it'

Re: [OpenWrt-Devel] [Bug: Busybox 1.22.1] false return 0 instead of 1 with '--help' switch.

2014-09-02 Thread Alive4Ever
On Friday, August 29, 2014 02:08:56 PM Bastian Bittorf wrote: > * Alive4ever [29.08.2014 14:03]: > > I'm using an embedded system with busybox v1.22.1, running Openwrt Chaos > > Chalmer r42321, mips24k AR9330 > > > > When I call 'busybox false --help&#x

[OpenWrt-Devel] [PATCH][package] dropbear: enable sha2-based hmac by default.

2014-09-23 Thread Alive4Ever
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

Re: [OpenWrt-Devel] [PATCH][package] dropbear: enable sha2-based hmac by default.

2014-09-24 Thread Alive4Ever
> 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

[OpenWrt-Devel] Unable to compile libnl-tiny [stdio.h not found]

2014-10-08 Thread Alive4Ever
Hello openwrt devs! Since I moved the openwrt build directory to another partition on another external hard-drive, I'm unable to compile openwrt. Everytime I run openwrt build process, the following error occurs and compilation stopped prematurely. Here is the error message produced by `make V=s`

Re: [OpenWrt-Devel] Unable to compile libnl-tiny [stdio.h not found]

2014-10-08 Thread Alive4Ever
On Wednesday, October 08, 2014 07:02:33 PM Felix Fietkau wrote: > Try running make dirclean and rebuild. Thanks. I'll try this workaround. I'll check if this will fix the problem. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lis

Re: [OpenWrt-Devel] [PATCH] [package] dropbear: enable sha2-based hmac by default.

2014-10-08 Thread Alive4Ever
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

[OpenWrt-Devel] cyassl is causing build errors

2014-10-13 Thread Alive4Ever
I've experienced many build errors on bb-14.07 because of cyassl. For your information, cyassl can't be downloaded directly from its official site. There is a form that needs to be filled before Wolfssl allows downloading of cyassl-3.2.0.zip. Any attemt to download cyassl directly will cause redir

Re: [OpenWrt-Devel] cyassl is causing build errors (Alive4Ever)

2014-10-13 Thread Alive4Ever
On Monday, October 13, 2014 09:49:15 AM openwrt-devel-requ...@lists.openwrt.org wrote: > Message: 4 > Date: Mon, 13 Oct 2014 14:20:07 +0700 > From: Alive4Ever > To: OpenWrt Development List > Subject: [OpenWrt-Devel] cyassl is causing build errors > Message-ID: > Con

[OpenWrt-Devel] Consider enabling HTTPS for wiki.openwrt.org

2014-10-16 Thread Alive4Ever
I'm unable to access http://wiki.openwrt.org. It seems that the wiki site is down. Is there any maintenance to the wiki? If it's because of maintenance, I suggest to implement tls over http (https) to secure data integrity. So that, editing and viewing OpenWrt wiki will be more convenient. I fee