You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hejsa
Disabling DROPBEAR_SVR_MULTIUSER config on kernel 5.10 without CONFIG_MULTIUSER produces a failed sanity check when initiation a session.
Traced the issue down to
. The "getuid()" doesn't set errno to "ENOSYS" as expected.
Looked into the kernel source and looks like "getuid()" syscall is always present, independently of CONFIG_MULTIUSER. Also, when CONFIG_MULTIUSER is disabled "getuid()" always succeeds and returns "0". This behaviour is present at leats from kernel 4.9.
My workaround is to change "getuid" syscall into "getgroups". The "getgroups" has the expected behaviour, it is only present when the kernel is configured with CONFIG_MULTIUSER.
The text was updated successfully, but these errors were encountered:
Hejsa
Disabling DROPBEAR_SVR_MULTIUSER config on kernel 5.10 without CONFIG_MULTIUSER produces a failed sanity check when initiation a session.
Traced the issue down to
dropbear/common-session.c
Line 75 in 9defeb4
Looked into the kernel source and looks like "getuid()" syscall is always present, independently of CONFIG_MULTIUSER. Also, when CONFIG_MULTIUSER is disabled "getuid()" always succeeds and returns "0". This behaviour is present at leats from kernel 4.9.
My workaround is to change "getuid" syscall into "getgroups". The "getgroups" has the expected behaviour, it is only present when the kernel is configured with CONFIG_MULTIUSER.
The text was updated successfully, but these errors were encountered: