I feel like auto-locking isn't always happening

toblix
toblix
Community Member
in Browsers (Edge, Chrome, Firefox, etc.)

I've noticed that I've been surprised quite a number of times (typically after lunch or coming in in the morning) that the extension is already unlocked when I open it. I'm usually about 85% certain I did not just unlock it, with the remaining 15% allowing for a brain-fart) Is the auto-locking implemented in such a way that a bug could let it remain open indefinitely?

1Password Version: Not Provided
Extension Version: 0.9.6
OS Version: Chrome on Kubuntu
Sync Type: Not Provided

Comments

  • beyer
    beyer
    1Password Alumni

    Hey @toblix,

    Thanks for taking the time to let us know you may be seeing some inconsistencies in 1Password for Chrome's auto-lock behavior. We have yet to see anyone report any issues since we overhauled our locking manager about a month ago. To aid in troubleshooting your issue, I've ensured some additional lock manager logging will be created in the next release of 1Password. This release should hopefully be coming out later tonight.

    Is it possible you're signing into your account on 1Password.com before using 1Password for Chrome? I know on occasion I've known for sure that I didn't unlock 1Password for Chrome, only to find out I unlocked it by signing into my account on 1Password.com.

    I'll give you some additional troubleshooting steps when we publish the next release. Thanks for your help!

    --
    Andrew Beyer (Ann Arbor, MI)
    Lifeline @ AgileBits

  • dteare
    dteare

    Hi @toblix,

    We just published 0.9.7 with some additional logs. Please give that a go and next time this happens send us a copy of your logs so we can investigate what's happening. You can find the logs by going to the chrome://extensions page and clicking on the "background page" link, as shown here:

    From there you'll be able to find the Console and copy the logs from there.

    Please let us know when this issue happens again and we'll take a peek. Thanks again for reporting this!

  • toblix
    toblix
    Community Member

    Thanks, I'll update and be on the lookout!

  • toblix
    toblix
    Community Member

    Just did a test. FYI I'm running the extension in both of two Chrome "people" profiles, which might or might not matter.

    1. I made sure both extension instances were locked
    2. I unlocked one of the extension instances
    3. I started a stopwatch
    4. I locked my computer to the Kubuntu screen locker login thing
    5. Waited 11 minutes
    6. Unlocked computer by logging back in
    7. The extension instance I had unlocked was still unlocked :ohnoes:

    I also checked that the extension settings screen showed 10 minutes. I'd do a longer test, but I'm at work, so.

    Here's the full console output (sorry about the formatting, but I couldn't find a good multi-line code style):
    crypto tests: 245.7568359375ms
    my.1password.com/api/v2/auth/verify Failed to load resource: the server responded with a status of 400 (Bad Request)
    background.js:1 [_request] Request "/api/v2/auth/verify" failed: Error: Invalid request parameters.
    at new t (background.js:1)
    at _handleQwestError (background.js:1)
    at Array.f (background.js:1)
    at background.js:1
    at i (background.js:1)
    at a (background.js:1)
    at r (background.js:1)
    e.(anonymous function) @ background.js:1
    background.js:1 Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 signInWithEmailAndPasswordGetUniverse failed: Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 Failed to sign in: Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 PBES2g-HS256(100000): 36.24609375ms
    background.js:1 [LM] @startMonitoring (autolock=10)
    background.js:1

  • toblix
    toblix
    Community Member

    I just came in to the office today, and it was still unlocked. I've pasted the console dump below. Either I've started to 100% subconsciously unlock 1Password, or there's a bug somewhere ... Anyway:

    crypto tests: 245.7568359375ms
    my.1password.com/api/v2/auth/verify Failed to load resource: the server responded with a status of 400 (Bad Request)
    background.js:1 [_request] Request "/api/v2/auth/verify" failed: Error: Invalid request parameters.
    at new t (background.js:1)
    at _handleQwestError (background.js:1)
    at Array.f (background.js:1)
    at background.js:1
    at i (background.js:1)
    at a (background.js:1)
    at r (background.js:1)
    e.(anonymous function) @ background.js:1
    background.js:1 Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 signInWithEmailAndPasswordGetUniverse failed: Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 Failed to sign in: Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 PBES2g-HS256(100000): 36.24609375ms
    background.js:1 [LM] @startMonitoring (autolock=10)
    background.js:1

  • toblix
    toblix
    Community Member

    Huh. There's more than what I pasted, in both posts above; it just cuts off mid-log. Looks like the flag characters in the log are messing up the post (even though they look fine in the preview)?

    Here's an updated log, hand-escaped:

    crypto tests: 245.7568359375ms
    my.1password.com/api/v2/auth/verify Failed to load resource: the server responded with a status of 400 (Bad Request)
    background.js:1 [_request] Request "/api/v2/auth/verify" failed: Error: Invalid request parameters.
    at new t (background.js:1)
    at _handleQwestError (background.js:1)
    at Array.f (background.js:1)
    at background.js:1
    at i (background.js:1)
    at a (background.js:1)
    at r (background.js:1)
    e.(anonymous function) @ background.js:1
    background.js:1 Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 signInWithEmailAndPasswordGetUniverse failed: Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 Failed to sign in: Error: Invalid email or password
    at new t (background.js:1)
    at background.js:1
    at
    e.(anonymous function) @ background.js:1
    background.js:1 PBES2g-HS256(100000): 36.24609375ms
    background.js:1 [LM] @startMonitoring (autolock=10)
    background.js:1 (golf flag) start
    background.js:1 (car racing flag) end
    background.js:1 (golf flag) start
    background.js:1 (car racing flag) end
    background.js:1 [LM] Locked at Sat Nov 04 2017 16:47:29 GMT+0100 (CET)
    background.js:1 [LM] @stopMonitoring
    background.js:1 PBES2g-HS256(100000): 36.298095703125ms
    background.js:1 [LM] @startMonitoring (autolock=10)
    background.js:1 (golf flag) start
    background.js:1 (car racing flag) end
    background.js:1 (golf flag) start
    background.js:1 (car racing flag) end

  • beyer
    beyer
    1Password Alumni

    @toblix: Can you enable the Preserve log and Show timestamps checkboxes above the Console output? Once you see this issue again, right-click the console log, save it as a text file, and send it to support+forum@agilebits.com with the following tracking code in the subject line [ZLI-97759-634]. Additionally, I'd like you to try running our new diagnostics report tool. Follow this link, click the "Open 1Password and Send Diagnostics" button, and click "Send" on the support form. This should hopefully give us a clearer picture to work with.

    We greatly appreciate your help!

    --
    Andrew Beyer (Ann Arbor, MI)
    Lifeline @ AgileBits

  • toblix
    toblix
    Community Member

    Email sent and support form sent. Another thing I forgot to mention is that I'm running Chrome in developer mode, in case that matters at all.

  • AGAlumB
    AGAlumB
    1Password Alumni

    @toblix: Thanks for mentioning that. I'll add a note there so Beyer sees it. :)

    ref: DAF-84917-165

This discussion has been closed.