Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Patch which requires a new library
Date: Thu, 7 Mar 2024 16:06:43 +0100
Message-ID: <CA+ag07YhuZGsnVMAKhPTdk5Ja=PYPO-oKdFgHQ=EpBtMf7TaqQ@mail.gmail.com> (raw)

Hi all!

I would like to contribute a patch that adds sig v4 authentication (
https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html)
to the http module.

This would allow for example to play/store an MPEG DASH content stored on
an S3 Bucket which requires authentication.

I have the code ready, but it requires using
https://github.com/aws/SigV4-for-AWS-IoT-embedded-sdk library (which is
MIT, so there should be no license issues) and I am not sure what is the
best way of adding it to the configuration file and adding the conditional
compile flags to enable the feature or not.

Could anyone give me any pointers on what is the best way of doing this?

Best regards
Sergio
_______________________________________________
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".

             reply	other threads:[~2024-03-07 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 15:06 Sergio Garcia Murillo [this message]
2024-03-07 15:30 ` Kieran Kunhya
2024-03-07 17:16   ` Sergio Garcia Murillo
2024-03-07 17:20     ` Kieran Kunhya
2024-03-07 17:30       ` Sergio Garcia Murillo
2024-03-07 18:02         ` Rémi Denis-Courmont
2024-03-07 20:16           ` Sergio Garcia Murillo
2024-03-07 20:56             ` Kieran Kunhya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+ag07YhuZGsnVMAKhPTdk5Ja=PYPO-oKdFgHQ=EpBtMf7TaqQ@mail.gmail.com' \
    --to=sergio.garcia.murillo@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git