Skip to content
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.

Sign up for GitHub

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

Update key-generation.md #27

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update key-generation.md #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/key-generation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ Password Manager Entry = concact(Cipher, Random Salt)

## Account recovery

To ensure the user can still access their account under the above assumptions, a recovery kit is required. This kit contains infromation needed to recover the Account Private Key and regain spending access on the account.
To ensure the user can still access their account under the above assumptions, a recovery kit is required. This kit contains information needed to recover the Account Private Key and regain spending access on the account.

## Recovering the Spending Private Key

Expand Down Expand Up @@ -117,7 +117,7 @@ Important this information can be used to recover you Aztec Account.

## Scenarios

### Lost device / no access to password manager / can’t remeber user password.
### Lost device / no access to password manager / can’t remember user password.

Here the user must posses their recovery kit and have access to their Ethereum Private Key. If they posses this, they can do the following.

Expand All @@ -138,7 +138,7 @@ It may be worth considering encrypting the Spending `Private Key` and `Account P

### Attacker tricks the user into generating their Recovery Private Key.

Without the `Recovery Kit`, the attacker can’t use this in any attack. However there is a phising attack here that the attacker could trick the user into “recovering” on an insecure website.
Without the `Recovery Kit`, the attacker can’t use this in any attack. However there is a phishing attack here that the attacker could trick the user into “recovering” on an insecure website.

To combat this, the recovery kit should explictly detail the correct URL to recover via e.g `wallet.aztec.network/recovery`.

Expand Down