riccardom 1d213dd4d4 [client] Treat a profile with no identity as already deregistered ...

Two findings on the same consequence of pure reads: a profile can legitimately
carry no keys, because logging out clears them in place.

- sendLogoutRequestWithConfig went straight to wgtypes.ParseKey and failed with
  "incorrect key size: 0" on the second logout of the same profile. There is
  nothing to deregister for a peer that was never registered, so it returns
  cleanly. Before pure reads this case was hidden: the read minted a key and
  the daemon dialed management with one it had never seen.
- The mobile logout read the config with the generating reader right after
  checking the file exists. The two are not atomic, so a profile removed in
  between was resolved from the defaults and recreated by the write that
  follows. It uses the existing-file reader now.

Reported by cubic-dev-ai and CodeRabbit on PR #7398.

2026-09-02 15:50:19 +02:00

..

profile_manager.go

[client] Treat a profile with no identity as already deregistered

2026-09-02 15:50:19 +02:00

profile_state_test.go

[client, ios] Migrate switft profile manager to go (#6528)

2026-08-26 09:42:50 +02:00

profile_state.go

[client] Reuse the profile's account for iOS SSO logins (#7193)

2026-09-01 13:29:26 +02:00