summaryrefslogtreecommitdiff
path: root/cli-runopts.c
diff options
context:
space:
mode:
authoriquaba <cooka2011@gmail.com>2014-08-06 08:48:43 -0500
committeriquaba <cooka2011@gmail.com>2014-08-06 08:48:43 -0500
commit1e0bbc558176b8406f37fbafb11ab1b069b25ed0 (patch)
tree2019da9c8dd35645065176d05c2a379abbbc0fc5 /cli-runopts.c
parent45cd2fc537a7d90a9a2051e90bdafc4a3ed2e1d1 (diff)
downloaddropbear-1e0bbc558176b8406f37fbafb11ab1b069b25ed0.tar.gz
Try without identifying current user
Small change that warns the user if the current user cannot be identified rather than aborting. This came in handy when I put dropbear on a dlink that did not have a true user environment. Falling back on the "-l" option and user@ options works just fine as a client. The only implication I found is that the -J option will fail ungracefully without a known own_user.
Diffstat (limited to 'cli-runopts.c')
-rw-r--r--cli-runopts.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/cli-runopts.c b/cli-runopts.c
index 5f36f7c..8c9bc8e 100644
--- a/cli-runopts.c
+++ b/cli-runopts.c
@@ -684,7 +684,7 @@ static void fill_own_user() {
pw = getpwuid(uid);
if (pw == NULL || pw->pw_name == NULL) {
- dropbear_exit("Unknown own user");
+ dropbear_log(LOG_INFO, "Warning: failed to identify current user. Trying anyway.");
}
cli_opts.own_user = m_strdup(pw->pw_name);