Skip to contentSkip to conversation

Allow build of dropbear without wtmp and lastlog support to stop it from generating system log error messages

PATCH New Will Moore 2 participants 2 messages Oct 25, 2011 – Oct 26, 2011

lore
Share & tools
lore

Will Moore

author
#0 lore raw

PATCH 1/1 Allow build of dropbear without wtmp and lastlog support to stop it from generating system log error messages

Buildroot does not have wtmp or lastlog support by default so allow dropbear to be configured to stop using them and hence to stop generating system log error messages.

It seems I had problems with git send-email sending direct to the list (the patch failed to appear within a day) so I have forwarded the copy it cc'ed to myself to the list...

---
 package/dropbear/Config.in   |   16 ++++++++++++++++
 package/dropbear/dropbear.mk |    8 ++++++++
 2 files changed, 24 insertions(+), 0 deletions(-)
package/dropbear/Config.in +6 -0
index c30228f..58fed4a 100644
@@ -23,3 +23,19 @@ config BR2_PACKAGE_DROPBEAR_SMALL
 
 	  Tradeoffs are slower hashes and ciphers, and disabling of the
 	  blowfish cipher and zlib.
+
+config BR2_PACKAGE_DROPBEAR_DISABLE_WTMP
+	bool "disable logging of dropbear access to wtmp"
+	depends on BR2_PACKAGE_DROPBEAR
+	help
+	  Disable logging of dropbear access to wtmp. Buildroot does not

generate
+ wtmp by default and so by disabling dropbear's use of wtmp this
+ prevents warnings in the system log.
+
+config BR2_PACKAGE_DROPBEAR_DISABLE_LASTLOG
+ bool "disable logging of dropbear access to lastlog"
+ depends on BR2_PACKAGE_DROPBEAR
+ help

+	  Disable logging of dropbear access to lastlog. Buildroot does not
+	  generate lastlog by default and so by disabling dropbear's use of
+	  lastlog this prevents warnings in the system log.
package/dropbear/dropbear.mk +8 -0
index e9da42d..0c9c5fc 100644
@@ -46,6 +46,14 @@ DROPBEAR_POST_EXTRACT_HOOKS += DROPBEAR_BUILD_FEATURED
 DROPBEAR_DEPENDENCIES += zlib
 endif
 
+ifeq ($(BR2_PACKAGE_DROPBEAR_DISABLE_WTMP),y)
+DROPBEAR_CONF_OPT += --disable-wtmp
+endif
+
+ifeq ($(BR2_PACKAGE_DROPBEAR_DISABLE_LASTLOG),y)
+DROPBEAR_CONF_OPT += --disable-lastlog
+endif
+
 define DROPBEAR_INSTALL_TARGET_CMDS
 	$(INSTALL) -m 755 $(@D)/dropbearmulti $(TARGET_DIR)/usr/sbin/dropbear
 	for f in $(DROPBEAR_TARGET_BINS); do \
Signature · 1 line
1.7.0.4
#1 lore raw

PATCH 1/1 Allow build of dropbear without wtmp and lastlog support to stop it from generating system log error messages

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Will" == Will Moore <[email protected]> writes:

Will> Buildroot does not have wtmp or lastlog support by default so Will> allow dropbear to be configured to stop using them and hence to Will> stop generating system log error messages.

Committed, thanks - I prefer positive options (E.G. to enable wtmp/lastlog logging - And I disable them by default as that's what most people would want).

Will> It seems I had problems with git send-email sending direct to the Will> list (the patch failed to appear within a day) so I have Will> forwarded the copy it cc'ed to myself to the list...

Please keep these comment after the '---' line, otherwise it gets included in the commit message.

Signature · 1 line
Bye, Peter Korsgaard