busybox: add option for standalone telnetd on target

PATCH Superseded Alexey Brodkin 1 participant 2 messages Mar 12, 2015 – Apr 21, 2015

Share & tools

Alexey Brodkin

author

2015-03-12 09:31 UTC #0 lore raw

PATCH v2 1/1 busybox: add option for standalone telnetd on target

If target has connection to the network it might be pretty useful to have telnet connection to it instead of serial console or even in addition to serial console.

Even though it's possible to add telnetd on target manually via:
[a] Busybox - with "make busybox-menuconfig" and in "Networking
Utilities" select "telnetd"
[b] xinetd

Still additional manual steps will be required to allow root login over telnet and telnet daemon auto-start on boot.

With this change it will be possible to get telnetd built and installed on target with only enabling BR2_SYSTEM_STANDALONE_TELNETD option in Buildroot configuration utility or in boards defconfig.

Signed-off-by Alexey Brodkin <[email protected]>

Cc Peter Korsgaard <[email protected]>

Cc "Yann E. MORIN" <[email protected]>

Cc Thomas Petazzoni <[email protected]>

---

Changes in v2:
* STANDALONE_TELNETD option moved from "system" to Busybox package
* Added auto-start script for telnet daemon
* Added warning in Kconfig about possible Telnet security issues with mention of SSH to be used instead on production systems

---
 package/busybox/Config.in  | 22 ++++++++++++++++++++++
 package/busybox/S50telnet  | 20 ++++++++++++++++++++
 package/busybox/busybox.mk | 14 ++++++++++++++
 system/system.mk           | 17 +++++++++++++++++
 4 files changed, 73 insertions(+)
 create mode 100755 package/busybox/S50telnet

package/busybox/Config.in +22 -0

index f2f2990..e9d4a3f 100644
@@ -45,6 +45,28 @@ config BR2_PACKAGE_BUSYBOX_WATCHDOG_PERIOD
 
 endif
 
+config BR2_PACKAGE_BUSYBOX_STANDALONE_TELNETD
+	bool "Enable telnet daemon on target"
+	depends on !BR2_PACKAGE_XINETD
+	default n
+	help
+	  By default user may interact with target via serial port if set in
+	  kernel's command line with "console" option or as a GENERIC_GETTY here
+	  in Buildroot.
+
+	  Another useful option if target is connected to the network is telnet.
+
+	  For it to work telnet daemon (telnetd) must be installed and
+	  auto-started on target during boot process.
+
+	  Say yes here if you would like to have an ability to telnet on target.
+	  If unsure, say N.
+
+	  WARNING! WARNING!
+	  Telnet connection (especially if there're users with no password)
+	  might be not safe, so on production systems please consider usage of
+	  SSH (provided by Dropbear or OpenSSH packages).
+
 endif
 
 if !BR2_PACKAGE_BUSYBOX # kconfig doesn't support else

package/busybox/S50telnet new file +20 -0

new file mode 100755
index 0000000..8888e17
@@ -0,0 +1,20 @@
+#!/bin/sh
+#
+# Start telnet....
+#
+
+case "$1" in
+  start)
+	echo "Starting telnet..."
+	/usr/sbin/telnetd
+	;;
+  stop)
+	;;
+  restart|reload)
+	;;
+  *)
+	echo "Usage: $0 {start|stop|restart}"
+	exit 1
+esac
+
+exit $?

package/busybox/busybox.mk +14 -0

index 61f6a16..d80052e 100644
@@ -180,6 +180,18 @@ define BUSYBOX_INSTALL_WATCHDOG_SCRIPT
 endef
 endif
 
+ifeq ($(BR2_PACKAGE_BUSYBOX_STANDALONE_TELNETD),y)
+define BUSYBOX_SET_STANDALONE_TELNETD
+	$(call KCONFIG_ENABLE_OPT,CONFIG_TELNETD,$(BUSYBOX_BUILD_CONFIG))
+	$(call KCONFIG_ENABLE_OPT,CONFIG_FEATURE_TELNETD_STANDALONE,$(BUSYBOX_BUILD_CONFIG))
+	$(call KCONFIG_ENABLE_OPT,CONFIG_FEATURE_TELNETD_INETD_WAIT,$(BUSYBOX_BUILD_CONFIG))
+endef
+define BUSYBOX_INSTALL_TELNET_SCRIPT
+	$(INSTALL) -m 0755 -D package/busybox/S50telnet \
+		$(TARGET_DIR)/etc/init.d/S50telnet;
+endef
+endif
+
 # Enable "noclobber" in install.sh, to prevent BusyBox from overwriting any
 # full-blown versions of apps installed by other packages with sym/hard links.
 define BUSYBOX_NOCLOBBER_INSTALL

