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
Although the command line interface is different, it looks like prs implements the format used by pass. This is not explicitly documented in the README. Is it safe to use for people that switch back and forth, or may modifying the password store using prs lead to a situation where it's not compatible with plain pass anymore? It would be great if that could be documented.
The text was updated successfully, but these errors were encountered:
Switching back and forth should be safe! Though my testing on this is somewhat limited.
I do mention compatibility here, but I agree that it isn't really an exhaustive list.
It's special additions that may not work very well with prs together. Tomb support may be a good example, to encrypt your password store directory to prevent metadata leakage. prs handles all of it fully automatically, while pass does not. There are helpers for it though, such as pass-tomb. You could use the very same helper for prs as well, but that's not needed as it will do it for you.
Although the command line interface is different, it looks like
prs
implements the format used by pass. This is not explicitly documented in the README. Is it safe to use for people that switch back and forth, or may modifying the password store usingprs
lead to a situation where it's not compatible with plainpass
anymore? It would be great if that could be documented.The text was updated successfully, but these errors were encountered: