[GH-ISSUE #977] MacOS - Barrier would like to access your photos !? #785

Open
opened 2026-05-05 07:07:09 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @caparomula on GitHub (Dec 8, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/977

I just had a fairly alarming experience. I've been using barrier for quite some time now. I always download the pre-built binary from barrier's github releases page. I'm currently running 2.3.3-release (Juy 14) on MacOS Big Sur on an M1 Macbook Air. I've been using it since the mac arrived a couple weeks ago. Just today, out of the blue, I got one of the MacOS permissions dialogs, saying "Barrier would like to access your photos".

This seems very bad to me. Is the binary on github trojaned?

Originally created by @caparomula on GitHub (Dec 8, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/977 I just had a fairly alarming experience. I've been using barrier for quite some time now. I always download the pre-built binary from barrier's github releases page. I'm currently running 2.3.3-release (Juy 14) on MacOS Big Sur on an M1 Macbook Air. I've been using it since the mac arrived a couple weeks ago. Just today, out of the blue, I got one of the MacOS permissions dialogs, saying "Barrier would like to access your photos". This seems very bad to me. Is the binary on github trojaned?
Author
Owner

@zenspider commented on GitHub (Dec 15, 2020):

For the record, I just installed the same revision on an M1 and on an intel and didn't get that warning on server or client side.

<!-- gh-comment-id:745484401 --> @zenspider commented on GitHub (Dec 15, 2020): For the record, I just installed the same revision on an M1 and on an intel and didn't get that warning on server or client side.
Author
Owner

@caparomula commented on GitHub (Dec 15, 2020):

After that happened I did a clean install of Mac OS Big Sur, installed Little Snitch so I could watch network activity by application, and then installed barrier on this fresh system. I have not seen anything weird since, either. I wonder if there is some scenario in which barrier legitimately attempts to access the file system for anything other than configuration information? I imagine it was a red herring, but it's still odd.

<!-- gh-comment-id:745492343 --> @caparomula commented on GitHub (Dec 15, 2020): After that happened I did a clean install of Mac OS Big Sur, installed Little Snitch so I could watch network activity by application, and then installed barrier on this fresh system. I have not seen anything weird since, either. I wonder if there is some scenario in which barrier legitimately attempts to access the file system for anything other than configuration information? I imagine it was a red herring, but it's still odd.
Author
Owner

@WorkInProgress-Development commented on GitHub (Jan 9, 2021):

Just adding my two cents: if an application tries to access your pictures folder, that permission dialog will occur.
When opening Barrier, going into settings, enabling log to file, and then browsing to your users directory, then the pictures folder, this triggers the permissions request. That doesn't explain why it would happen randomly out of the blue though.

This is true for all applications on macOS, and I've found in the past for some other software that the default folder that opens when you select BROWSE can trigger the permission request. This doesn't seem to be occurring here, as, at least for me, the default location opened is the folder /var/log/

Hope this makes sense.

<!-- gh-comment-id:757155795 --> @WorkInProgress-Development commented on GitHub (Jan 9, 2021): Just adding my two cents: if an application tries to access your pictures folder, that permission dialog will occur. When opening Barrier, going into settings, enabling log to file, and then browsing to your users directory, then the pictures folder, this triggers the permissions request. That doesn't explain why it would happen randomly out of the blue though. This is true for all applications on macOS, and I've found in the past for some other software that the default folder that opens when you select BROWSE can trigger the permission request. This doesn't seem to be occurring here, as, at least for me, the default location opened is the folder /var/log/ Hope this makes sense.
Author
Owner

@Morph-Tollon commented on GitHub (Apr 10, 2024):

I found this issue materialises when accidentally dragging and dropping files from machine 1 to machine two, because barrier needs permission to view the file in order to move it between the two machines, made me crap myself iether way.

<!-- gh-comment-id:2048357919 --> @Morph-Tollon commented on GitHub (Apr 10, 2024): I found this issue materialises when accidentally dragging and dropping files from machine 1 to machine two, because barrier needs permission to view the file in order to move it between the two machines, made me crap myself iether way.
Author
Owner

@arcv commented on GitHub (Dec 13, 2024):

According to logs in my setup, Client crashed and restarted itself then "Request to access Downloads folder" popup shown.

[2024-12-13T09:34:29] ERROR: exception on thread 0x00000004:
libc++abi: terminating due to uncaught exception of type std::runtime_error: failed to get file size
[2024-12-13T09:34:29] ERROR: process exited with error code: 6
[2024-12-13T09:34:29] INFO: detected process not running, auto restarting

[2024-12-13T09:34:30] INFO: starting client
[2024-12-13T09:34:30] INFO: config file: /private/var/folders/18/yccyv73n1lx3r1zf_88t10_c0000gn/T/Barrier.xIpMcp
[2024-12-13T09:34:30] INFO: log level: INFO
[2024-12-13T09:34:30] INFO: drag and drop enabled
[2024-12-13T09:34:30] NOTE: started client

This is the first time I get this popup for a year Barrier usage. Could be related to Clipboard copy-paste.

<!-- gh-comment-id:2540684341 --> @arcv commented on GitHub (Dec 13, 2024): According to logs in my setup, Client crashed and restarted itself then "Request to access Downloads folder" popup shown. > [2024-12-13T09:34:29] ERROR: exception on thread 0x00000004: <unknown> > libc++abi: terminating due to uncaught exception of type std::runtime_error: failed to get file size > [2024-12-13T09:34:29] ERROR: process exited with error code: 6 > [2024-12-13T09:34:29] INFO: detected process not running, auto restarting > > [2024-12-13T09:34:30] INFO: starting client > [2024-12-13T09:34:30] INFO: config file: /private/var/folders/18/yccyv73n1lx3r1zf_88t10_c0000gn/T/Barrier.xIpMcp > [2024-12-13T09:34:30] INFO: log level: INFO > [2024-12-13T09:34:30] INFO: drag and drop enabled > [2024-12-13T09:34:30] NOTE: started client This is the first time I get this popup for a year Barrier usage. Could be related to Clipboard copy-paste.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#785
No description provided.