Timeline for How can I permit SSH connection terminal programs to access Camera?
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 11, 2019 at 19:04 | comment | added | esarkis | Let us continue this discussion in chat. | |
| Dec 11, 2019 at 14:52 | comment | added | esarkis |
Instead of modifying imagesnap I'm trying an alternative better-established command line image tool, FFmpeg. I run it locally from my Terminal and it works as expected. However, via SSH it aborts with code 10780. The command is: ffmpeg -ss 0.5 -f avfoundation -pix_fmt uyvy422 -framerate 30 -i "0" -t 1 -frames:v 1 /Users/esarkis/ffmpegcapture.jpg
|
|
| Dec 11, 2019 at 13:21 | comment | added | jksoegaard | Try modifying imagesnap to save its error messages to a file - then you can see what happens. Might be worth contacting the developer? | |
| Dec 11, 2019 at 12:57 | comment | added | esarkis |
@jksoegaard thanks again for all the help. I ran sudo find / -name mysnap.png so the file was not saved anywhere locally. When I ran '/usr/local/bin/imagesnap' --args '-w 1 /Users/esarkis/Downloads/mysnap.png -v' to save the image to my download folder but there is still no image file.
|
|
| Dec 10, 2019 at 21:43 | comment | added | jksoegaard | You just need to specify the full path to mysnap.png. I..e replace "mysnap.png" in your command line with something like "/Users/myuser/mysnap.png". Then the file should end up in a predictable spot! | |
| Dec 10, 2019 at 16:32 | comment | added | esarkis |
Update: by running open '/usr/local/bin/imagesnap' --args '-w 1 mysnap.png -v', the arguments being the imagesnap commands to take a photo, I notice my MacBook's Camera light turning on. However, searching with find I cannot locate any file matching mysnap.png and without access to the terminal output of imagesnap since it was launched this way I'm unsure how to confirm or deny if the SSH program has access to the Camera. Terminal is still the only entry in "Security & Privacy" => "Camera".
|
|
| Dec 10, 2019 at 16:05 | comment | added | esarkis |
Running open /usr/local/bin/imagesnap opens and closes a terminal on the MacBook display! Thanks for the help. This is progress, so next I will look into how to pass the command-line options via open on SSH to run imagesnap to attempt to use the camera.
|
|
| Dec 10, 2019 at 15:59 | comment | added | jksoegaard | Try just "open /usr/local/bin/imagesnap" -- same problem? | |
| Dec 10, 2019 at 15:46 | comment | added | esarkis |
I've tried running open -a /usr/local/bin/imagesnap /usr/local/bin/imagesnap from my SSH connection and received the following output: LSOpenURLsWithRole() failed for the application /usr/local/bin/imagesnap with error -10810 for the file /usr/local/bin/imagesnap.. My cursory research suggests this involves the Launch Services framework.
|
|
| Dec 10, 2019 at 15:30 | comment | added | jksoegaard | Ah, I see your problem now - please try the suggestion I have added (using the open command to force it opened as a GUI application). | |
| Dec 10, 2019 at 15:30 | history | edited | jksoegaard | CC BY-SA 4.0 |
added 276 characters in body
|
| Dec 10, 2019 at 14:45 | comment | added | esarkis | Yes, my issue is using the Camera from programs over an SSH connection. A local Terminal behaves as expected. I've updated my post to make this as clear as possible. | |
| Dec 10, 2019 at 14:22 | comment | added | nohillside♦ | For sessions logged in from remote (which seems to be what the OP is doing) Terminal isn't involved so granting Camera access to Terminal won't help. | |
| Dec 10, 2019 at 14:13 | history | edited | jksoegaard | CC BY-SA 4.0 |
added 186 characters in body
|
| Dec 10, 2019 at 14:13 | comment | added | jksoegaard | Yes, then you have set everything up correctly! | |
| Dec 10, 2019 at 13:40 | comment | added | esarkis | When viewing System Preferences => Security & Privacy => Camera, only the Terminal appears in the list, and it has been checked off as yes for access to the Camera. I haven't denied SSH programs access to the camera in the past, and don't receive a pop-up requesting Camera access privileges when running the program that attempts to open the Camera via SSH, so Terminal remains the only entry in the Camera privacy list. | |
| Dec 9, 2019 at 23:54 | history | answered | jksoegaard | CC BY-SA 4.0 |