From 1a4424fa74771ec2b91ceafbbca755dfe5eb771b Mon Sep 17 00:00:00 2001 From: Max Goedjen Date: Sat, 14 Mar 2020 14:28:44 -0700 Subject: [PATCH] Fixes #35 --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index e31fcf1..9444905 100644 --- a/README.md +++ b/README.md @@ -31,3 +31,11 @@ For Macs without Secure Enclaves, you can configure a Smart Card (such as a Yubi ### Security Considerations For the moment, you must build Secretive from source. For an app like this, it's critical that you trust that the app you're running is the app whose source you've checked out. To this end, Secretive has no third party dependecies, and is designed to be easy for you to audit for exploits. + +### A Note Around Code Signing and Keychains + +While Secretive uses the Secure Enclave for key storage, it still relies on Keychain APIs to access them. Keychain restricts reads of keys to the app (and specifically, the bundle ID) that created them. If you build Secretive from source, make sure you are consistent in which bundle ID you use so that the Keychain is able to locate your keys. + +### Backups and Transfers to New Machines + +Beacuse secrets in the Secure Enclave are not exportable, they are not able to be backed up, and you will not be able to transfer them to a new machine. If you get a new Mac, just create a new set of secrets specific to that Mac.