Re: Login attempt for nonexistent user

Hi Matt, Yes you are right, with strace i see missing files : 03   open("/usr/lib/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) 103   stat64("/usr/lib", {st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0 103   open("/lib/libnss_files.so.2", O_RDONLY|O_CLOEXEC) =

Re: Login attempt for nonexistent user

Hi Laurent, My best guess is that it was built on lubuntu which uses glibc, but the Udoo board doesn't have the required /lib/somewhere/libnss*.so libraries - those get chosen at runtime based on /etc/nsswitch.conf. Building using a uclibc cross compiler would avoid that - how did you build

Login attempt for nonexistent user

with correct subject : Hi, I fail to login with ssh client to dropbox I use Udoo ARM board with busybox to install ssh server I cross compiled dropbear under VirtualBox lubuntu and install binary to board ( /bin & /sbin) I generate RSA key (ssh-keygen -t rsa ) under lubuntu and copied 

Re: Login attempt for nonexistent user on Alpine Linux

* Hugo Genesse [2017-12-01 18:57:02 +]: > > -vvv on dropbear doesn't seem to be a valid option: > > 67b4c38f79c6:/usr/lib# /root/dropbear -R -E -vvv > Invalid option -v > > Is my command correct? > ah -v is only supported if dropbear is built with

Re: Login attempt for nonexistent user on Alpine Linux

key,password). and in the dropbear logs I still get: [67] Dec 01 17:03:47 Child connection from :40878 [67] Dec 01 17:03:47 Login attempt for nonexistent user from [...] make it more verbose, you will see what part of the user lookup fails. I saw that I could create a configuration file in /etc/dropbear t

Re: Login attempt for nonexistent user on Alpine Linux

* Matt Johnston [2017-12-01 16:53:33 +]: > Statically linking glibc isn't sufficient to make it's not glibc if it's on alpine linux

Re: Login attempt for nonexistent user on Alpine Linux

not > > > > mistaken). I run dropbear like this: "./dropbear -R" and can't login > > > > with > > > > proper credentials. With the "-E" switch I get the following: > > > > > > > > /root/dropbear -R -E > > > &g

Re: Login attempt for nonexistent user on Alpine Linux

:03:47 Child connection from :40878 [67] Dec 01 17:03:47 Login attempt for nonexistent user from [...] I saw that I could create a configuration file in /etc/dropbear to allow root logins by it seems to be enabled by default and I would prefer just drop a binary on the device to enable ssh

Re: Login attempt for nonexistent user on Alpine Linux

ith the "-E" switch I get the following: > > > > /root/dropbear -R -E > > [59] Dec 01 04:31:32 Running in background > > [60] Dec 01 04:31:36 Child connection from > > [60] Dec 01 04:31:36 Login attempt for nonexistent user from > > > > i

Re: Login attempt for nonexistent user on Alpine Linux

; mistaken). I run dropbear like this: "./dropbear -R" and can't login with > proper credentials. With the "-E" switch I get the following: > > /root/dropbear -R -E > [59] Dec 01 04:31:32 Running in background > [60] Dec 01 04:31:36 Child connection from >

Login attempt for nonexistent user on Alpine Linux

an't login with proper credentials. With the "-E" switch I get the following: /root/dropbear -R -E [59] Dec 01 04:31:32 Running in background [60] Dec 01 04:31:36 Child connection from [60] Dec 01 04:31:36 Login attempt for nonexistent user from My credentials are right and the command to con

RE: Login attempt for nonexistent user

Dropbear starts up fine with dropbear -E. But when I try to log in, dropbear complains: Login attempt for nonexistent user from 192.168.211.1:3186 Ok, I found the solution myself. Basically, libnsl is needed as well, in addition to libnss. Just in case anyone else stumbles over the same