fishi0x01/vsh

Properly handle ambigious files

Closed this issue · 0 comments

Vault allows a path structure like:

secret/a
secret/a/x
secret/a/y

For vsh this makes secret/a a potential file and directory at the same time. This leads to potentially unwanted behavior in cp, mv, cat and grep.

The same bug was already solved for rm in #29