On Fri Dec 27, 2019 at 10:00 AM, Solène Rapenne wrote:
> Le 2019-12-26 16:53, [email protected] a écrit :
> >> 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
> >
> > [email protected]:/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.
> >
> >
>
>
> you want to try disabling unveil and pledge first, but adding / rwc
> is not the correct way to do so.
>
>
> disabling unveil/pledge is explained in the pkg-readme firefox file
> installed under /usr/local/share/doc/pkg-readmes/firefox
I don't have that directory on my machine. `man firefox` was the first
place I looked, however it doesn't mention anything about pledge/unveil
(or much of anything outside of flags), and SEE ALSO was not helpful.
> -----
> To disable pledge and/or unveil support when troubleshooting, set the
> corresponding pledge or unveil file in
> /etc/firefox/{unveil,pledge}.{main,content,gpu} to contain
> just "disable".
> -----
I disabled pledge and unveil per your instructions (creating a total of
6 files), however the bug is not fixed.
