Master password reprompts not handled correctly

[samcday]

This might be related to #3.

I couldn't get this workflow to work at first. After a bit of diagnosis, I found lastpass/lastpass-cli#70. Basically, your Lastpass can be configured at the account level, or at the individual site/note level to require a master password reprompt. The kicker is that if your vault contains a single site or secure note that requires reprompt, then every call to lpass export will require the master password, regardless of whether you have an active lpass agent session or not.

You can test this by changing one of your sites to require password reprompt, then run lpass export over and over again - you'll hit the master password prompt every single time.

This totally breaks this Alfred workflow, because the master prompt gets hit when it tries to run the export. In essence, no matter how robust you make the "am I currently logged in?" check (btw - I think checking the sockfile is a good solution), you'll still break in this case.

When you run lpass export, is there any reason why you can't detect the master password prompt (I believe it's output on stderr), and then show an error to the user? As it currently stands, the export that lpdd runs will actually hang indefinitely on the master password prompt.

[cthulu]

Facing this issue as well. lpass export requests my master pw as well (some of my logins request the password re-type).