On Thu Dec 26, 2019 at 6:12 PM, Stuart Henderson wrote: > On 2019/12/26 07:53, open...@evantann.com wrote: > > >Synopsis: "1Password X" extension on Firefox shows 0 passwords > > >Category: > > >Environment: > > System : OpenBSD 6.6 > > Details : OpenBSD 6.6-current (GENERIC.MP) #565: Tue Dec 24 > > 13:18:50 MST 2019 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > When logging into the 1Password X extension, you'll see a brief flash > > of your vault items (passwords), but after ~100ms they disappear and > > are replaced with the text "No items in this vault." As a result I'm > > unable to access any of my passwords on any OpenBSD device running > > -current. > > > > After communicating with a 1Password dev, he confirmed that all > > 1Password X storage is within Firefox's cache visible in about:cache. > > > > If it helps debug, Chrome also experiences this same issue, but it has > > been a problem in Chrome for longer. > > >How-To-Repeat: > > Install Firefox and the 1Password X extension. Save a password (vault > > item) into the extension. Log into the extension. You'll see the vault > > item briefly flash onto the screen then disappear. > > >Fix: > > Unknown. Initially I thought this could be related to the unveil > > changes that happened around the same time, since Chrome also has the > > same issue. I modified the /etc/firefox/unveil.main file to have > > `/ rwc` for testing but that did not change the behavior. I found no > > indications of a pledge-permission problem in dmesg. > > > Perhaps it is not in the main process - try unveil.content? > > > Running firefox under ktrace -di may also give clues but it's very > noisy, > I would usually get it started and to the point just before I trigger > the > behaviour, then "ktrace -di -p <parent process pid>" - the parent > process > is the one just named "/usr/local/bin/firefox" in the ps(1) listing.
Adding `/ rwc` to unveil.content and unveil.main did not fix the problem. ktrace was indeed very noisy. I grepped the kdump with $ kdump | grep RET -C4 | grep "\-1" -C4 to focus on -1 exit codes and searched the resulting output for "1password". I found 2 errors. The first with the mem address substituted: CALL futex($MEM_ADDRESS,0x82<FUTEX_WAKE|FUTEX_PRIVATE_FLAG>,1,0,0) RET write 1 RET futex -1 errno 1 Operation not permitted And the second with my cache folder and hash substituted: NAMI "$CACHE_FOLDER/entries/$HEX_HASH" RET sendmsg 32/0x20 RET acess -1 errno 2 No such file or directory I checked and indeed that cache entry does not exist on my filesystem. Just searching kdump for 1password reveals many http requests, however it's not clear to me if there's any errors surrounding those.
