https://bugs.kde.org/show_bug.cgi?id=526928

            Bug ID: 526928
           Summary: NLA login always fails with "Could not find user in
                    SAM database" (FreeRDP 3.32.1)
    Classification: Plasma
           Product: KRdp
      Version First 6.7.5
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

With KRdp users ("Other users", or -u/-p on the command line), every NLA login
fails with "Could not find user in SAM database", even with the correct
password.
Versions:
- krdp 6.7.5 (Fedora 44)
- freerdp 3.32.1 (freerdp-libs-3.32.1-1.fc44)
Steps to reproduce:
1. Start a standalone server with known credentials:
   krdpserver --address 127.0.0.1 --port 3392 -u probe -p probe-pass
2. Connect with the correct password:
   xfreerdp /v:127.0.0.1:3392 /u:probe /p:probe-pass /sec:ext /cert:ignore
/auth-only
Actual result:
Client: ERRCONNECT_LOGON_FAILURE [0x00020014]. Server:
    [com.winpr.sspi.NTLM] ntlm_fetch_ntlm_v2_hash: Error: Could not find user
in SAM database
    [com.winpr.sspi] winpr_AcceptSecurityContext: AcceptSecurityContext status
SEC_E_NO_CREDENTIALS [0x8009030e]
    [com.freerdp.core.auth] credssp_auth_authenticate: AcceptSecurityContext
status SEC_E_NO_CREDENTIALS [0x8009030e]
    [com.freerdp.core.transport] transport_accept_nla: client authentication
failure
The result is the same with a user added in System Settings > Remote Desktop
(Users=<user> in krdpserverrc, with the password present in the secret service
as KRDP/<user>).
Expected result:
NLA login succeeds with the configured username and password.
Related:
- The same symptom was reported after a FreeRDP 3.31.1 -> 3.32.1 update, and
rolling back fixed it:
https://discuss.cachyos.org/t/rdp-server-broken-since-yesterday/36483
- https://discuss.kde.org/t/krdp-unable-to-authenticate/41471
- This is not bug 521776 (NoNewPrivileges/PAM). That one affects system-user
login, which works here for TLS-only clients.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to