-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dropbear is closing non-root connections when used in a docker container #146
Comments
It looks like the Might also be worth putting some debug logging in ~tech/.bashrc (or whichever shell) |
I'm not sure what you meant by putting debug logging in my bashrc, but I did get some logs from strace. There's two files because in the container there were two PIDs (maybe because the docker daemon is started in a script instead of directly from the dockerfile). Here's the output from one process:
And from the other:
|
Ah, the problem looks like /home/tech is missing
Really Dropbear should just print a warning there. |
Alright, adding in the |
I want to test out an application that uses SSH to access devices which use the
clish
CLI project. I'm trying to create a docker container that runs Dropbear.The application tries to log in as a user called
tech
. Here is the contents of my/etc/passwd
file:In case you're wondering why the
tech
user has a UID of 0, it's because in the custom CLI that's being run in the container viaclish
, thetech
user needs root privileges for certain commands.So far, this is working well for the root user, as shown below
However, when trying to log in as the
tech
user, the connection succeeds, but is then immediately terminated.Here is the output of
ssh
with-vvv
after the connection succeedsAny help debugging this would be appreciated.
The text was updated successfully, but these errors were encountered: