On 14/04/2026 03:18, Kieran Kunhya via ffmpeg-devel wrote:
On Tue, 14 Apr 2026, 02:11 Kieran Kunhya, <[email protected]> wrote:
On Tue, 14 Apr 2026, 01:51 James Almer via ffmpeg-devel, <
[email protected]> wrote:
On 4/13/2026 9:08 PM, Betchkal, Davyd via ffmpeg-devel wrote:
Thank you for the responses. It is correct to assume the NPS uses your
Windows executable (although I use ffmpeg with Linux at home).
Incidentally we are also restricted from using the Windows Store. So,
to be clear, adding a digital signature is not something that the ffmpeg
developer community can or will support? A definitive answer would be
helpful going forward.
It is something we could support, but as far as I'm aware, the certs
required to sign Windows binaries are not cheap. Sponsoring to cover the
cost would however solve that.
Maybe FFmpeg could self-sign?
When getting a commercial digital signature, I believe there's some form
of identity verification involved. FFmpeg of course does not have a legal
entity to verify.
Kieran
There is apparently a way we could do this:
https://signpath.org
I think to remember them refusing to sign FFmpeg binaries due to the
x264 dual licensing model, and virtually every FFmpeg binary comes with
x264/x265 support.
Timo
_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
