[GH-ISSUE #45] [UI Fix] Warn when overwriting a pending device entry #9

New issue

Closed

opened 2026-03-04 01:34:05 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:34:05 +03:00

Owner

Originally created by @rgov on GitHub (Aug 1, 2022).
Original GitHub issue: https://github.com/spr-networks/super/issues/45

I can only have one device in "pending" state (where the MAC address is unassigned until the device connects) at a time. If I try to add another one, it silently replaces the first.

It should be possible to have multiple pending devices because they will connect with different passwords and therefore can be differentiated.

Originally created by @rgov on GitHub (Aug 1, 2022). Original GitHub issue: https://github.com/spr-networks/super/issues/45 I can only have one device in "pending" state (where the MAC address is unassigned until the device connects) at a time. If I try to add another one, it silently replaces the first. It should be possible to have multiple pending devices because they will connect with different passwords and therefore can be differentiated.

kerem closed this issue

2026-03-04 01:34:05 +03:00

kerem commented

2026-03-04 01:34:06 +03:00

Author

Owner

@lts-rad commented on GitHub (Aug 5, 2022):

This is a limitation of WPA3 support and using the wildcard MAC to accept a new device without knowing it's MAC address. ahead of time. When a device does authenticate successfully, the "pending" identifier is assigned to that device's MAC address.

Essentially -- WPA3 is a zero knowledge authentication protocol. The server must know the same password as the client ahead of time, otherwise the server has to have the client reconnect and retry if the server guesses the wrong password. So only one password at a time can be used with the password assigned to the wildcard MAC.

This differs from WPA2 where it would be possible to run multiple PBKDF2 hashes to find a matching password.

As a work around, a user can specify the MAC address of multiple new devices before they connect.

Docs might need to better reflect this

@lts-rad commented on GitHub (Aug 5, 2022): This is a limitation of WPA3 support and using the wildcard MAC to accept a new device without knowing it's MAC address. ahead of time. When a device does authenticate successfully, the "pending" identifier is assigned to that device's MAC address. Essentially -- WPA3 is a zero knowledge authentication protocol. The server must know the same password as the client ahead of time, otherwise the server has to have the client reconnect and retry if the server guesses the wrong password. So only one password at a time can be used with the password assigned to the wildcard MAC. This differs from WPA2 where it would be possible to run multiple PBKDF2 hashes to find a matching password. As a work around, a user can specify the MAC address of multiple new devices before they connect. Docs might need to better reflect this

kerem commented

2026-03-04 01:34:06 +03:00

Author

Owner

@rgov commented on GitHub (Aug 5, 2022):

Thanks for context. I think not only docs but a UI alert should appear and get confirmation before proceeding to delete a previously configured host.

On Aug 5, 2022, at 13:35, Alex Rad @.***> wrote:

Closed #45 as not planned.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

@rgov commented on GitHub (Aug 5, 2022): Thanks for context. I think not only docs but a UI alert should appear and get confirmation before proceeding to delete a previously configured host. > On Aug 5, 2022, at 13:35, Alex Rad ***@***.***> wrote: > > > Closed #45 as not planned. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you authored the thread.

kerem commented

2026-03-04 01:34:06 +03:00

Author

Owner

@lts-po commented on GitHub (Sep 8, 2022):

fixed in dev github.com/spr-networks/super@15bfa14296

@lts-po commented on GitHub (Sep 8, 2022): fixed in dev https://github.com/spr-networks/super/commit/15bfa142967548920d250de7aa914a8a04bfb70b

kerem referenced this issue

2026-03-04 01:35:51 +03:00

[PR #9] [MERGED] Api revamp #242