Flaw in WARP Override Code


It seems that the override code does not refresh or randomly generate a new one when it is used. In my opinion, this is a poor design choice. If an override is used to disable the WARP client, the dashboard should receive a trigger indicating that the current code has been used and should generate a new one within seconds.

There are many ways in which this can be abused, which I won’t go into detail about. Please consider fixing this issue as a new feature request if it is not already on the roadmap.