Skip to content
This repository has been archived by the owner on Jan 7, 2022. It is now read-only.

Argument for using public key for the path, instead of discovery key #3

Open
pfrazee opened this issue Apr 12, 2017 · 1 comment
Open

Comments

@pfrazee
Copy link

pfrazee commented Apr 12, 2017

The argument for using discovery keys for the folder paths is to make it so you can't enumerate a user's dats with an ls.

Counter arguments:

  1. I actually want to be able to do that, especially when I'm debugging.
  2. You're not offering that much protection. If a program can ls, it can just read the secret keys. The concern about reading bash history seems esoteric to me.
@joehand
Copy link
Collaborator

joehand commented Apr 12, 2017

Yep, its a minor protection. The other concern we had was users accidentally publishing keys in screenshots or otherwise.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants