Re: Dropbear 2015.70 fixes password authentication

Matt Johnston: Dropbear 2015.70 released now fixes password server authentication on Linux. This version does indeed fix the issue I was seeing. Thank you for the swift bug fix! -- \\// Peter - http://www.softwolves.pp.se/

2015.69 and password authentication

Hi! Upgrading from 2015.68 to 2015.69 on the embedded platform at $DAYJOB, password authentication does no longer work. This seems to be related to a newly added test for crypt() in the configure script, which fails to find it and thus disables password authentication. Has anyone else been

Port forwarding for certain users only

Hi! Is there a way to restrict port forwarding to certain users only? On an embedded device, I have a user that opens a settings menu when logging in (with username + password), and I do not wish that user to allow port forwarding. The UID for the login is 0 because it needs to be able to

Re: [PATCH] dropbear: support out-of-tree builds

Hi! Thank you for the patch. I think this should be solved in the hg tree but it didn't make it into the 2016.74 release. It does indeed. I didn't notice it when looking through the revision history. Sorry for the duplicate. -- \\// Peter - http://www.softwolves.pp.se/

[SUSPECTED SPAM]Re: Dropbear 2018.76

Matt Johnston: This should be fixed in https://secure.ucc.asn.au/hg/dropbear/rev/0dc3103a5900 This patch does indeed fix the problem. Thank you! -- \\// Peter - http://www.softwolves.pp.se/

Re: Dropbear 2018.76

Matt Johnston: Yes it should. I can't immediately reproduce it here, what flags are you giving to Dropbear? Is /mnt/nv/dropbear_ecdsa_host_key specified with -r or as a default config path, and are there other keyfiles? The daemon is started with "dropbear -R", and the keyfiles are specified

Re: Strange behaviour surrounding "ssh -T ..." and non-zero exit

2018-11-09 17:52 skrev W. Michael Petullo: Here is a more practical example which demonstrates the problem: $ echo false | dbclient -T r...@host.example.com $ echo $? 0 That is because $? contains the exit status of the left-most command (echo), not the pipe. If you are using a bash shell,

Re: Strange behaviour surrounding "ssh -T ..." and non-zero exit

2018-11-10 12:53 skrev W. Michael Petullo: I read the reference you provided, but I am not yet convinced. Is it not true that pipelines by default produce the exit code from the right-most program in the pipeline? You're right and I am wrong. The exit code is the right-most command. Sorry

[PATCH] Fix compile when disabling SHA-1

Fixes compile when disabling SHA-1 with #define DROPBEAR_SHA1_HMAC 0 #define DROPBEAR_RSA_SHA1 0 #define DROPBEAR_DH_GROUP14_SHA1 0 while keeping SHA-256 enabled. Should also fix the opposite, but that is not a recommended configuration. --- src/svr-runopts.c | 4 diff --git