mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #976] Windows10 client: unable to open trustetedServersFile - Username with space #784
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#784
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Schlunze on GitHub (Dec 8, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/976
on a Windows Client i have a space and "ä" in the username.
The File trustedServers.txt is written correctly, fingerprint is ok.
The log on client shows continuously: Unable to open trustetedServersFile: C:\Users\xxx xäx\AppData\Local\Barrier...
someone has similar problems with linux client and chinese symbols i think. New issue do to win client.
Thanks for your help in advance
@albertony commented on GitHub (Dec 9, 2020):
Would you be willing to test this beta build?
https://dev.azure.com/debauchee/Barrier/_build/results?buildId=355&view=artifacts&pathAsName=false&type=publishedArtifacts
If that fixes it, the problem was the nordic character and not the space.
@albertony commented on GitHub (Dec 9, 2020):
Pushed a fix for an additional related issue; when enabling the drag-drop functionality it would not find the desktop path where it will drop files for the same reason as the previous fix.
Edit: Tracked down another issue, this time in the windows service (deamon) communication. If you want to test your exact case, the beta is here:
https://dev.azure.com/debauchee/Barrier/_build/results?buildId=376&view=artifacts&pathAsName=false&type=publishedArtifactsEdit 2: Aaaaand another issue, this time in the client: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=388&view=artifacts&pathAsName=false&type=publishedArtifacts
PS: The issue were non-ascii characters in user name, space did not seem be problematic.
@Schlunze commented on GitHub (Dec 18, 2020):
Hello albertony
sorry for the late reply. I have tested the build from Edit 2.
The non-ascii character in username does not work in this build.
Here is the log:
...[2020-12-18T11:13:32] NOTE: server fingerprint: 67:44:C8:9F:D8:3F:6E:42:93:2C:4D:60:E5:18:9F:55:11:30:4C:04[2020-12-18T11:13:32] NOTE: trustedServersFilename: C:\Users\xxxxx xäx\AppData\Local\Barrier /SSL/Fingerprints/TrustedServers.txt[2020-12-18T11:13:32] NOTE: Unable to open trustedServersFile: C:\Users\xxxxx xäx\AppData\Local\Barrier /SSL/Fingerprints/TrustedServers.txt[2020-12-18T11:13:32] ERROR: failed to verify server certificate fingerprint...btw thank you for your work :)
@albertony commented on GitHub (Dec 18, 2020):
Thank you for your feedback!
That error is the same as https://github.com/debauchee/barrier/issues/974#issuecomment-744119543 (I think that issue and yours are essentially duplicates, and is about non-ascii characters). I have not been able to reproduce that in my test setup, unfortunately, latest beta works with special characters (and space), but will have another look.
@Schlunze commented on GitHub (Dec 18, 2020):
That build works with non-ascii characters and solved my issue - thank you.
https://dev.azure.com/debauchee/Barrier/_build/results?buildId=396&view=artifacts&pathAsName=false&type=publishedArtifacts
@albertony commented on GitHub (Dec 18, 2020):
Great!!