-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lpass logout
prompts for password when session is stale
#477
Comments
waterkip
added a commit
to waterkip/lastpass-cli
that referenced
this issue
Mar 26, 2019
`lpass status` asks the agent to see if we are logged in or not. The code for the logout bit checks the session and if a session has gone stale it want to refresh it. Implement a similar logic as in cmd-status.c where we ask the agent if we have a session, if we do, proceed as always, else, wipe all the session data that we can find. This removes the if-logic in session kill, to delete all config files even if they for whatever reason do not exist. Since we want to kill it, it seems logical to ignore these missing files. Fixes: lastpass#477 Signed-off-by: Wesley Schwengle <wesley@schwengle.net>
Could you test my branch: |
waterkip
added a commit
to waterkip/lastpass-cli
that referenced
this issue
Mar 26, 2019
waterkip
added a commit
to waterkip/lastpass-cli
that referenced
this issue
Mar 26, 2019
`lpass status` asks the agent to see if we are logged in or not. The code for the logout bit checks the session and if a session has gone stale it want to refresh it. Implement a similar logic as in cmd-status.c where we ask the agent if we have a session, if we do, proceed as always, else, wipe all the session data that we can find. This removes the if-logic in session kill, to delete all config files even if they for whatever reason do not exist. Since we want to kill it, it seems logical to ignore these missing files. Fixes: lastpass#477 Signed-off-by: Wesley Schwengle <wesley@schwengle.net>
waterkip
added a commit
to waterkip/lastpass-cli
that referenced
this issue
Mar 29, 2019
`lpass status` asks the agent to see if we are logged in or not. The code for the logout bit checks the session and if a session has gone stale it want to refresh it. Implement a similar logic as in cmd-status.c where we ask the agent if we have a session, if we do, proceed as always, else, wipe all the session data that we can find. This removes the if-logic in session kill, to delete all config files even if they for whatever reason do not exist. Since we want to kill it, it seems logical to ignore these missing files. Fixes: lastpass#477 Signed-off-by: Wesley Schwengle <wesley@schwengle.net>
waterkip
added a commit
to waterkip/lastpass-cli
that referenced
this issue
Mar 29, 2019
`lpass status` asks the agent to see if we are logged in or not. The code for the logout bit checks the session and if a session has gone stale it want to refresh it. Implement a similar logic as in cmd-status.c where we ask the agent if we have a session, if we do, proceed as always, else, wipe all the session data that we can find. This removes the if-logic in session kill, to delete all config files even if they for whatever reason do not exist. Since we want to kill it, it seems logical to ignore these missing files. Fixes: lastpass#477 Signed-off-by: Wesley Schwengle <wesley@schwengle.net>
GPaulovics
added a commit
that referenced
this issue
Apr 5, 2019
…e_a_login Fix bug where logout requires login by @waterkip
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repro steps:
lpass show
should reprompt for password,lpass status
returns "Not logged in.")lpass logout -f
Expected Behaviour:
lpass should clear any session information from memory, or if no session information is present should no-op
Actual Behaviour:
lpass prompts to reauthenticate
Additional observation:
lpass logout
can distinguish between 'logged out' and 'expired session' (it either prompts for confirmation or displays "Error: Not currently logged in.") butlpass status
does not distinguish between these two scenarios (returns "Not logged in." with exit code 1 in both cases).My use case is a script to log me out of assorted CLIs at the end of the day. I don't want the script to require interaction, but I currently have to sign in to lastpass so that I can sign out of lastpass. In addition, the current behaviour of
lpass status
means I can't query if I'm truly logged out beforecalling
lpass logout
.The text was updated successfully, but these errors were encountered: