Re: Firefox extension broken in -current's v71.0
On 2019/12/27 07:18, Evan Tann wrote: > On Fri Dec 27, 2019 at 10:00 AM, Solène Rapenne wrote: > > Le 2019-12-26 16:53, open...@evantann.com 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 > > > > > > 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. > > > > > > > > > > > > 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. Here are the contents, however something is strangely wrong with your installation if you have installed firefox from ports/packages and this doesn't exist. $ cat /usr/local/share/doc/pkg-readmes/firefox $OpenBSD: README,v 1.25 2019/12/03 17:00:46 landry Exp $ +--- | Running firefox on OpenBSD +--- If you encounter strange problems relating to bookmarks, downloads, window placement, toolbars, history, or other settings, it is recommended that you create a new profile and attempt to reproduce the problem before filing bugs. To create a new profile, start Firefox with the -ProfileManager switch, e.g. firefox -ProfileManager, and click "Create Profile". If Firefox doesn't start at all, try starting it with -safe-mode switch, which disables extensions and themes for your session. pledge(2) and unveil(2) Support === Firefox on OpenBSD is secured with pledge(2) and unveil(2) to limit the system calls and filesystem access that each of Firefox's three process types (main, content, and GPU) is permitted. By default, only ~/Downloads and /tmp can be written to when downloading files, or when viewing local files as file:// URLs. Files containing pledge promises and unveil paths and permissions for each type of process are located in /usr/local/lib/firefox/browser/defaults/preferences/. Each file can be overridden by copying it to /etc/firefox/ and modifying it. 3rd-Party MIME Handlers === Due to unveil(2) limiting filesystem access, only the default MIME handler registered for a given type can be chosen when opening a downloaded file. For example, to use the mupdf package to read PDFs, it must be registered as the default with XDG: $ xdg-mime default mupdf.desktop application/pdf The current default for a given type can be viewed with xdg-mime's query command: $ xdg-mime query default application/pdf The older mailcap-format handlers are also supported, but the path being executed must be explicitly added to the unveil.main file with "rx" permissions. For example, a ~/.mailcap file specifying: application/pdf; /usr/local/bin/xpdf %s must have "/usr/local/bin/xpdf rx" added to unveil.main for it to appear as an option in the "Open With" drop-down. Using mailto: links === To enable mailto: links in Firefox to open in your mail program, you may have to set a mailto protocol handler. Type "about:config" in Firefox's URL text field. Type "mailto" in the filter. If there is a string called
Re: Firefox extension broken in -current's v71.0
On Fri Dec 27, 2019 at 10:00 AM, Solène Rapenne wrote:
> Le 2019-12-26 16:53, open...@evantann.com 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
> >
> > 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.
> >
> >
>
>
> 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.
Re: Firefox extension broken in -current's v71.0
On Fri Dec 27, 2019 at 12:18 AM, George Koehler wrote: > On Thu, 26 Dec 2019 19:58:31 -0600 > myportslist20190...@nym.hush.com wrote: > > > > >Synopsis: "1Password X" extension on Firefox shows 0 passwords > > >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." > > > > I had this problem until I changed /etc/login.conf default class to use > > datasize-max=7000M: and datasize-cur=7000M and rebooted. I have > > 8GB RAM and haven't tried lower values yet for datasize-max and -cur. > > > > ... > > > > If I go to about:debugging# and This Firefox and UBlock Origin, I > > see > > "WebAssembly.Memory failed to reserve a large virtual memory region. > > This may be due to low configured virtual memory limits on this system." > > > WebAssembly in Firefox is broken because it allocates too much memory. > A Reddit comment from /u/brynet [1] suggests to disable WebAssembly. > "You need to manually set `javascript.options.wasm;false` in Firefox > `about:config`." I have never tried this and don't know whether it > would fix anything. I tried disabling wasm however the problem persists. > I run my amd64 desktop with datasize-cur=8G, though I have only 4G total > RAM. (I'm in the staff class, says `userinfo kernigh`.) This is enough > for Firefox to run some small WebAssembly demos [2], but doesn't fix > Twitch video. My staff class datasize-cur is 8192M and -max is infinity running 16G.
Re: Firefox extension broken in -current's v71.0
Le 2019-12-26 16:53, open...@evantann.com 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
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.
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
-
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".
-
Re: Firefox extension broken in -current's v71.0
On Thu, 26 Dec 2019 19:58:31 -0600 myportslist20190...@nym.hush.com wrote: > >Synopsis:"1Password X" extension on Firefox shows 0 passwords > >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." > > I had this problem until I changed /etc/login.conf default class to use > datasize-max=7000M: and datasize-cur=7000M and rebooted. I have > 8GB RAM and haven't tried lower values yet for datasize-max and -cur. > > ... > > If I go to about:debugging# and This Firefox and UBlock Origin, I > see > "WebAssembly.Memory failed to reserve a large virtual memory region. > This may be due to low configured virtual memory limits on this system." WebAssembly in Firefox is broken because it allocates too much memory. A Reddit comment from /u/brynet [1] suggests to disable WebAssembly. "You need to manually set `javascript.options.wasm;false` in Firefox `about:config`." I have never tried this and don't know whether it would fix anything. I run my amd64 desktop with datasize-cur=8G, though I have only 4G total RAM. (I'm in the staff class, says `userinfo kernigh`.) This is enough for Firefox to run some small WebAssembly demos [2], but doesn't fix Twitch video. [1] https://www.reddit.com/r/openbsd/comments/dlps5a/what_are_the_required_aboutconfig_settings_on/f4txe1c?utm_source=share_medium=web2x [2] https://docs.assemblyscript.org/examples -- George
Re: Firefox extension broken in -current's v71.0
>Synopsis: "1Password X" extension on Firefox shows 0 passwords >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." I had this problem until I changed /etc/login.conf default class to use datasize-max=7000M: and datasize-cur=7000M and rebooted. I have 8GB RAM and haven't tried lower values yet for datasize-max and -cur. I am using only three extensions: 1Password X, Firefox Containers, and UBlock Origin. For me, 1Password X will not work until I disable UBlock Origin and then restart Firefox. I then sign in to 1 Password X. At that point, I can re-enable UBlock Origin and everything works. The problem started with 1Password's new version 1.17.0. This workaround does work on all my -current machines. If I go to about:debugging# and This Firefox and UBlock Origin, I see "WebAssembly.Memory failed to reserve a large virtual memory region. This may be due to low configured virtual memory limits on this system." I don't know how to fix this, and my increased datasize-max and -cur don't change this. But if UBlock Origin starts before 1Password X, my guess is that this memory error stops 1Password X from working. As a side note, I have to start Firefox from the Downloads folder if I want to be able to upload files from it.
Re: Firefox extension broken in -current's v71.0
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 " - 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,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.
Re: Firefox extension broken in -current's v71.0
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 " - the parent process is the one just named "/usr/local/bin/firefox" in the ps(1) listing.
Firefox extension broken in -current's v71.0
>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. dmesg: 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 real mem = 17098555392 (16306MB) avail mem = 16567906304 (15800MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8f9a8000 (94 entries) bios0: vendor American Megatrends Inc. version "3801" date 03/14/2018 bios0: ASUSTeK COMPUTER INC. Z170-AR acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT TPM2 MCFG SSDT FIDT SSDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT DBGP DBG2 acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) SIO1(S3) PS2K(S4) PS2M(S4) UAR1(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3510.83 MHz, 06-5e-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3509.52 MHz, 06-5e-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3509.52 MHz, 06-5e-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3509.52 MHz, 06-5e-03 cpu3:
