Open pablosmedina opened 4 years ago
A PR has been merged into master (#522) that aims to fix this issue, in theory.
Is the version you're running effectively the latest? I can see the GIT
suffix in the version number, but it appears to be the same as mine. In fact, it looks like it matches v1.3.3
, which is before the latest version in master.
That said: have you tried compiling from source? I.e., the version with the PR fix?
Can confirm that this fix appears to work as of commit (8767b5e).
I compiled from source today on macOS Catalina 10.15.4 (only modification I made was to adjust line 1 in Makefile (PREFIX ?= /usr/local) because of SIP. Was able to log in using my lastpass account that uses Microsoft Authenticator.
I ran in to this issue after installing the latest available version 1.3.3
. @Sparrow0hawk as you mentioned the fix was merged. Can a new version of the code base be tagged so we can install without having to compile from source?
If it helps anyone, I installed lastpass-cli
from master
and it seemed to work.
brew install lastpass-cli --HEAD
Thank you!
I ran in to this issue after installing the latest available version
1.3.3
. @Sparrow0hawk as you mentioned the fix was merged. Can a new version of the code base be tagged so we can install without having to compile from source?If it helps anyone, I installed
lastpass-cli
frommaster
and it seemed to work.brew install lastpass-cli --HEAD
Thank you!
Has this been updated into the master version? I installed on Ubuntu but could use the code in your reply.
Please tag it so I can install it with apt.
Hi!
I'm trying to log in using lpass cli with Microsoft authenticator enabled. After entering my master password an error in red appears saying 'Microsoft authenticator authentication required!'. But then it asks me for my master password again so nothing happens. I'm able to log in through web and browser extension by entering the 2fa code. So it seems there is a problem with the lastpass cli. I've already reported this issue through LogMeIn Support (ticket 12132104) and they confirmed the issue and it seems it requires code change.
Please let me know if you need more details about the issue.
Thank you!
Pablo