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

            Bug ID: 514959
           Summary: KRDC / KDE Connect - Remember this certificate not
                    remembered
    Classification: Applications
           Product: krdc
      Version First unspecified
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: RDP
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY
When connecting to remote device via KRDC from "Virtual Display" / "Use device
as an external monitor" in KDE Connect, and it asks every time to verify the
certificate.


STEPS TO REPRODUCE
1. Setup KRDC and KDE connect between 2 machines.
2. Connect to remote device.
3. Remember this certificate when prompted.
4. disconnect.
5. reconnect. (new session)
6. It will prompt again "The certificate for this system is unknown", because
it does not remember.

OBSERVED RESULT
I click the "Remember this certificate" box. But it doesn't remember because it
keeps asking each session. I have taken note of the fingerprint in the details,
and it does not change between sessions. 

This is from the same host to the same remote device.

EXPECTED RESULT
It should only ask once, after remembering the first time.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.5-arch1-1 (64-bit)
Graphics Platform: Wayland

(both machines are the same)

ADDITIONAL INFORMATION

Something I noticed is the <hash> portion of the rdp connection string seems to
change each time I connect. In this format: rdp://<user>:<hash>@<ip>:<port>
And the port also seems to keep changing. Perhaps the port auto-increments if
it left a binding behind? I am not sure if the certificate is tied to the port
or something, seems unrelated. Just making notes.

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

Reply via email to