Authorize HTML5 Push notifications

[Leon]

Hello,

With Windows 10 LTSC, I use Sandboxie Classic, Waterfox as browser and Home Assistant with a permanent tab in Waterfox.

Home Assistant is well configured to send notifications through the browser.
https://www.home-assistant.io/integrations/html5

These are therefore HTML5 notifications (which could also come from any website).

If I execute the non -sandboxed waterfox browser, there is no problem, the notifications work well!

But with Sandboxie the notifications from a website, are blocked, and I do not find how to allow them, I seek everywhere.

What is the solution?
Leon

 

[bastik-1001]

Hello.

Do you see notifications with https://www.kenherbert.dev/browser-notification-tester or https://www.bennish.net/web-notifications.html?

My assumption had been that it just works and the browser works quite normal. I don't use the HMTL5 notifications, but I understand that there is a use-case.

 

[Leon]

Yes this site: https://www.bennish.net/web-notifications.html is a perfect example, you must first validate the notification authorization and then the notification reaches the OS in the bottom corner RIGHT.

It works if it is not sandboxed, but it is blocked by Sandboxie.

 

[offhub]

From source:
// ToastNotificationManager requires open com and original token, with boxed com this causes a deadlock

You need to enable Application Compartment and COM access to see notifications.

# NoSecurityIsolation=y requires a supporter certificate. It also sacrifices security for compatibility.
NoSecurityIsolation=y

# Template=OpenCOM also sacrifices security for compatibility.
OpenIpcPath=waterfox.exe,*\BaseNamedObjects*\__ComCatalogCache__
OpenIpcPath=waterfox.exe,\RPC Control\epmapper
OpenIpcPath=waterfox.exe,\RPC Control\OLE*
OpenIpcPath=waterfox.exe,\RPC Control\LRPC*

 

[bastik-1001]

Something new from Windows 10 on. https://learn.microsoft.com/en-us/u...ons.toastnotificationmanager?view=winrt-26100

It even seems to have limitations.

Generally, sending a toast notification from a desktop app is the same as sending it from a UWP app. However, you should be aware of these differences and requirements:

• For a desktop app to display a toast, the app must have a shortcut on the Start screen.
• The shortcut must have an AppUserModelID.
• Desktop apps cannot schedule a toast.

In my tests, it worked with Firefox on Windows 7, but apparently things got complicated.

 

[Leon]

From source:
// ToastNotificationManager requires open com and original token, with boxed com this causes a deadlock

You need to enable Application Compartment and COM access to see notifications.

# NoSecurityIsolation=y requires a supporter certificate. It also sacrifices security for compatibility.
NoSecurityIsolation=y

# Template=OpenCOM also sacrifices security for compatibility.
OpenIpcPath=waterfox.exe,*\BaseNamedObjects*\__ComCatalogCache__
OpenIpcPath=waterfox.exe,\RPC Control\epmapper
OpenIpcPath=waterfox.exe,\RPC Control\OLE*
OpenIpcPath=waterfox.exe,\RPC Control\LRPC*

If I understood correctly, it involves:

- to go from Sandboxie Classic to Sandboxie Plus
- to have a license / certificate
- to sacrifice security a little
I am not ready to go through these steps for the moment, but I sincerely thank you for your effective response.

For my part, I found an alternative with the notifications from Home Assistant, with HASS.Agent which allows communication between HAOS / PC directly, without going through the browser.

@bastik-1001 I see that you are one of the refractory, or in other words, of those who enjoyed Windows 7 and I understand you!

I myself stayed for a very long time on Windows XP before making a jump to Windows 10, and that's only because I discovered the LTSC variant! Otherwise it was Linux direction for my personal PC.

 

[bastik-1001]

If I understood correctly, it involves:

- to go from Sandboxie Classic to Sandboxie Plus
- to have a license / certificate
- to sacrifice security a little

It's not required to switch from Sandboxie Classic version to Sandboxie Plus for that, but the new interface makes it easier.
In some instances, some steps can be applied without the need for a license / certificate, but I don't see a workaround for the application compartment use case. It should be investigated if there is something that can be done to allow standard applications to display standard notification, if the user wishes to do so. Due to the reduced isolation that is required, I recommend to set up two boxes, one for the purpose of getting notifications and the another for general browsing.

I found an alternative with the notifications from Home Assistant, with HASS.Agent which allows communication between HAOS / PC directly

This sounds like a good solution.

@bastik-1001 I see that you are one of the refractory, or in other words, of those who enjoyed Windows 7 and I understand you!

I myself stayed for a very long time on Windows XP before making a jump to Windows 10, and that's only because I discovered the LTSC variant! Otherwise it was Linux direction for my personal PC.

I have to change sooner or later (and the sooner, the better), but I have to get used to the new design, and its quirks. I am used to Windows, though Linux is still an option, but I doubt that I will leave Windows behind in its entirety.