[FFmpeg-user] Resolve (was Re: key frame)

MacFH - C E Macfarlane - News news at macfh.co.uk
Sun Jun 30 01:53:17 EEST 2024


On 29/06/2024 23:30, MediaMouth wrote:
>
>> On Jun 29, 2024, at 18:21, MacFH - C E Macfarlane - News <news at macfh.co.uk> wrote:
>>
>> On 29/06/2024 22:35, Mark Filipak wrote:
>>>
>>> 2 - There is a web site that shows your open ports. I can't remember the
>>> name. Sorry. I did tests to prove open ports are readily seen. I did not
>>> have to reconfigure the router to do the tests. The site uses your IP to
>>> probe.
>>
>> Gibson Research, follow the link to the 'Shields Up!!' Test:
>>
>> http://grc.com/default.htm
>>
>> Note:  You said earlier that outgoing ports are not the problem, but
>> actually they can be  -  how do you think botnet nodes communicate with
>> their control?  On your router, you should have all internet facing
>> ports closed except those that are strictly needed for normal net
>> functionality.
>>
>
> FWIW Resolve uses a database approach to its projects.  (Avid uses files (bins aka .avb files) as does Premiere.  That likely accounts for at least one of the open ports if not more
>
> The database approach is true genius: you get extremely fast, powerful, free open source project sharing.  In the array of tradeoffs between editing systems, this one's a plus for Resolve.  But that benefit can involve open ports, and closing them can undermine its ability to function

So those would be needed for that particular net functionality, and
similarly other systems require particular open ports as well, but that
doesn't alter the fact that any ports that aren't needed should be closed.


More information about the ffmpeg-user mailing list