ClearML/dropbear
1
0
Fork 0
mirror of https://github.com/clearml/dropbear synced 2025-01-31 02:46:58 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Better docs for DisableTrivialAuth

Browse Source
This commit is contained in:
Matt Johnston 2022-11-11 11:25:50 +08:00
parent 960d374e65
commit b2b94acc97
2 changed files with 27 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
CHANGES
View File

@ -40,7 +40,7 @@ Features and Changes:
- Improve permission error message - Improve permission error message
Patch from k-kurematsu Patch from k-kurematsu
2022.82 regression fixes: Regression fixes from 2022.82:
- Fix X11 build - Fix X11 build
@ -155,10 +155,13 @@ Features and Changes:
Patch from Raphaël Hertzog Patch from Raphaël Hertzog
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903403 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903403
- Added client option "-o DisableTrivialAuth". This can be used to prevent - Added client option "-o DisableTrivialAuth". It disallows a server immediately
the server immediately accepting successful authentication (before any auth giving successful authentication (without presenting any password/pubkey prompt).
request) which could cause UI confusion and security issues with agent This avoids a UI confusion issue where it may appear that the user is accepting
forwarding - it isn't clear which host is prompting to use a key. a SSH agent prompt from their local machine, but are actually accepting a prompt
sent immediately by the remote server.
CVE-2021-36369 though the description there is a bit confused. It only applies
to Dropbear as a client.
Thanks to Manfred Kaiser from Austrian MilCERT Thanks to Manfred Kaiser from Austrian MilCERT
- Add -q client option to hide remote banner, from Hans Harder - Add -q client option to hide remote banner, from Hans Harder

20
dbclient.1
View File

@ -94,7 +94,18 @@ is performed at all, this is usually undesirable.
.B \-A .B \-A
Forward agent connections to the remote host. dbclient will use any Forward agent connections to the remote host. dbclient will use any
OpenSSH-style agent program if available ($SSH_AUTH_SOCK will be set) for OpenSSH-style agent program if available ($SSH_AUTH_SOCK will be set) for
public key authentication. Forwarding is only enabled if -A is specified. public key authentication. Forwarding is only enabled if \fI-A\fR is specified.
Beware that a forwarded agent connection will allow the remote server to have
the same authentication credentials as you have used locally. A compromised
remote server could use that to log in to other servers.
In many situations Dropbear's multi-hop mode is a better and more secure alternative
to agent forwarding, avoiding having to trust the intermediate server.
If the SSH agent program is set to prompt when a key is used, the
\fI-o DisableTrivialAuth\fR option can prevent UI confusion.
.TP .TP
.B \-W \fIwindowsize .B \-W \fIwindowsize
Specify the per-channel receive window buffer size. Increasing this Specify the per-channel receive window buffer size. Increasing this
@ -159,6 +170,13 @@ Send dbclient log messages to syslog in addition to stderr.
.TP .TP
.B Port .B Port
Specify a listening port, like the \fI-p\fR argument. Specify a listening port, like the \fI-p\fR argument.
.TP
.B DisableTrivialAuth
Disallow a server immediately
giving successful authentication (without presenting any password/pubkey prompt).
This avoids a UI confusion issue where it may appear that the user is accepting
a SSH agent prompt from their local machine, but are actually accepting a prompt
sent immediately by the remote server.
.RE .RE
.TP .TP
.B \-s .B \-s