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
Some W11 systems are configured to use more extensive security features, either by user choice or company policy.
One of these more problematic features is ASLR, which has the nasty side effect of breaking heaps of software, due to address relocations.
Problem
On a W11 system with Mandatory ASLR enabled (configured via Windows security), SSHFS-Win's underlying Cygwin implementation will throw a fatal error, citing address mismatch. This causes in most cases the network mapping to silently fail without errors.
Diagnosing this fault can be done by running .\sshfs-win.exe svc \sshfs.kr\user@myserver\ X:.
Reproduction
The issue can be systematically reproduced by toggling "Force randomisation for images (Mandatory ASLR)" in Windows Security to "On by default" :
Workaround
Disabling Mandatory ASLR and rebooting will solve any issues caused by address mismatch.
While this issue may perhaps never be fixed in the scope of SSHFS-Win, I ought to share my findings, having spent way too much time diagnosing this issue.
The text was updated successfully, but these errors were encountered:
Context
Some W11 systems are configured to use more extensive security features, either by user choice or company policy.
One of these more problematic features is ASLR, which has the nasty side effect of breaking heaps of software, due to address relocations.
Problem
On a W11 system with Mandatory ASLR enabled (configured via Windows security), SSHFS-Win's underlying Cygwin implementation will throw a fatal error, citing address mismatch. This causes in most cases the network mapping to silently fail without errors.
Diagnosing this fault can be done by running
.\sshfs-win.exe svc \sshfs.kr\user@myserver\ X:
.Reproduction
The issue can be systematically reproduced by toggling "Force randomisation for images (Mandatory ASLR)" in Windows Security to "On by default" :
Workaround
Disabling Mandatory ASLR and rebooting will solve any issues caused by address mismatch.
While this issue may perhaps never be fixed in the scope of SSHFS-Win, I ought to share my findings, having spent way too much time diagnosing this issue.
The text was updated successfully, but these errors were encountered: