You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JWT auth + Fly proxy + possible second layer of encryption + fixing decrypting seed locally are all interconnected and need to be solved together.
remove CSRF token with an API authentication
What are the options for an additional layer of encryption (research additional TLS options to solve potential MITM proxy issues) -> decided not to do this
How does the Fly gateway work? does it remove the need for subdomains? -> yes, progress has started on fly gateway
Send unlock password to hub backend and hub will return seed protected by HTTPS and possibly another layer of encryption - this will solve the issue with users unable to backup their seed on .local addresses
JWT sounds good and saving to local storage. For fly gateway, we use an extra header.
The text was updated successfully, but these errors were encountered:
JWT auth + Fly proxy + possible second layer of encryption + fixing decrypting seed locally are all interconnected and need to be solved together.
What are the options for an additional layer of encryption (research additional TLS options to solve potential MITM proxy issues)-> decided not to do thisThe text was updated successfully, but these errors were encountered: