Unable to fetch blob - after successful login/sync about lastpass-cli HOT 8 CLOSED

what about --sync=no after login (which should only look at the local blob)?

from lastpass-cli.

Consolidating my comments here:

1. good login
2. tested lpass ls --sync=no : same error
3. currently testing this with and without active agent. I note that the .lpass/agent.sock is present regardless of the value of LPASS_AGENT_DISABLE, though I assume that is unrelated.
4. ~/.lpass/blob is > 600k after initial (good) login, so network connectivity and sync seems to work, but lpass is erroring out on finding the blob in subsequent commands.
5. I also tested with a recursive chmod to a+rwx on .lpass and no luck.

from lastpass-cli.

Same problem here on Debian/Ubuntu.

lastpass_get_blob_version in blob_get_latest returns 0 causing the function to ignore the local blob.

login_check.php returns the following xml on my system:

from lastpass-cli.

Well it's clear we need a better message in any case.

@dirkvm what 2fa are you using? care to send me your login details so I can check it out on the server? ([email protected])

EDIT: I mean just username only

from lastpass-cli.

@altercation same questions to you. If you send me your username privately I can check whether it's related to your configuration.

from lastpass-cli.

In dirkvm's case we tracked this down to omnikey (smartcard authentication) being enabled which isn't supported in lastpass-cli, so disabling that is a thing to try for anyone in the same boat. Also we modified the server to not spit out an invalid/confusing error message in this case.

from lastpass-cli.

@bcopeland I'll message you privately as well with username, but I'm not seeing omnikey options (to disable) in lastpass prefs. Could you give me a pointer towards that option to disable.

I should also note that I have the lastpass binary component installed here, prior to/separately from lastpass-cli.

from lastpass-cli.

altercation and I worked this out offline -- it seems different errors can manifest in the same way. At any rate, I pushed 46e507d to fix and will close this. Anyone still experiencing this should open a new issue.

from lastpass-cli.