New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle new server from peerbook #357
Labels
enhancement
New feature or request
Comments
what does authorize do? and when do use authorize and verify? |
this was a bit outdated. I've updated the description: authorize is gone, it's only verify from now on... |
does it need to be moved out of the connect command? |
what will happen if the user chooses "dont ask me again"? |
We need to store a flag in local storage using the Preference plugin and don't show the menu if it's there.
…On 26 Jun 2023 at 10:56 +0300, Eyal Sasson ***@***.***>, wrote:
what will happen if the user chooses "dont ask me again"?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
and should the gate be removed? |
I'm closing this, as doing it when connecting to the gate is the best flow |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the user install webexec on a new server and properly configure its user id, Terminal7 receives and unverified peer notification from PeerBook. TWR should pop up and ask the user if he wants to verify it.
When the users chooses to verify, it asks the user from an OTP snd sends peerbook the "verify" admin command.
The text was updated successfully, but these errors were encountered: