You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v0.107.53 we have added a migration that should automatically detect and fix lax permissions on files on Unix-like systems. Unfortunately, the poor support of the Windows permission model from the standard Go library prevented us from doing the same on Windows.
We must find or develop libraries to make the migration and these mitigations work on Windows, as well just generally allow us to control file permissions properly.
Expected result
v0.107.53 fixes applied automatically on Windows.
Actual result
v0.107.53 fixes are not applied automatically on Windows.
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered:
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Windows, AMD64 (aka x86_64)
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
v0.107.53
Action
In v0.107.53 we have added a migration that should automatically detect and fix lax permissions on files on Unix-like systems. Unfortunately, the poor support of the Windows permission model from the standard Go library prevented us from doing the same on Windows.
We must find or develop libraries to make the migration and these mitigations work on Windows, as well just generally allow us to control file permissions properly.
Expected result
v0.107.53 fixes applied automatically on Windows.
Actual result
v0.107.53 fixes are not applied automatically on Windows.
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered: