Firefox 90 reports that Fences 'injects' a 'module' into Firefix - what is going on here?

Visiting about:third-party in Firefox 90 reveals this (link to screenshot). Why does Fences (I have version 3.0.9.11, on Windows 10) need to mess with Firefox? I would rather it did not mess with it.

11,457 views 7 replies
Reply #1 Top

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 Top


Visiting about:third-party in Firefox 90 reveals this (link to screenshot). Why does Fences (I have version 3.0.9.11, on Windows 10) need to mess with Firefox? I would rather it did not mess with it.
End of quote

Fences does not 'inject' anything into FF.  Fences runs in the Windows Explorer process only - which is pervasive in Windows so I suspect that is what it's seeing (and totally benign). 

Sean Drohan
Stardock Support Manager

Reply #3 Top

Basj, Sean: thanks.

I take it, then, that Firefox is being over-zealous in its conception (or detection) of software that modifies Firefox. I do find that result surprising (because, more or less, I trust and estimate Mozilla). I'll keep an eye on what others say about the new Firefox page.

 

Reply #4 Top

This is normal for applications which impact system wide things.  Sometimes hooks have to be set which can only be system wide with no ability to filter it for process names.

A dll being in process is not cause for concern in this case and it will simply do nothing in the firefox process as it is not explorer.  The list is not a list of software which modifies Firefox, it is purely a list of dlls loaded into the memory space which are not signed by Microsoft or Mozilla.

Reply #5 Top

Same thing with WindowBlinds. I suspect it's usage is simply because Firefox doesn't natively support 3rd party theming so WB/Fences use the module for such.

Reply #6 Top

Quoting bobj420, reply 5

Same thing with WindowBlinds. I suspect it's usage is simply because Firefox doesn't natively support 3rd party theming so WB/Fences use the module for such.
End of bobj420's quote

The WB one is entirely unavoidable as WB loads into everything.  Otherwise it wouldn't work.  The only difference is WB isn't MS signed unlike the MS theme engine.

This is the problem with a feature that lists dlls without any context.

Reply #7 Top

Quoting Neil, reply 6

The WB one is entirely unavoidable as WB loads into everything. Otherwise it wouldn't work. The only difference is WB isn't MS signed unlike the MS theme engine.

This is the problem with a feature that lists dlls without any context.
End of Neil's quote

My mistake entirely, I was actually thinking about Curtains which is why I was considering a similarity, didn't even pay attention to the section I was in.