Capture Full Page don't work after update

[cpuheater]

@DoctorG At least on the VeraCrypt drive Windows reports Everyone Full Control, the other I didn't check, but should be the same.

@lfisk NTFS is by default not case-sensitive, I don't know, if there is an option to make it case-sensitive.

[Pathduck]

@cpuheater said in Capture Full Page don't work after update:

@Pathduck Thank you very much for your great support, I really appreciate this!

You're very welcome

Probably the problem is not exclusively related to VeraCrypt encrypted drive, but I still don't understand why the filesystem should make a difference.

I think you're correct in that it's not exclusive to VeraCrypt.
I got digging into this and this rabbit hole goes deep

Vivaldi is a Chromium browser, and Chromium processes run "sandboxed" for security. One thing the installer does is add special user SIDs to the Application folder that plays a role in this sandboxing.

If these special SIDs are removed, the full-page capture fails, reasons unknown. If the SIDs are added back, full-page capture works. This seems to have started in Vivaldi 6.8/Chr128 and is independent of VeraCrypt.

As long as the file system is NTFS, the installer will apply these SIDs to the Application folder where the exe resides. This also applies on VeraCrypt drives, so it doesn't fully explain the issue, but the symptoms are related and probably caused by the sandboxing.

VeraCrypt drives seem to have default "Everyone=Full Control" permissions, with inheritance. But this does not seem to matter, what matters is the SIDs + the sandboxing. Possibly VeraCrypt's driver is involved as well.

There's a bug report now, and a dev will take a look over the weekend I hope. No idea how easy it is to solve though.

If you're interested in some more technical details I wrote up a doc including some links to Chromium source:
https://docs.google.com/document/d/1ovRymEhJwMCg2CkFQDUqHEMBLGit7hwE5-Y0j0a2FBk/edit?usp=sharing

Unfortunately I have not found any workaround to make it work on VeraCrypt, even adding the exact same standard permission an application folder should have on Windows and the capture still fails.

[cpuheater]

@Pathduck Thank you for continuing to investigate on this problem and for digging!
I try to help dig, but my knowledge is limited.

The information you provided is very interesting for me, even I don't understand everything, I learned a few things.

Unfortunately I have not found any workaround to make it work on VeraCrypt, even adding the exact same standard permission an application folder should have on Windows and the capture still fails.

I tried also to apply the same permissions to the Vivaldi folder including subfolders on the VeraCrypt drive as on the working Vivaldi Standalone installation folder. -> It's not working (as you mentioned)

I tried to copy the working Standalone installation to the VeraCrypt drive with robocopy.exe, using the following arguments:

robocopy "D:\Apps\Vivaldi.6.9.3447.51.x64(D)" "E:\Apps\Vivaldi.6.9.3447.51.x64(D)" /COPY:DATSOU /DCOPY:DATE /MIR

I was expecting it copies ALL attributes, security settings, etc., but this test failed too.

[Pathduck]

@cpuheater I found a possible "workaround" but probably not recommended.

A command line argument:
--no-sandbox
Disables the sandbox for all process types that are normally sandboxed. Meant to be used as a browser-level switch for testing purposes only
https://peter.sh/experiments/chromium-command-line-switches/#no-sandbox

Not sure about what sandboxing does or how important it is, but it's to do with process security that's all I know.

At least it's more proof that this is related to sandboxing.

[DoctorG]

@Pathduck Huh, running processes not-in-sandbox is not advised, disabling sandbox can open a large security risk wo browser and OS – not a box of pandora, but can of worms.

[Pathduck]

@DoctorG Yes of course, that's why it's only for testing. It confirms that sandboxing is involved in the issue is all.

Do you know what the sandboxing does and how it functions exactly and why Vivaldi's full-page capture fails on VeraCrypt drives with sandboxing enabled? Please let us know

I joke of course, only Chromium devs know I'm afraid.

[DoctorG]

@Pathduck said in Capture Full Page don't work after update:

only Chromium devs know I'm afraid.

Yepp!

[robinwayne]

This post is deleted!