search

CasparCG / client

Client software primarily used with the CasparCG Server software for audio and video playout, to control graphics and recording, but it can also be used for other tasks within television broadcast.
https://casparcg.com
GNU General Public License v3.0
278 stars 97 forks source link

MacOS client security challenges and not releasing port 6250 #309

Closed amwtech closed 6 months ago

amwtech commented 7 months ago

Most of the items I checked in the Decmber 2023 build worked perfectly, wit many existing bugs removed. But I did encounter one issue.

When I initially opened the macOS app I received the standard macOS security challenge. I told the OS to enable the app, and provided an admin name and password to confirm the choice. I then received the standard question about enabling network traffic, and I selected the enable option. I tested various functions, noting that audio meters and progress bars in video clips worked.

I closed the client. Later I re-opened the client and I was again challenged about allowing network access. I checked the privacy settings and these reported the network traffic was already allowed for this app. This challenge repeats every time the app is started, and about one occasion in two I also have to confirm that the app is allowed to run.

The audio meters and video clip progress bars no longer functioned. Invetsigations showed that the OSC status data port (6250) was locked with no owner, and a large number of bytes were buffered awaiting collection. The only way the port could be released was a full host re-boot. After the first run of the client app the port is again locked out.

I tested the app using both admin and user accounts, and with and without firewall enabled in both modes. The challenges and locking of port 6250 happened in all combinations of user and firewall enable/disable.

macOS version: 12.7.2 (Monterey) Host hardware: iMac 2019 Intel i9

Andy.

amwtech commented 6 months ago

I tested client 2.3.0 RC 1 built on 9th January on an Intel Mac running macOS 12.7.2

I am pleased to report the new build process created a client that loded correctly on first run, releases the port correctly and re-opens with no security challenges. The Apple certificate also correctly enables the required routes through the OS firewall.

I therefore belive this issue can be closed.

Andy