We can do this by just adding a āresetā button to the enter code state
I noticed that when you reset an exit thatās been registered, the state goes back to āNewā but when you go to register it again, the registration seems to happen automatically without emailing a new code or asking for a code again.
I expected a new code to arrive and be required. Maybe this is planned since @drozdiak1 is still working on updating the registration endpoints.
@Adam_Soltys I think that once you have registered with an exit (successfully confirmed email), you āhave an accountā. Hitting the āResetā button just resets the exit listing state in your router.
To get the functionality you want, the āResetā button would involve also asking the exit to erase the account. Iām not sure what this would accomplish.
Ok that makes sense actually, it just makes it a little more difficult to test the verification process. Is there some way for me to access the exit to reset my own account for dev purposes?
One thing I did notice (I think, only tried once and Iāve been thoroughly confused all dayā¦) is that even when I signed up to the same exit with a different email, it still just auto registered me. I suppose we would actually want a new code in that case though.
@ttk2 @drozdziak1
We need to get the debugging functionality that Adam needs in. Either we have an endpoint that resets a routerās wireguard key without a reflash, or we have an endpoint on a test exit that makes it forget its database.
@Adam_Soltys your confusion results from the fact that you think of the email address as being the account identifier, but it is not. The account identifier is the routerās wireguard key, which is not visible to you. The only thing that the exit actually uses the email for is to check that you have access to an email account at all. This is intended as a (weak) anti sybil measure.
Iām not sure if this is actually a problem, but it is weird. Can anyone think of a reason why this would be an issue? Letās roll with it and see if things end up confusing for the user.
Ok thanks that makes about the wg key being the identifier and explains why putting another email in didnāt cause the exit to re-verify me. As for having a test exit, Iām thinking I may want to configure my gateway router at home as an exit anyways since Iāve noticed some performance degradation when Iām on AltheaHome as opposed to my normal wifi that Iām guessing is related to the fact that Iām using a remote exit. If I get that working then I can wipe the database as I please. A /wipe or /reset endpoint might still be handy thoughā¦
you need a vm for a exit, since itās kinda itās own thing. If you give me an ssh key I can give you access to borked, an exit which you can re-deploy and reset at will.