Device connection fails after authentication due to invalid certificate errors

[Iss-in]

Current Behavior

KDEconnect/Playstore in moto edge device
valent-git 1.0.0.alpha.46.r94.g1ce2347-1/ AUR

After the first pair, Device disconnects from valent

on refreshing client on either side , device momentarily shows up and disappear again with same error.

I am able to connect to kdeconnect on some other device without any issue. But that other device is also working with valent without any issues

Expected Behavior

show stay connected after pairing

Desktop

Other (please specify)

Other Desktop

hyprland

Operating System

Arch

Installed from

Other

Version

1.0.0.alpha

Devices

No response

Plugins

No response

Logs

9:56:05.1163     valent-lan-channel-service:    DEBUG: incoming_broadcast_task(): authenticating (192.168.1.57:1716): Invalid certificate for "f3943726_4104_4a5b_bad5_f3383f92d564"
09:56:08.3976     valent-lan-channel-service:    DEBUG: incoming_broadcast_task(): authenticating (192.168.1.57:1716): Invalid certificate for "f3943726_4104_4a5b_bad5_f3383f92d564"

### Screenshots

_No response_

[andyholmes]

Thanks! I haven't seen this myself, but something is going funky.

For reference, KDE Connect devices store their device ID in the subject of the TLS certificate. In other words, the TLS certificate is a reliable source of truth for the device ID, so this bug "shouldn't" happen.

The obvious security breach is someone creating a new TLS certificate with a spoofed device ID, but they'd need to be on your LAN and so on; pretty unlikely. I'll see what I can dig up :)

[Iss-in]

this is happening only with my brand new moto edge 50 neo, which idk if relevant or not , letme know if i can help in debugging with it in any way