Re: KDE connect: wrong association key with BT during authorization with app

Stakanov <[email protected]> Mon, 05 Jan 2026 14:20:27 +0100
Newsgroups gmane.comp.kde.general
Message-ID <2376400.EFV029mV52@p200300c96f2793004cf7d2cb2556b110.dip0.t-ipconnect.de>
--nextPart11287686.lLdpxTegYS
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Stakanov <[email protected]>
To: [email protected]
Date: Mon, 05 Jan 2026 14:20:27 +0100
In-Reply-To: <1980384.BzoyzFIZL3@bola>
MIME-Version: 1.0

In data domenica 4 gennaio 2026 15:07:56 Ora standard dell=E2=80=99Europa c=
entrale,=20
Ren=C3=A9 J.V. Bertin ha scritto:
> On Sunday January 04 2026 11:21:24 Stakanov wrote:
> >I have a Xiaomi
>=20
> Maybe that's your problem, and you just stumbled upon proof that those
> state-controlled Chinese manufacturers do indeed try to pull MITM-like
> tricks ;)
>=20
> Seriously, this is just a generic forum. You probably should report this
> first on Susie's bug tracker as there are just too many layers where
> something can go wrong (i.e. it might not be an issue in KDE Connect).
>=20
> Did you try pairing over good old wifi?

Can I do this with direct connection to this PC without needing to pass ove=
r a=20
network?
--nextPart11287686.lLdpxTegYS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQFPBAABCAA5FiEEq7egIaWjj/Ppns8x8mOB1qZR8N8FAmlbupwbFIAAAAAABAAO
bWFudTIsMi41KzEuMTEsMiwyAAoJEPJjgdamUfDfIEMH/18cvT38ROeEbrbLYD0Z
wEXeTEjpO/Nf4MtzKRb3Kb1w5Yd2eJ1jwZ/WB0mVLo8RJZ8JJbOcEd7S8/NlFNyR
nxpawRNiqBp0aDN9WfrytlWsHWYi2ddZN0Q2m59RWfQvz/hsiLZxwqmxkQrCvwg3
180zs1ivuQMfjm2cAjgKc/5Fowespp4pNFEKveGYXfVAXeJ43+g6sGDYWB5+0nxo
dyM4r7ITsh3owM3+oEN1nLgH8J+IKm9tDQvtvUMxwLZrx8s6uUKIqnD008ZhTvnD
fBJS/ZXinhqTRzTtBKOHxiUMhG6p2sS1oL4y7phOf7nEt/wuPdxfsrpJKEI4MpHB
lR4=
=9ccu
-----END PGP SIGNATURE-----

--nextPart11287686.lLdpxTegYS--