New issue
Advanced search Search tips

Issue 689624 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Task



Sign in to add a comment

Stop using libsecret's synchronous API

Project Member Reported by cfroussios@chromium.org, Feb 7 2017

Issue description

Password Manager and OSCrypt use the libsecret's synchronous API. When a call to libsecret needs to unlock the keyring, libsecret will display a prompt to the user and calling thread will block indefinitely on the user's decision. If the user does not react to the prompt at all, blocking will be indefinite and the thread will appear to be hanging.

Possible plan
After issue 571003 is resolved, Password Manager will not use libsecret directly, but only through OSCrypt.

For OSCrypt, the only complete solution is to make the API asynchronous. This will require effort from all of OSCrypt's several clients.
 

Comment 1 by vabr@chromium.org, Feb 17 2017

Labels: tracking_work
Thanks for filing this!

Comment 2 by vabr@chromium.org, May 2 2017

Labels: -tracking_work Type-Task
Project Member

Comment 3 by sheriffbot@chromium.org, May 2 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment