We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Why not specify a different authorized_keys file, it should be much simpler to implement. No need to do all the stuff for a possible ~ expansion.
Just dropbear -H ~/.ssh -D auth_test That way you can also have multiple dropbear active with each own authorized_keys file
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Why not specify a different authorized_keys file, it should be much simpler to implement.
No need to do all the stuff for a possible ~ expansion.
Just dropbear -H ~/.ssh -D auth_test
That way you can also have multiple dropbear active with each own authorized_keys file
The text was updated successfully, but these errors were encountered: