View Single Post
Old 06-29-2013, 09:41 PM   #12
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@knc1: Heh, funny story: that's not dropbear's default behavior, the default settings are patched to print the Kindle's /etc/issue in my USBNetwork build... *inserts evil laugh here*. IIRC, there's a switch to disable it altogether. I can easily add it as a configurable option in the next release .

EDIT: ... Which is exactly what you used in the patch linked in your thread, oops. .

(Kind of forgot about it to tell the truth, I switched to OpenSSH on nearly all my devices, the dropbear/libtom regression on ARM that kills the performance of the auth kinda got on my nerve... ^^).

EDITē: Done. Look for the QUIET_DROPBEAR config flag in the next release (defaults unchanged).

Last edited by NiLuJe; 06-30-2013 at 09:57 PM.
NiLuJe is offline   Reply With Quote