Re: [OpenWrt-Devel] [PATCH] dropbear: update to 2014.63
ping??
On Sat, Mar 1, 2014 at 4:05 AM, Catalin Patulea c...@vv.carleton.ca wrote:
ping
On Mon, Feb 24, 2014 at 1:02 AM, Catalin Patulea c...@vv.carleton.ca wrote:
Upstream changelog:
https://matt.ucc.asn.au/dropbear/CHANGES
This adds elliptic curve cryptography (ECC) support as an option, disabled
by default.
dropbear mips 34kc uClibc binary size:
before: 161,672 bytes
after, without ECC (default): 164,968
after, with ECC: 198,008
Signed-off-by: Catalin Patulea c...@vv.carleton.ca
---
package/network/services/dropbear/Config.in| 27 ++
package/network/services/dropbear/Makefile | 24 ++--
.../dropbear/patches/100-pubkey_path.patch |4 +--
.../dropbear/patches/110-change_user.patch |2 +-
.../dropbear/patches/120-openwrt_options.patch | 21 --
.../dropbear/patches/140-disable_assert.patch |2 +-
.../patches/150-dbconvert_standalone.patch |6 ++--
.../dropbear/patches/200-lcrypt_bsdfix.patch | 29
.../dropbear/patches/500-set-default-path.patch|2 +-
9 files changed, 63 insertions(+), 54 deletions(-)
create mode 100644 package/network/services/dropbear/Config.in
delete mode 100644
package/network/services/dropbear/patches/200-lcrypt_bsdfix.patch
diff --git a/package/network/services/dropbear/Config.in
b/package/network/services/dropbear/Config.in
new file mode 100644
index 000..e2a7610
--- /dev/null
+++ b/package/network/services/dropbear/Config.in
@@ -0,0 +1,27 @@
+menu Configuration
+ depends on PACKAGE_dropbear
+
+config DROPBEAR_ECC
+ bool Elliptic curve cryptography (ECC)
+ default n
+ help
+ Enables elliptic curve cryptography (ECC) support in key
exchange and public key
+ authentication.
+
+ Key exchange algorithms:
+ ecdh-sha2-nistp256
+ ecdh-sha2-nistp384
+ ecdh-sha2-nistp521
+ curve25519-sha...@libssh.org
+
+ Public key algorithms:
+ ecdsa-sha2-nistp256
+ ecdsa-sha2-nistp384
+ ecdsa-sha2-nistp521
+
+ Does not generate ECC host keys by default (ECC key exchange
will not be used,
+ only ECC public key auth).
+
+ Increases binary size by about 36 kB (MIPS).
+
+endmenu
diff --git a/package/network/services/dropbear/Makefile
b/package/network/services/dropbear/Makefile
index 02be761..692199e 100644
--- a/package/network/services/dropbear/Makefile
+++ b/package/network/services/dropbear/Makefile
@@ -8,26 +8,32 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=dropbear
-PKG_VERSION:=2013.59
+PKG_VERSION:=2014.63
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:= \
http://matt.ucc.asn.au/dropbear/releases/ \
https://dropbear.nl/mirror/releases/
-PKG_MD5SUM:=6c1e6c2c297f4034488ffc95e8b7e6e9
+PKG_MD5SUM:=7066bb9a2da708f3ed06314fdc9c47fd
PKG_LICENSE:=MIT
PKG_LICENSE_FILES:=LICENSE libtomcrypt/LICENSE libtommath/LICENSE
PKG_BUILD_PARALLEL:=1
+PKG_CONFIG_DEPENDS:=CONFIG_DROPBEAR_ECC
+
include $(INCLUDE_DIR)/package.mk
define Package/dropbear/Default
URL:=http://matt.ucc.asn.au/dropbear/
endef
+define Package/dropbear/config
+ source $(SOURCE)/Config.in
+endef
+
define Package/dropbear
$(call Package/dropbear/Default)
SECTION:=net
@@ -72,6 +78,20 @@ CONFIGURE_ARGS += \
TARGET_CFLAGS += -DARGTYPE=3 -ffunction-sections -fdata-sections
TARGET_LDFLAGS += -Wl,--gc-sections
+define Build/Prepare
+ $(call Build/Prepare/Default)
+ # Enforce that all replacements are made, otherwise options.h has
changed
+ # format and this logic is broken.
+ for OPTION in DROPBEAR_ECDSA DROPBEAR_ECDH DROPBEAR_CURVE25519; do \
+ awk 'BEGIN { rc = 1 } \
+ /'OPTION'/ { 0 = $(if $(CONFIG_DROPBEAR_ECC),,//
)#define 'OPTION'; rc = 0 } \
+ { print } \
+ END { exit(rc) }' $(PKG_BUILD_DIR)/options.h \
+ $(PKG_BUILD_DIR)/options.h.new \
+ mv $(PKG_BUILD_DIR)/options.h.new $(PKG_BUILD_DIR)/options.h ||
exit 1; \
+ done
+endef
+
define Build/Compile
+$(MAKE) $(PKG_JOBS) -C $(PKG_BUILD_DIR) \
$(TARGET_CONFIGURE_OPTS) \
diff --git a/package/network/services/dropbear/patches/100-pubkey_path.patch
b/package/network/services/dropbear/patches/100-pubkey_path.patch
index c1802f5..456874b 100644
--- a/package/network/services/dropbear/patches/100-pubkey_path.patch
+++ b/package/network/services/dropbear/patches/100-pubkey_path.patch
@@ -1,6 +1,6 @@
--- a/svr-authpubkey.c
+++ b/svr-authpubkey.c
-@@ -209,17 +209,21 @@ static int checkpubkey(unsigned char* al
+@@ -208,17 +208,21 @@ static int checkpubkey(unsigned char* al
[OpenWrt-Devel] how enable the scp service ?
hello everyone I've encountered a error during use winscp for login to my router. it's seems scp service disbled. what's the name of scp service on OpenWRT ? BR Alan.Hoo,Code Monkey MSFT ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] how enable the scp service ?
PS, the winscp program login successfully but exit very soon. From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Alan.Hoo Sent: Thursday, March 13, 2014 2:43 PM To: 'OpenWrt Development List' Subject: [OpenWrt-Devel] how enable the scp service ? hello everyone I've encountered a error during use winscp for login to my router. it's seems scp service disbled. what's the name of scp service on OpenWRT ? BR Alan.Hoo,Code Monkey MSFT ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
These files are parsed by shell scripts or some thing else? I really can't figure it out. Please give me some idea about this. -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
Hello Wandy, the UCI guide on OpenWrt wiki describes how it does work. http://wiki.openwrt.org/doc/uci Kind regards, Jiri Slachta Dne 13. 3. 2014 9:11, Wandy Lau napsal(a): These files are parsed by shell scripts or some thing else? I really can't figure it out. Please give me some idea about this. -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config filesin /etc/config/* are parsed?
You can go to the directory /etc/init.d/, such /etc/init.d/network cant see the file /etc/config/network above is a good entrance for your doubt -- Original -- From: Jiří Šlachta;slac...@cesnet.cz; Date: Thu, Mar 13, 2014 04:18 PM To: OpenWrt Development Listopenwrt-devel@lists.openwrt.org; Subject: Re: [OpenWrt-Devel] I still can't figure out how the config filesin /etc/config/* are parsed? Hello Wandy, the UCI guide on OpenWrt wiki describes how it does work. http://wiki.openwrt.org/doc/uci Kind regards, Jiri Slachta Dne 13. 3. 2014 9:11, Wandy Lau napsal(a): These files are parsed by shell scripts or some thing else? I really can't figure it out. Please give me some idea about this. -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel .___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
Hi, On 13 March 2014 16:11, Wandy Lau xdragon...@gmail.com wrote: These files are parsed by shell scripts or some thing else? I really can't figure it out. Please give me some idea about this. UCI is really a pearl in OpenWrt. I was surprised by the design and implementation when trying to understand the details. Basically, identifiers like config, option are defined as shell functions, so uci config files can be evaled by the shell when they are parsed, kind of self interpretation. IIRC, you can find the details in /lib/functions.sh, /lib/config/uci.sh. There are a lot of eval statements there, so be warned. :) yousong ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
Hi, I really appreciate your kind help,guys. Thank you all. I wonder the process of uci configuration process is : LuCI makes changes into the /etc/config/*, then all the file in this directory will be parsed producing the configure file of other application such as hostapt, dropbear and so on. I have been looking for the parse process for a couple days. Actually, I want to do some changes, so I have to figure out this process. Thank you zhou for you reminds. Perhaps I miss some points when read the uci.sh and function.sh. Thank you. I will try again. On Thu, Mar 13, 2014 at 4:44 PM, Yousong Zhou yszhou4t...@gmail.com wrote: Hi, On 13 March 2014 16:11, Wandy Lau xdragon...@gmail.com wrote: These files are parsed by shell scripts or some thing else? I really can't figure it out. Please give me some idea about this. UCI is really a pearl in OpenWrt. I was surprised by the design and implementation when trying to understand the details. Basically, identifiers like config, option are defined as shell functions, so uci config files can be evaled by the shell when they are parsed, kind of self interpretation. IIRC, you can find the details in /lib/functions.sh, /lib/config/uci.sh. There are a lot of eval statements there, so be warned. :) yousong ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
Hello Wandy. Read this: http://wiki.openwrt.org/doc/devel/config-scripting and this: http://wiki.openwrt.org/doc/devel/network-scripting http://wiki.openwrt.org/doc/start#developing http://downloads.openwrt.org/docs/openwrt.html#x1-310001.3 Should give you a good starting point. On 13 March 2014 10:04, Wandy Lau xdragon...@gmail.com wrote: Hi, I really appreciate your kind help,guys. Thank you all. I wonder the process of uci configuration process is : LuCI makes changes into the /etc/config/*, then all the file in this directory will be parsed producing the configure file of other application such as hostapt, dropbear and so on. I have been looking for the parse process for a couple days. Actually, I want to do some changes, so I have to figure out this process. Thank you zhou for you reminds. Perhaps I miss some points when read the uci.sh and function.sh. Thank you. I will try again. On Thu, Mar 13, 2014 at 4:44 PM, Yousong Zhou yszhou4t...@gmail.comwrote: Hi, On 13 March 2014 16:11, Wandy Lau xdragon...@gmail.com wrote: These files are parsed by shell scripts or some thing else? I really can't figure it out. Please give me some idea about this. UCI is really a pearl in OpenWrt. I was surprised by the design and implementation when trying to understand the details. Basically, identifiers like config, option are defined as shell functions, so uci config files can be evaled by the shell when they are parsed, kind of self interpretation. IIRC, you can find the details in /lib/functions.sh, /lib/config/uci.sh. There are a lot of eval statements there, so be warned. :) yousong ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
Thank you for your kindness. I have read all these. But I think that is not enough. Some more work need to be done. I need dig deeper. Ok, let me tell something: Actually I want to know how the hostapd.conf is produced. Because there is one option that I am interested, channel. This option resides int the /etc/config/wireless. I just want to know how the channle in wireless is piped to hostapd.conf. And I want do some altercation about this option. At the beginning, I thought that the point was the hostapd.sh which resides in /lib/wifi/. But it still works after I deleted this file. mac80211.sh which also resides in the same directory initiates the system for the first time startup. Then I deleted the /sbin/wifi. But the translation from wireless to hostapd.conf still works. Then I found the problem maybe was in /etc/init.d/network. So I commented all the functions except the start_servive() , but everything still was good. Finally I commented the start_service and the pipe was cut off. The translation was down as well as the system. I know the point might be here. Something related to procd which is just a process management application. I am stuck here. I still can't figure how the channel translated from wireless to hostapd.conf is achieved. On Thu, Mar 13, 2014 at 6:08 PM, Damian Kaczkowski damian.kaczkowski+open...@gmail.com wrote: Hello Wandy. Read this: http://wiki.openwrt.org/doc/devel/config-scripting and this: http://wiki.openwrt.org/doc/devel/network-scripting http://wiki.openwrt.org/doc/start#developing http://downloads.openwrt.org/docs/openwrt.html#x1-310001.3 Should give you a good starting point. On 13 March 2014 10:04, Wandy Lau xdragon...@gmail.com wrote: Hi, I really appreciate your kind help,guys. Thank you all. I wonder the process of uci configuration process is : LuCI makes changes into the /etc/config/*, then all the file in this directory will be parsed producing the configure file of other application such as hostapt, dropbear and so on. I have been looking for the parse process for a couple days. Actually, I want to do some changes, so I have to figure out this process. Thank you zhou for you reminds. Perhaps I miss some points when read the uci.sh and function.sh. Thank you. I will try again. On Thu, Mar 13, 2014 at 4:44 PM, Yousong Zhou yszhou4t...@gmail.comwrote: Hi, On 13 March 2014 16:11, Wandy Lau xdragon...@gmail.com wrote: These files are parsed by shell scripts or some thing else? I really can't figure it out. Please give me some idea about this. UCI is really a pearl in OpenWrt. I was surprised by the design and implementation when trying to understand the details. Basically, identifiers like config, option are defined as shell functions, so uci config files can be evaled by the shell when they are parsed, kind of self interpretation. IIRC, you can find the details in /lib/functions.sh, /lib/config/uci.sh. There are a lot of eval statements there, so be warned. :) yousong ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
Hi, On 13 March 2014 18:46, Wandy Lau xdragon...@gmail.com wrote: Thank you for your kindness. I have read all these. But I think that is not enough. Some more work need to be done. I need dig deeper. Ok, let me tell something: Actually I want to know how the hostapd.conf is produced. Because there is one option that I am interested, channel. This option resides int the /etc/config/wireless. I just want to know how the channle in wireless is piped to hostapd.conf. And I want do some altercation about this option. At You can check netifd/wireless.c, /lib/netifd/wireless/mac80211.sh. Netifd will get needed information with ./mac80211.sh '' dump I am not familiar with netifd and wireless enough, but hope this will help you in some way. yousong the beginning, I thought that the point was the hostapd.sh which resides in /lib/wifi/. But it still works after I deleted this file. mac80211.sh which also resides in the same directory initiates the system for the first time startup. Then I deleted the /sbin/wifi. But the translation from wireless to hostapd.conf still works. Then I found the problem maybe was in /etc/init.d/network. So I commented all the functions except the start_servive() , but everything still was good. Finally I commented the start_service and the pipe was cut off. The translation was down as well as the system. I know the point might be here. Something related to procd which is just a process management application. I am stuck here. I still can't figure how the channel translated from wireless to hostapd.conf is achieved. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I still can't figure out how the config files in /etc/config/* are parsed?
Ok, Thank you so much for your time. I really appreciate it. I will try it. On Thu, Mar 13, 2014 at 7:23 PM, Yousong Zhou yszhou4t...@gmail.com wrote: Hi, On 13 March 2014 18:46, Wandy Lau xdragon...@gmail.com wrote: Thank you for your kindness. I have read all these. But I think that is not enough. Some more work need to be done. I need dig deeper. Ok, let me tell something: Actually I want to know how the hostapd.conf is produced. Because there is one option that I am interested, channel. This option resides int the /etc/config/wireless. I just want to know how the channle in wireless is piped to hostapd.conf. And I want do some altercation about this option. At You can check netifd/wireless.c, /lib/netifd/wireless/mac80211.sh. Netifd will get needed information with ./mac80211.sh '' dump I am not familiar with netifd and wireless enough, but hope this will help you in some way. yousong the beginning, I thought that the point was the hostapd.sh which resides in /lib/wifi/. But it still works after I deleted this file. mac80211.sh which also resides in the same directory initiates the system for the first time startup. Then I deleted the /sbin/wifi. But the translation from wireless to hostapd.conf still works. Then I found the problem maybe was in /etc/init.d/network. So I commented all the functions except the start_servive() , but everything still was good. Finally I commented the start_service and the pipe was cut off. The translation was down as well as the system. I know the point might be here. Something related to procd which is just a process management application. I am stuck here. I still can't figure how the channel translated from wireless to hostapd.conf is achieved. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- This is my life,but world of us~~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH RESEND] build image for TL-WDR4300v1 (IL)
The version of TL-WDR4300 sold in Israel comes with a different hardware id.
---
target/linux/ar71xx/base-files/lib/ar71xx.sh | 4
target/linux/ar71xx/image/Makefile | 3 ++-
tools/firmware-utils/src/mktplinkfw.c| 6 ++
3 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 06f128b..47c03bc 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -180,6 +180,10 @@ tplink_board_detect() {
43*)
model=TP-Link TL-WDR4300
;;
+ 430080*)
+ iw reg set IL
+ model=TP-Link TL-WDR4300 (IL)
+ ;;
431000*)
model=TP-Link TL-WDR4310
;;
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index b2b1706..472732e 100644
--- a/target/linux/ar71xx/image/Makefile
+++ b/target/linux/ar71xx/image/Makefile
@@ -1050,6 +1050,7 @@ $(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,TLWR2543,tl-wr2543-v1,TL-WR2543N,
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,TLWDR3500V1,tl-wdr3500-v1,TL-WDR3500,ttyS0,115200,0x3501,1,8Mlzma))
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,TLWDR3600V1,tl-wdr3600-v1,TL-WDR4300,ttyS0,115200,0x3601,1,8Mlzma))
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,TLWDR4300V1,tl-wdr4300-v1,TL-WDR4300,ttyS0,115200,0x4301,1,8Mlzma))
+$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,TLWDR4300V1IL,tl-wdr4300-v1-il,TL-WDR4300,ttyS0,115200,0x43008001,1,8Mlzma))
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,TLWDR4310V1,tl-wdr4310-v1,TL-WDR4300,ttyS0,115200,0x4311,1,8Mlzma))
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,TLWDR4900V2,tl-wdr4900-v2,TL-WDR4900-v2,ttyS0,115200,0x4902,1,8Mlzma))
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,MW4530RV1,mw4530r-v1,TL-WDR4300,ttyS0,115200,0x4531,1,8Mlzma))
@@ -1109,7 +1110,7 @@ $(eval $(call MultiProfile,TLWR841,TLWR841NV15 TLWR841NV3
TLWR841NV5 TLWR841NV7
$(eval $(call MultiProfile,TLWR842,TLWR842V1 TLWR842V2))
$(eval $(call MultiProfile,TLWR941,TLWR941NV2 TLWR941NV3 TLWR941NV4
TLWR941NV6))
$(eval $(call MultiProfile,TLWR1043,TLWR1043V1 TLWR1043V2))
-$(eval $(call MultiProfile,TLWDR4300,TLWDR3500V1 TLWDR3600V1 TLWDR4300V1
TLWDR4310V1 MW4530RV1))
+$(eval $(call MultiProfile,TLWDR4300,TLWDR3500V1 TLWDR3600V1 TLWDR4300V1
TLWDR4300V1IL TLWDR4310V1 MW4530RV1))
$(eval $(call MultiProfile,UBNT,UBNTAIRROUTER UBNTRS UBNTRSPRO UBNTLSSR71
UBNTBULLETM UBNTROCKETM UBNTNANOM UBNTUNIFI UBNTUNIFIOUTDOOR UAPPRO))
$(eval $(call MultiProfile,WNDR3700,WNDR3700V1 WNDR3700V2 WNDR3800 WNDRMAC
WNDRMACV2))
$(eval $(call MultiProfile,WNR612V2,REALWNR612V2 N150R))
diff --git a/tools/firmware-utils/src/mktplinkfw.c
b/tools/firmware-utils/src/mktplinkfw.c
index d15ca5b..a5e7d20 100644
--- a/tools/firmware-utils/src/mktplinkfw.c
+++ b/tools/firmware-utils/src/mktplinkfw.c
@@ -45,6 +45,7 @@
#define HWID_TL_WA801ND_V2 0x08010002
#define HWID_TL_WA901ND_V1 0x09010001
#define HWID_TL_WA901ND_V2 0x09010002
+#define HWID_TL_WDR4300_V1_IL 0x43008001
#define HWID_TL_WDR4900_V1 0x4901
#define HWID_TL_WR703N_V1 0x07030101
#define HWID_TL_WR720N_V3 0x07200103
@@ -274,6 +275,11 @@ static struct board_info boards[] = {
.hw_rev = 1,
.layout_id = 4M,
}, {
+ .id = TL-WDR4300v1,
+ .hw_id = HWID_TL_WDR4300_V1_IL,
+ .hw_rev = 1,
+ .layout_id = 8Mlzma,
+ }, {
.id = TL-WDR4900v1,
.hw_id = HWID_TL_WDR4900_V1,
.hw_rev = 1,
--
1.9.0
pgpeOfb7mkwTG.pgp
Description: PGP signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel/modules: package Hebrew charsets
--- package/kernel/linux/modules/nls.mk | 32 1 file changed, 32 insertions(+) diff --git a/package/kernel/linux/modules/nls.mk b/package/kernel/linux/modules/nls.mk index f1fa0fa..daef8b0 100644 --- a/package/kernel/linux/modules/nls.mk +++ b/package/kernel/linux/modules/nls.mk @@ -83,6 +83,22 @@ endef $(eval $(call KernelPackage,nls-cp852)) +define KernelPackage/nls-cp862 + SUBMENU:=Native Language Support + TITLE:=Codepage 862 (Hebrew) + KCONFIG:=CONFIG_NLS_CODEPAGE_862 + FILES:=$(LINUX_DIR)/fs/nls/nls_cp862.ko + AUTOLOAD:=$(call AutoLoad,25,nls_cp862) + $(call AddDepends/nls) +endef + +define KernelPackage/nls-cp862/description + Kernel module for NLS Codepage 862 (Hebrew) +endef + +$(eval $(call KernelPackage,nls-cp862)) + + define KernelPackage/nls-cp866 SUBMENU:=Native Language Support TITLE:=Codepage 866 (Cyrillic) @@ -163,6 +179,22 @@ endef $(eval $(call KernelPackage,nls-iso8859-2)) +define KernelPackage/nls-iso8859-8 + SUBMENU:=Native Language Support + TITLE:=ISO 8859-8, CP1255 (Hebrew) + KCONFIG:=CONFIG_NLS_ISO8859_8 + FILES:=$(LINUX_DIR)/fs/nls/nls_cp1255.ko + AUTOLOAD:=$(call AutoLoad,25,nls_cp1255) + $(call AddDepends/nls) +endef + +define KernelPackage/nls-iso8859-8/description + Kernel module for Hebrew charsets (ISO-8859-8, CP1255) +endef + +$(eval $(call KernelPackage,nls-iso8859-8)) + + define KernelPackage/nls-iso8859-13 SUBMENU:=Native Language Support TITLE:=ISO 8859-13 (Latin 7; Baltic) -- 1.9.0 pgpS6DNTYe8la.pgp Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel/modules: package Arabic charsets
--- package/kernel/linux/modules/nls.mk | 32 1 file changed, 32 insertions(+) diff --git a/package/kernel/linux/modules/nls.mk b/package/kernel/linux/modules/nls.mk index daef8b0..224fd03 100644 --- a/package/kernel/linux/modules/nls.mk +++ b/package/kernel/linux/modules/nls.mk @@ -99,6 +99,22 @@ endef $(eval $(call KernelPackage,nls-cp862)) +define KernelPackage/nls-cp864 + SUBMENU:=Native Language Support + TITLE:=Codepage 864 (Arabic) + KCONFIG:=CONFIG_NLS_CODEPAGE_864 + FILES:=$(LINUX_DIR)/fs/nls/nls_cp864.ko + AUTOLOAD:=$(call AutoLoad,25,nls_cp864) + $(call AddDepends/nls) +endef + +define KernelPackage/nls-cp864/description + Kernel module for NLS Codepage 864 (Arabic) +endef + +$(eval $(call KernelPackage,nls-cp864)) + + define KernelPackage/nls-cp866 SUBMENU:=Native Language Support TITLE:=Codepage 866 (Cyrillic) @@ -179,6 +195,22 @@ endef $(eval $(call KernelPackage,nls-iso8859-2)) +define KernelPackage/nls-iso8859-6 + SUBMENU:=Native Language Support + TITLE:=ISO 8859-6 (Arabic) + KCONFIG:=CONFIG_NLS_ISO8859_6 + FILES:=$(LINUX_DIR)/fs/nls/nls_iso8859-6.ko + AUTOLOAD:=$(call AutoLoad,25,nls_iso8859-6) + $(call AddDepends/nls) +endef + +define KernelPackage/nls-iso8859-6/description + Kernel module for NLS ISO 8859-6 (Arabic) +endef + +$(eval $(call KernelPackage,nls-iso8859-6)) + + define KernelPackage/nls-iso8859-8 SUBMENU:=Native Language Support TITLE:=ISO 8859-8, CP1255 (Hebrew) -- 1.9.0 pgp78D0ky2g0C.pgp Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] how enable the scp service ?
From my Mac, "scp -v myfile host:/tmp/target" (-v for verbose) appears to run "ssh host scp -v -t /tmp/target". On my AA 12.01: # which scp /usr/bin/scp # opkg search /usr/bin/scp dropbear - 2011.54-2 Does "ssh target" work? Can you run verbose mode (ie: "scp -v myfile host:/tmp/target")? Can you scp to other machines (insuring that your winscp is working)? On 3/13/14, 2:48 AM, Alan.Hoo wrote: PS, the winscp program login successfully but exit very soon. From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Alan.Hoo Sent: Thursday, March 13, 2014 2:43 PM To: 'OpenWrt Development List' Subject: [OpenWrt-Devel] how enable the scp service ? hello everyone I've encountered a error during use winscp for login to my router. it's seems scp service disbled. what's the name of scp service on OpenWRT ? BR Alan.Hoo,Code Monkey MSFT ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- -Justin justinval...@gmail.com smime.p7s Description: S/MIME Cryptographic Signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] how enable the scp service ?
Hi Alan, * Alan.Hoo (huqings...@ycmedia.cn) wrote: I've encountered a error during use winscp for login to my router. it's seems scp service disbled. what's the name of scp service on OpenWRT ? PS, the winscp program login successfully but exit very soon. dropbear supports SCP but not SFTP. I would guess WinSCP is trying to use SFTP since it'll do just that--die shortly after logging in. SCP works fine out of the box for me. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dropbear: update to 2014.63
On 03/13/2014 03:15 AM, Catalin Patulea wrote:
ping??
+1
2014.63 also fixes the brown-paper-bag bug that prevented from doing ssh
to link-local addresses, since the '%' operator had been (incorrectly)
reassigned.
On Sat, Mar 1, 2014 at 4:05 AM, Catalin Patulea c...@vv.carleton.ca wrote:
ping
On Mon, Feb 24, 2014 at 1:02 AM, Catalin Patulea c...@vv.carleton.ca wrote:
Upstream changelog:
https://matt.ucc.asn.au/dropbear/CHANGES
This adds elliptic curve cryptography (ECC) support as an option, disabled
by default.
dropbear mips 34kc uClibc binary size:
before: 161,672 bytes
after, without ECC (default): 164,968
after, with ECC: 198,008
Signed-off-by: Catalin Patulea c...@vv.carleton.ca
---
package/network/services/dropbear/Config.in| 27 ++
package/network/services/dropbear/Makefile | 24 ++--
.../dropbear/patches/100-pubkey_path.patch |4 +--
.../dropbear/patches/110-change_user.patch |2 +-
.../dropbear/patches/120-openwrt_options.patch | 21 --
.../dropbear/patches/140-disable_assert.patch |2 +-
.../patches/150-dbconvert_standalone.patch |6 ++--
.../dropbear/patches/200-lcrypt_bsdfix.patch | 29
.../dropbear/patches/500-set-default-path.patch|2 +-
9 files changed, 63 insertions(+), 54 deletions(-)
create mode 100644 package/network/services/dropbear/Config.in
delete mode 100644
package/network/services/dropbear/patches/200-lcrypt_bsdfix.patch
diff --git a/package/network/services/dropbear/Config.in
b/package/network/services/dropbear/Config.in
new file mode 100644
index 000..e2a7610
--- /dev/null
+++ b/package/network/services/dropbear/Config.in
@@ -0,0 +1,27 @@
+menu Configuration
+ depends on PACKAGE_dropbear
+
+config DROPBEAR_ECC
+ bool Elliptic curve cryptography (ECC)
+ default n
+ help
+ Enables elliptic curve cryptography (ECC) support in key
exchange and public key
+ authentication.
+
+ Key exchange algorithms:
+ ecdh-sha2-nistp256
+ ecdh-sha2-nistp384
+ ecdh-sha2-nistp521
+ curve25519-sha...@libssh.org
+
+ Public key algorithms:
+ ecdsa-sha2-nistp256
+ ecdsa-sha2-nistp384
+ ecdsa-sha2-nistp521
+
+ Does not generate ECC host keys by default (ECC key exchange
will not be used,
+ only ECC public key auth).
+
+ Increases binary size by about 36 kB (MIPS).
+
+endmenu
diff --git a/package/network/services/dropbear/Makefile
b/package/network/services/dropbear/Makefile
index 02be761..692199e 100644
--- a/package/network/services/dropbear/Makefile
+++ b/package/network/services/dropbear/Makefile
@@ -8,26 +8,32 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=dropbear
-PKG_VERSION:=2013.59
+PKG_VERSION:=2014.63
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:= \
http://matt.ucc.asn.au/dropbear/releases/ \
https://dropbear.nl/mirror/releases/
-PKG_MD5SUM:=6c1e6c2c297f4034488ffc95e8b7e6e9
+PKG_MD5SUM:=7066bb9a2da708f3ed06314fdc9c47fd
PKG_LICENSE:=MIT
PKG_LICENSE_FILES:=LICENSE libtomcrypt/LICENSE libtommath/LICENSE
PKG_BUILD_PARALLEL:=1
+PKG_CONFIG_DEPENDS:=CONFIG_DROPBEAR_ECC
+
include $(INCLUDE_DIR)/package.mk
define Package/dropbear/Default
URL:=http://matt.ucc.asn.au/dropbear/
endef
+define Package/dropbear/config
+ source $(SOURCE)/Config.in
+endef
+
define Package/dropbear
$(call Package/dropbear/Default)
SECTION:=net
@@ -72,6 +78,20 @@ CONFIGURE_ARGS += \
TARGET_CFLAGS += -DARGTYPE=3 -ffunction-sections -fdata-sections
TARGET_LDFLAGS += -Wl,--gc-sections
+define Build/Prepare
+ $(call Build/Prepare/Default)
+ # Enforce that all replacements are made, otherwise options.h has
changed
+ # format and this logic is broken.
+ for OPTION in DROPBEAR_ECDSA DROPBEAR_ECDH DROPBEAR_CURVE25519; do \
+ awk 'BEGIN { rc = 1 } \
+ /'OPTION'/ { 0 = $(if $(CONFIG_DROPBEAR_ECC),,// )#define
'OPTION'; rc = 0 } \
+ { print } \
+ END { exit(rc) }' $(PKG_BUILD_DIR)/options.h \
+ $(PKG_BUILD_DIR)/options.h.new \
+ mv $(PKG_BUILD_DIR)/options.h.new $(PKG_BUILD_DIR)/options.h || exit
1; \
+ done
+endef
+
define Build/Compile
+$(MAKE) $(PKG_JOBS) -C $(PKG_BUILD_DIR) \
$(TARGET_CONFIGURE_OPTS) \
diff --git a/package/network/services/dropbear/patches/100-pubkey_path.patch
b/package/network/services/dropbear/patches/100-pubkey_path.patch
index c1802f5..456874b 100644
--- a/package/network/services/dropbear/patches/100-pubkey_path.patch
+++ b/package/network/services/dropbear/patches/100-pubkey_path.patch
@@ -1,6 +1,6 @@
--- a/svr-authpubkey.c
+++ b/svr-authpubkey.c
-@@ -209,17
