Use Entitiy.EncryptionKey instead of reimplementing it
This fixes us sometimes using subkeys whose key flags allow encryption but don't have a valid algorithm for encryption, or that are expired, etc.
This commit is contained in:
parent
e65ed17b41
commit
781681b548
4 changed files with 6 additions and 58 deletions
2
go.mod
2
go.mod
|
|
@ -8,4 +8,4 @@ require (
|
|||
golang.org/x/crypto v0.0.0-20190513172903-22d7a77e9e5f
|
||||
)
|
||||
|
||||
replace golang.org/x/crypto => github.com/ProtonMail/crypto v0.0.0-20190427044656-efb430e751f2
|
||||
replace golang.org/x/crypto => github.com/ProtonMail/crypto v0.0.0-20190604143603-d3d8a14a4d4f
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue