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
The PIN can be an arbitrary passphrase - nowhere is it enforced that it is actually a PIN. Whilst consumers of this package could enforce this, we don't and so references to "PIN" should just be renamed to "passphrase" everywhere it appears.
The text was updated successfully, but these errors were encountered:
Given that we need to abstract over things in one way or another in crypt.go. We can probably start there by renaming "PIN" to "UserPassphrase" in that context. Renaming PIN in the context of the TPM specific code is more involved, there's even a file called pin.go atm.
…* funcs
Also rename PIN in its definition to UserPassprase to move toward
better and also more abstract naming.
Same in the corresponding RecoveryKeyUsageReason code.
Se also issue #113
…* family
Merge pull request #116 from snapcore/activate-volume-options
Also rename PIN in its definition to Passphrase to move toward
better and also more abstract naming.
Same in the corresponding RecoveryKeyUsageReason code.
See also issue #113
The PIN can be an arbitrary passphrase - nowhere is it enforced that it is actually a PIN. Whilst consumers of this package could enforce this, we don't and so references to "PIN" should just be renamed to "passphrase" everywhere it appears.
The text was updated successfully, but these errors were encountered: