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
{{ message }}
This repository has been archived by the owner on Jan 7, 2022. It is now read-only.
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:
I actually want to be able to do that, especially when I'm debugging.
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.
The text was updated successfully, but these errors were encountered:
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:
ls
, it can just read the secret keys. The concern about reading bash history seems esoteric to me.The text was updated successfully, but these errors were encountered: