Signal Desktop App on Windows does not properly handle UNC attachment or sticker paths. about signal-desktop HOT 2 OPEN

@crashkopf Hi, it seems like UNC paths are used to access network paths, and in the discussion in #5427 there was a decision to consider Signal network path file access a feature request, because it's not by design that Signal works across network paths for security reasons.

This seems to be very similar to #5427 and I'd ask that you post in the Community Forum Desktop Feature Requests (https://community.signalusers.org/c/feature-requests/desktop-feature-requests/20) to show support for the feature before we implement it.

from signal-desktop.

Regardless of whether the maintainers intend to support user profiles stored on networked drives (which rightfully should be the choice of the user or system administrator), the following salient points should be considered:

• The path-handling code for attachments is not working as intended. In other parts of the app, userDataPath isn't being being mangled, so there's some inconsistency. File paths should be handled correctly and consistently throughout the app.
• The app is using %APPDATA%/Signal as it's path to store user data. If that's the design choice then you have to respect that %APPDATA% can be any valid directory path. See https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats. In fact, UNC paths are part of the protocol filter tests, implying they're already intentionally supported.

from signal-desktop.