Dropbear SSH closing connection when attempting to connect as a non Root User

Having issues with your DietPi installation or found a bug? Post it here.
djcjf
Posts: 11
Joined: Thu Jun 03, 2021 8:04 am

Re: Dropbear SSH closing connection when attempting to connect as a non Root User

Post by djcjf »

Joulinar wrote: Sat Jun 05, 2021 10:57 pm hmm I'm not able to replicate your behaviour. I created a simple demo user using adduser, and was able to login via SSH right after.

Code: Select all

root@DietPi3:~# adduser demo
Adding user `demo' ...
Adding new group `demo' (1001) ...
Adding new user `demo' (1001) with group `demo' ...
Creating home directory `/home/demo' ...
Copying files from `/etc/skel' ...
New password:
Retype new password:
passwd: password updated successfully
Changing the user information for demo
Enter the new value, or press ENTER for the default
        Full Name []: x
        Room Number []: x
        Work Phone []: x
        Home Phone []: x
        Other []: x
Is the information correct? [Y/n] y
root@DietPi3:~#

Code: Select all

 ─────────────────────────────────────────────────────
 DietPi v7.2.3 : 22:54 - Sat 06/05/21
 ─────────────────────────────────────────────────────
 - Device model : RPi 3 Model B+ (armv7l)
 - Uptime : up 1 minute
 - CPU temp : 39'C : 102'F (Cool runnings)
 - LAN IP : 192.168.0.12 (eth0)
 - Info Text : !!! DEMO 32bit !!!
 ─────────────────────────────────────────────────────


demo@DietPi3:~ $

are you able to share cat /etc/passwd
Probably you might going to hide personal data
There is two entries regarding the new users those being the following...

Code: Select all

user1:x:1001:1001: :/home/user1:/bin/bash

Code: Select all

user2:x:1002:1002: :/home/user2:/bin/bash
Both users still get connection closed via ssh although they work fine to login via a Samba Share or Local at the Pi...
User avatar
Joulinar
Posts: 5162
Joined: Sat Nov 16, 2019 12:49 am

Re: Dropbear SSH closing connection when attempting to connect as a non Root User

Post by Joulinar »

if the user would be locked or something, you would get a different error message I guess.

Can you check the log for realted messages

Code: Select all

journalctl -u dropbear.service
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply