Re: [FFmpeg-devel] [PATCH v3 2/2] libavformat/vapoursynth: Update to API version 4, load library at runtime

[Stefan Oltmanns via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>]

Am 30.07.24 um 16:12 schrieb Ramiro Polla:
> On Mon, Jul 29, 2024 at 5:56 AM Stefan Oltmanns via ffmpeg-devel
> <ffmpeg-devel@ffmpeg.org> wrote:
>> Am 28.07.24 um 15:15 schrieb Ramiro Polla:
>>> I think calling win32_dlopen() with a full path will be problematic for
>>> systems without KB2533623. win32_dlopen() might need to be fixed in a
>>> separate patch.
>>
>> Yes, win32_dlopen would need to check if a full path is already given
>> and if yes skip all the stuff to determine it's own and system32 path,
>> but instead just use the given parameter directly. To check if it's a
>> full path it should be enough to check if it either starts with "\??\"
>> (NT-style path) or if the second character is ":" (win32 style path).
>>
>> But is this really is needed for an operating system that reached
>> support end over 4 years ago and does not have a security patch applied
>> released over 13 years ago?
>> I don't know what ffmpeg's exact policy is in this case, just asking.
>
> Makes sense. I sent a patchset to clean this, but I haven't been able
> to test on a real Windows system.
>
> I'll test the vapoursynth patches later on Linux.
>

Any progress on this? Anything I can do?

Best regards
Stefan
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".