I should also mention that the directory symlink also fails with the command line `pass` so maybe the origin of the behavior rests in that part of the code.
However, after explaining the conundrum to a friend, I learned that a file-level symlink works with the command line tool (and therefore passff) but still fails on Android. On Fri, Jun 25, 2021 at 4:36 PM Andrew Beyer <beyer.and...@gmail.com> wrote: > > Personally I'd say you're doing the right thing, it's the external tools that > are not. > > Doesn't provide much help though, short of suggesting maybe file bugs against > them. > > On Fri, Jun 25, 2021, 13:48 Ken Smith <kgsm...@gmail.com> wrote: >> >> Apologies if this has already been answered in another forum but >> searching and a rereading of the man page have not turned up a good >> answer. What is the best practice around using the same password for >> completely separate domains, eg. companya.com and companyb.com merged >> and companyb.com asks us to log in using our companya.com credentials. >> I tried making a symlink just linking companyb.com -> companya.com and >> committing that to the repo but none of my password management tools >> (Android Password Store and passff) could find companyb.com in my >> password database despite finding companya.com just fine. >> >> Thank you in advance for your guidance. >> >> Ken S
