On 6/4/2018 8:15 AM, Thomas Volkert wrote:
>
>
> On 22.05.2018 00:47, James Almer wrote:
>> On 5/21/2018 11:15 AM, James Almer wrote:
>>> On 5/21/2018 8:27 AM, Thomas Volkert wrote:
Hi,
On 14.05.2018 19:04, Dave Gregory wrote:
> Hi all,
>
> [..comparison with alternativ
On 22.05.2018 00:47, James Almer wrote:
> On 5/21/2018 11:15 AM, James Almer wrote:
>> On 5/21/2018 8:27 AM, Thomas Volkert wrote:
>>> Hi,
>>>
>>> On 14.05.2018 19:04, Dave Gregory wrote:
Hi all,
[..comparison with alternative TLS implementations..]
>>> Ping.
>>>
>>> I still sugges
On 27.05.2018 17:20, Ricardo Constantino wrote:
> On 26 May 2018 at 19:42, Reino Wijnsma wrote:
>
>> On 23-5-2018 2:11, Reino Wijnsma wrote:
>>> On 22-4-2018 14:47, Thomas Volkert wrote:
+enabled mbedtls && { check_pkg_config mbedtls mbedtls
>> mbedtls/x509_crt.h mbedtls_x509_crt
On 27-5-2018 21:23, James Almer wrote:
> Pushed the check_lib() change only, after confirming it's needed for static
> builds of mbedtls.
Thank you, James.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-
On 5/27/2018 12:20 PM, Ricardo Constantino wrote:
> On 26 May 2018 at 19:42, Reino Wijnsma wrote:
>
>> On 23-5-2018 2:11, Reino Wijnsma wrote:
>>> On 22-4-2018 14:47, Thomas Volkert wrote:
+enabled mbedtls && { check_pkg_config mbedtls mbedtls
>> mbedtls/x509_crt.h mbedtls_x509_c
On 26 May 2018 at 19:42, Reino Wijnsma wrote:
> On 23-5-2018 2:11, Reino Wijnsma wrote:
> > On 22-4-2018 14:47, Thomas Volkert wrote:
> >> +enabled mbedtls && { check_pkg_config mbedtls mbedtls
> mbedtls/x509_crt.h mbedtls_x509_crt_init ||
> >> + check_pk
On 23-5-2018 2:11, Reino Wijnsma wrote:
> On 22-4-2018 14:47, Thomas Volkert wrote:
>> +enabled mbedtls && { check_pkg_config mbedtls mbedtls
>> mbedtls/x509_crt.h mbedtls_x509_crt_init ||
>> + check_pkg_config mbedtls mbedtls
>> mbedtls/ssl.h mbedtls_ssl
On 22-4-2018 14:47, Thomas Volkert wrote:
> +enabled mbedtls && { check_pkg_config mbedtls mbedtls
> mbedtls/x509_crt.h mbedtls_x509_crt_init ||
> + check_pkg_config mbedtls mbedtls
> mbedtls/ssl.h mbedtls_ssl_init ||
> + chec
On 5/21/2018 11:15 AM, James Almer wrote:
> On 5/21/2018 8:27 AM, Thomas Volkert wrote:
>> Hi,
>>
>> On 14.05.2018 19:04, Dave Gregory wrote:
>>> Hi all,
>>>
>>> [..comparison with alternative TLS implementations..]
>>
>> Ping.
>>
>> I still suggest to support mbedTLS in FFmpeg because it is especi
On 5/21/2018 8:27 AM, Thomas Volkert wrote:
> Hi,
>
> On 14.05.2018 19:04, Dave Gregory wrote:
>> Hi all,
>>
>> [..comparison with alternative TLS implementations..]
>
> Ping.
>
> I still suggest to support mbedTLS in FFmpeg because it is especially
> interesting for embedded devices.
>
> Best
Hi,
On 14.05.2018 19:04, Dave Gregory wrote:
> Hi all,
>
> [..comparison with alternative TLS implementations..]
Ping.
I still suggest to support mbedTLS in FFmpeg because it is especially
interesting for embedded devices.
Best regards,
Thomas.
___
ff
> Have you considered BearSSL?
Thanks Nicolas; it sounds great but we disregarded it because the web
site declares it to be beta-quality. We will certainly keep an eye on
it.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/
Dave Gregory (2018-05-14):
> First, a bit of context on our motivation. We write software that runs on
> IP cameras to connect them to our cloud service. We started off by
> using GnuTLS to secure our connections but there's very limited disk
> space on the cameras and the relatively large binary f
Hi all,
I am an engineer working at Manything (https://manything.com). We
develop software that allows users to view their security cameras over
the Internet. Thomas has been working with us to develop this mbedTLS
integration.
Thanks for your feedback on his patch; we have run some tests that I
On 24 April 2018 at 07:18, Thomas Volkert wrote:
> On 23.04.2018 21:33, Rostislav Pehlivanov wrote:
> > On 23 April 2018 at 20:16, Thomas Volkert wrote:
> >
> >> On 23.04.2018 11:27, Thomas Volkert wrote:
> >>> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
> 2018-04-22 20:00 GMT+02:00, Nicol
On 23.04.2018 21:33, Rostislav Pehlivanov wrote:
> On 23 April 2018 at 20:16, Thomas Volkert wrote:
>
>> On 23.04.2018 11:27, Thomas Volkert wrote:
>>> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
2018-04-22 20:00 GMT+02:00, Nicolas George :
> Carl Eugen Hoyos (2018-04-22):
>> How do
On 23.04.2018 21:02, James Almer wrote:
> On 4/23/2018 6:27 AM, Thomas Volkert wrote:
>> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
>>> 2018-04-22 20:00 GMT+02:00, Nicolas George :
Carl Eugen Hoyos (2018-04-22):
> How do you detect that this is not the "current version" of mbed?
Is
On 23 April 2018 at 20:16, Thomas Volkert wrote:
>
> On 23.04.2018 11:27, Thomas Volkert wrote:
> > On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
> >> 2018-04-22 20:00 GMT+02:00, Nicolas George :
> >>> Carl Eugen Hoyos (2018-04-22):
> How do you detect that this is not the "current version" o
On Mon, 23 Apr 2018 21:09:09 +0200
Thomas Volkert wrote:
> On 23.04.2018 14:08, Rostislav Pehlivanov wrote:
> > On 23 April 2018 at 10:27, Thomas Volkert wrote:
> >
> >> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
> >>> 2018-04-22 20:00 GMT+02:00, Nicolas George :
> Carl Eugen Hoyos
On 23.04.2018 11:27, Thomas Volkert wrote:
> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
>> 2018-04-22 20:00 GMT+02:00, Nicolas George :
>>> Carl Eugen Hoyos (2018-04-22):
How do you detect that this is not the "current version" of mbed?
>>> Is it really our responsibility?
>> We try to alwa
On 23.04.2018 14:08, Rostislav Pehlivanov wrote:
> On 23 April 2018 at 10:27, Thomas Volkert wrote:
>
>> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
>>> 2018-04-22 20:00 GMT+02:00, Nicolas George :
Carl Eugen Hoyos (2018-04-22):
> How do you detect that this is not the "current version"
On 4/23/2018 6:27 AM, Thomas Volkert wrote:
> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
>> 2018-04-22 20:00 GMT+02:00, Nicolas George :
>>> Carl Eugen Hoyos (2018-04-22):
How do you detect that this is not the "current version" of mbed?
>>> Is it really our responsibility?
>> We try to alwa
On 23 April 2018 at 10:27, Thomas Volkert wrote:
> On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
> > 2018-04-22 20:00 GMT+02:00, Nicolas George :
> >> Carl Eugen Hoyos (2018-04-22):
> >>> How do you detect that this is not the "current version" of mbed?
> >> Is it really our responsibility?
> > We
On 22.04.2018 20:03, Carl Eugen Hoyos wrote:
> 2018-04-22 20:00 GMT+02:00, Nicolas George :
>> Carl Eugen Hoyos (2018-04-22):
>>> How do you detect that this is not the "current version" of mbed?
>> Is it really our responsibility?
> We try to always do it and I believe that allowing LGPL makes
> m
2018-04-22 20:00 GMT+02:00, Nicolas George :
> Carl Eugen Hoyos (2018-04-22):
>> How do you detect that this is not the "current version" of mbed?
>
> Is it really our responsibility?
We try to always do it and I believe that allowing LGPL makes
more sense and less headache: Since we do the checks
Carl Eugen Hoyos (2018-04-22):
> How do you detect that this is not the "current version" of mbed?
Is it really our responsibility?
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@
2018-04-22 14:47 GMT+02:00, Thomas Volkert :
> From: Thomas Volkert
> @@ -1638,6 +1640,7 @@ EXTERNAL_LIBRARY_GPL_LIST="
> libx265
> libxavs
> libxvid
> +mbedtls
How do you detect that this is not the "current version" of mbed?
And why is LGPLv3 not supported?
Please make this
From: Thomas Volkert
---
Changelog | 1 +
configure | 31 ++--
libavformat/Makefile | 1 +
libavformat/rtmpdh.c | 55
libavformat/rtmpdh.h | 5 +
libavformat/tls_mbedtls.c | 351 ++
libavf
On 22.04.2018 01:48, Carl Eugen Hoyos wrote:
> 2018-04-22 1:30 GMT+02:00, Hendrik Leppkes :
>> On Sat, Apr 21, 2018 at 10:15 PM, Carl Eugen Hoyos
>> wrote:
>>> 2018-04-21 21:59 GMT+02:00, Thomas Volkert :
On 21.04.2018 21:46, Carl Eugen Hoyos wrote:
> 2018-04-21 21:37 GMT+02:00, Hen
2018-04-22 1:30 GMT+02:00, Hendrik Leppkes :
> On Sat, Apr 21, 2018 at 10:15 PM, Carl Eugen Hoyos
> wrote:
>> 2018-04-21 21:59 GMT+02:00, Thomas Volkert :
>>> On 21.04.2018 21:46, Carl Eugen Hoyos wrote:
>>>
2018-04-21 21:37 GMT+02:00, Hendrik Leppkes :
>>
> Can you elaborate what you thi
On Sat, Apr 21, 2018 at 10:15 PM, Carl Eugen Hoyos wrote:
> 2018-04-21 21:59 GMT+02:00, Thomas Volkert :
>> On 21.04.2018 21:46, Carl Eugen Hoyos wrote:
>>
>>> 2018-04-21 21:37 GMT+02:00, Hendrik Leppkes :
>
Can you elaborate what you think the problem is?
>>> Given that we allow muxing again
On 22.04.2018 01:33, Thomas Volkert wrote:
> From: Thomas Volkert
>
> ---
> Changelog | 1 +
> configure | 31 ++--
> libavformat/Makefile | 1 +
> libavformat/rtmpdh.c | 55
> libavformat/rtmpdh.h | 5 +
> libavformat/tls_mbedtls.c
From: Thomas Volkert
---
Changelog | 1 +
configure | 31 ++--
libavformat/Makefile | 1 +
libavformat/rtmpdh.c | 55
libavformat/rtmpdh.h | 5 +
libavformat/tls_mbedtls.c | 351 ++
libavf
2018-04-21 21:59 GMT+02:00, Thomas Volkert :
> On 21.04.2018 21:46, Carl Eugen Hoyos wrote:
>
>> 2018-04-21 21:37 GMT+02:00, Hendrik Leppkes :
>>> Can you elaborate what you think the problem is?
>> Given that we allow muxing against gpl and Apache, I believe
>> the patch can be improved.
>
> Okay
On 21.04.2018 21:46, Carl Eugen Hoyos wrote:
> 2018-04-21 21:37 GMT+02:00, Hendrik Leppkes :
>> On Sat, Apr 21, 2018 at 6:18 PM, Carl Eugen Hoyos
>> wrote:
>>> 2018-04-21 16:01 GMT+02:00, Thomas Volkert :
>>>
+++ b/Changelog
@@ -3,6 +3,7 @@ releases are sorted from youngest to oldest.
>
2018-04-21 21:37 GMT+02:00, Hendrik Leppkes :
> On Sat, Apr 21, 2018 at 6:18 PM, Carl Eugen Hoyos
> wrote:
>> 2018-04-21 16:01 GMT+02:00, Thomas Volkert :
>>
>>> +++ b/Changelog
>>> @@ -3,6 +3,7 @@ releases are sorted from youngest to oldest.
>>>
>>> version :
>>> - deblock filter
>>> +- support
On Sat, Apr 21, 2018 at 6:18 PM, Carl Eugen Hoyos wrote:
> 2018-04-21 16:01 GMT+02:00, Thomas Volkert :
>
>> +++ b/Changelog
>> @@ -3,6 +3,7 @@ releases are sorted from youngest to oldest.
>>
>> version :
>> - deblock filter
>> +- support mbedTLS based TLS
>
> From a quick look, I believe this l
2018-04-21 16:01 GMT+02:00, Thomas Volkert :
> +++ b/Changelog
> @@ -3,6 +3,7 @@ releases are sorted from youngest to oldest.
>
> version :
> - deblock filter
> +- support mbedTLS based TLS
From a quick look, I believe this library is not license-compatible,
please solve this before committing.
Thomas Volkert (2018-04-21):
> It needs less memory than other TLS implementations.
> This is especially interesting for embedded systems.
> (There is at least one real project which demands for this.)
Thanks. Do you know how it compares in terms of speed?
Also, did you check bearssl? It has simi
On 21.04.2018 16:05, Nicolas George wrote:
> Thomas Volkert (2018-04-21):
>> +- support mbedTLS based TLS
> What is the benefit?
It needs less memory than other TLS implementations.
This is especially interesting for embedded systems.
(There is at least one real project which demands for this.)
Thomas Volkert (2018-04-21):
> +- support mbedTLS based TLS
What is the benefit?
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpe
From: Thomas Volkert
---
Changelog | 1 +
configure | 31 ++--
libavformat/Makefile | 1 +
libavformat/rtmpdh.c | 55
libavformat/rtmpdh.h | 5 +
libavformat/tls_mbedtls.c | 351 ++
libavf
42 matches
Mail list logo