@@ -198,6 +210,7 @@ define BUSYBOX_KCONFIG_FIXUP_CMDS
 	$(BUSYBOX_INTERNAL_SHADOW_PASSWORDS)
 	$(BUSYBOX_SET_INIT)
 	$(BUSYBOX_SET_WATCHDOG)
+	$(BUSYBOX_SET_STANDALONE_TELNETD)
 endef
 
 define BUSYBOX_CONFIGURE_CMDS

@@ -221,6 +234,7 @@ define BUSYBOX_INSTALL_INIT_SYSV
 	$(BUSYBOX_INSTALL_MDEV_SCRIPT)
 	$(BUSYBOX_INSTALL_LOGGING_SCRIPT)
 	$(BUSYBOX_INSTALL_WATCHDOG_SCRIPT)
+	$(BUSYBOX_INSTALL_TELNET_SCRIPT)
 endef
 
 $(eval $(kconfig-package))

system/system.mk +17 -0

index 4a1eb4a..7066d1f 100644
@@ -16,6 +16,23 @@ endef
 TARGET_FINALIZE_HOOKS += SYSTEM_SECURETTY
 endif
 
+ifeq ($(BR2_PACKAGE_BUSYBOX_STANDALONE_TELNETD),y)
+define SYSTEM_SECURETTY_PTS
+	grep -q 'pts/0' $(TARGET_DIR)/etc/securetty || \
+		echo 'pts/0' >> $(TARGET_DIR)/etc/securetty
+
+	grep -q 'pts/1' $(TARGET_DIR)/etc/securetty || \
+		echo 'pts/1' >> $(TARGET_DIR)/etc/securetty
+
+	grep -q 'pts/2' $(TARGET_DIR)/etc/securetty || \
+		echo 'pts/2' >> $(TARGET_DIR)/etc/securetty
+
+	grep -q 'pts/3' $(TARGET_DIR)/etc/securetty || \
+		echo 'pts/3' >> $(TARGET_DIR)/etc/securetty
+endef
+TARGET_FINALIZE_HOOKS += SYSTEM_SECURETTY_PTS
+endif
+
 ifneq ($(TARGET_GENERIC_HOSTNAME),)
 define SYSTEM_HOSTNAME
 	mkdir -p $(TARGET_DIR)/etc

Signature · 1 line

2.1.0

Alexey Brodkin

author

2015-04-21 13:38 UTC #1 lore raw

PATCH v2 1/1 busybox: add option for standalone telnetd on target

Hi Peter,

Quoted 28 lines · Alexey Brodkin

If target has connection to the network it might be pretty useful to have telnet connection to it instead of serial console or even in addition to serial console.
Even though it's possible to add telnetd on target manually via:
[a] Busybox - with "make busybox-menuconfig" and in "Networking
Utilities" select "telnetd"
[b] xinetd
Still additional manual steps will be required to allow root login over telnet and telnet daemon auto-start on boot.
With this change it will be possible to get telnetd built and installed on target with only enabling BR2_SYSTEM_STANDALONE_TELNETD option in Buildroot configuration utility or in boards defconfig.
Signed-off-by Alexey Brodkin <[email protected]>
Cc Peter Korsgaard <[email protected]>
Cc "Yann E. MORIN" <[email protected]>
Cc Thomas Petazzoni <[email protected]>
---
Changes in v2:
* STANDALONE_TELNETD option moved from "system" to Busybox package
* Added auto-start script for telnet daemon
* Added warning in Kconfig about possible Telnet security issues with mention of SSH to be used instead on production systems

Quoted 7 lines

---
 package/busybox/Config.in  | 22 ++++++++++++++++++++++
 package/busybox/S50telnet  | 20 ++++++++++++++++++++
 package/busybox/busybox.mk | 14 ++++++++++++++
 system/system.mk           | 17 +++++++++++++++++
 4 files changed, 73 insertions(+)
 create mode 100755 package/busybox/S50telnet

I've got a reminder about my pending Buildroot patches and that one is one of them.

I'm still interested in this one and would like at least to discuss if that updated version suits Buildroot or as we discussed in v1 comments it's a no go in favor to ssh for debugging over network.

-Alexey