Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vivaldi (browser) can't save bookmarks anymore. #153

Closed
Julikus opened this issue Oct 15, 2020 · 9 comments
Closed

Vivaldi (browser) can't save bookmarks anymore. #153

Julikus opened this issue Oct 15, 2020 · 9 comments
Labels
fixed in next build Fixed in the next Sandboxie version

Comments

@Julikus
Copy link

Julikus commented Oct 15, 2020

Vivaldi can't save bookmarks anymore. Settings are set: "applications -> browsers -> Vivaldi [did same for Chrome] -> allow direkt access to Bookmarks".
If I add the path "%Local AppData%\Vivaldi\User Data\Default" in "Resource Access -> File Access -> Direct Access" I am able to save bookmarks.
But this is a big hole and allows everything to be saved (history, cookies, etc.).

I need some guidance to solve the issue.

@Julikus Julikus changed the title Vivaldi can't save bookmarks anymore. Vivaldi (browser) can't save bookmarks anymore. Oct 15, 2020
@Deadite333
Copy link

Same here.

Both methods, using the template or manually adding bookmarks don't work.

Only the entire profile folder or - slightly more secure - "Default" folder will do the trick, not recommended for obvious reasons.

Hopefully the next update will fix the issue, nothing a user can do.

@DavidXanatos
Copy link
Member

Is that issue Vivaldi specific or happens to other chrome derivates to?

@Deadite333
Copy link

Hi and thx for answering.

I've just tried Edge (Chromium version), added bookmarks via Direct Access, and yep, bookmarks/favorites don't get saved there either.

@bjm234
Copy link

bjm234 commented Oct 17, 2020

Hi and thx for answering.

I've just tried Edge (Chromium version), added bookmarks via Direct Access, and yep, bookmarks/favorites don't get saved there either.

Yep, my Direct Access not working -
%Local AppData%\Microsoft\Edge\User Data\Default\Bookmarks
%Local AppData%\Microsoft\Edge\User Data\Default\Favicons
5.43.6

@Julikus
Copy link
Author

Julikus commented Oct 21, 2020

Good to hear that I am not the only one with this issue. I hope you can fix it soon.
Unfortunately sandboxie is without this function worthless to me. :-(

@Deadite333
Copy link

It's a possibility to still add Default to Direct Access and then relevant files and folders from Default to Read-Only Access.

Greatly reduces what would hit the drive, instead of several MB it's only some kB. Bookmarks can now be handled, and the exposure left is tolarable (to me at least, under the circumstances) compared to the inconvenience of not being able to save or delete bookmarks from within Sandboxie .

@Julikus
Copy link
Author

Julikus commented Oct 21, 2020

It's a possibility to still add Default to Direct Access and then relevant files and folders from Default to Read-Only Access.

Greatly reduces what would hit the drive, instead of several MB it's only some kB. Bookmarks can now be handled, and the exposure left is tolarable (to me at least, under the circumstances) compared to the inconvenience of not being able to save or delete bookmarks from within Sandboxie .

That doesn't work for me. My Vivaldi won't start if I set "Default" to "Direct Access" and partial to "Read-Only Access".
Precisely if I add the file(s) "History", "Login Data", "Cookies", etc. to "Read-Only Access" the Vivaldi-Window won't show up just for a second.

My only choices are:
add "Default" to "Direct Access" (so using sandboxie makes no sense)
or:
to use sandboxie with standard config (nothing will be saved: no bookmarks, no cookies, no login, etc.).
Browsing without bookmarks is like browsing with Alzheimer's disease: you can't remember anything after <5 hours.

p.s.: I am using SandboxieInstall64-v5.43.6

@DavidXanatos DavidXanatos added fixed in next build Fixed in the next Sandboxie version and removed to investigate labels Oct 26, 2020
@DavidXanatos
Copy link
Member

DavidXanatos commented Oct 26, 2020

I found the issue it was a bug introduced with one of the driver verifier fixes and affects file renaming.

Chrome and derivatives create a temporary bookmark file and than rename it to its target name which is white listed in the ini, this renaming operation failed.

The issue is resolved in builds 0.4.3 / 5.43.7 and later (which are to be released soon), until than a workaround could be to allow chrome access to the entire chrome profile folder i.e. using
OpenFilePath=chrome.exe,%Local AppData%\Google\Chrome\User Data\Default*

@Julikus
Copy link
Author

Julikus commented Oct 26, 2020

Thank you very much DavidXanatos!

@Julikus Julikus closed this as completed Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed in next build Fixed in the next Sandboxie version
Projects
None yet
Development

No branches or pull requests

4 participants