23 replies to this topic

[Kollegah]

hallo leute,

 

hab eine kurze frage: besteht die möglichkeit iwie wolfSSL zu installieren?

 

liegt das auf dem feed? wenn ja, wie finde ich es? falls nein, kann das jmd mal hochladen ?

 

vielen dank

[littlesat]

http://www.milosoftw...p?body=dropbear

?

[Kollegah]

wie man etwas über telnet installiert weiß ich.

 

ich wollte nur wissen, ob wolfssl auf dem openpli feed liegt?

 

man benötigt es für den iptvplayer zusammen mit pycurl

[littlesat]

Wieder fuer illegalen iptv! Wolf gibt es nicht im feeds jetzt. Auch kein idee waarum mann es braucht...https://www.wolfssl.com

Edited by littlesat, 4 November 2018 - 08:48.

[Pumuckel]

 

man benötigt es für den iptvplayer zusammen mit pycurl

Was genau funktioniert denn am IPTV/E2i-Player nicht mit OpenPLi? Derzeit kann ich keinen Fehler finden, aber man schaut halt auch nicht alles bzw. man nutzt nicht jedes Feature.

 

 

... Pumuckel

[Kollegah]

es funktioniert grundsätzlich schon alles, aber es soll ja laut dem entwickler dadurch noch besser laufen und schneller sein.

 

man soll pycurl installieren (liegt ja auf dem feed) und neben pycurl ist auch wolfssl in dem paket von sss.

 

deshalb wollte ich mal fragen, ob man es auch einfach auf den openpli feed legen kann

 

dann könnte man alle dateien direkt über den feed laden und nicht über andere links.

Edited by Kollegah, 4 November 2018 - 12:39.

[honda-civic]

Quatsch,bei instalieren des plugins wird alle benotige scipt mitinstalliert

[Kollegah]

aber schau mal in der konfiguration vom ei2player dort gibt es den menüpunkt:

 

"verwende pycurl für http(s) anfragen" ja/nein

 

und pycurl wird standardmäßig nicht installiert, sondern muss nachinstalliert werden. entweder über einen link oder über den openpli feed.

und wenn man es über den link von dem entwickler vom plugin macht wird auch noch wolfssl installiert.

dies soll das plugin noch schneller machen, weil wolfssl tls 1.3 unterstützt, was openssl noch nicht macht und deswegen langsamer ist.

[littlesat]

Dan instellere es ueber den plugin?!

Edited by littlesat, 5 November 2018 - 02:20.

[Kollegah]

mache ich eigentlich nicht so gerne, ich installiere am liebsten alles hier über den feed

[samsamsam]

I think here is some misunderstanding.

libcurl support several different TLS backends.

 

Like OpenSSL, WolfSSL,  PolarSSL (mbed TLS ).

But this backed must be selected at compilation time.

 

PyCurl it is python wrapper for the libcurl. 

 

So, if the libcurl in the OpenPLI repository was compiled with OpenSSL then installing WolfSSL does not change anything.

 

E2iPlayer for web page download can use urllib2 or PyCurl. PyCurl is much faster then urllib2 and  it also support sessions re-using mechanizm.

 

E2iPlayer checks PyCurl version available in the system as follow:

                if verInfo[4] & (1<<7) and verInfo[1].startswith('7.6') and verInfo[5] == 'wolfSSL/3.15.3':

                    pyCurlInstalled = True

and if this diffrent one it will be not used.

 

So, if you installed version from the OpenPli repository then it is not used. This check was added because many Enigma2 distribution have old libcurl and due to this enabling PyCurl couse manny problems.

This check could be relaxed to allow also version with OpenSSL but the feature which is at least needed by the E2iPlayer is AsynchDNS:

 

verInfo[4] & (1<<7

 

Without this DNS requests could not be cancelled and as a consequence it may cause the decoder to hang ups.

 

Now, about WolfSSL - yest right it support TLS 1.3 and some server need TLS 1.3 to be able to connect to them. But this was not main reason why it was used.

OpenSSL v1.1.X and higher also support TLS 1.3, but you can not use two diffrent OpenSSL versions in the same process, due to symbol colissions.

Enigma2 already use OpenSSL 1.X.X or even OpenSSL 0.9.X PyCurl is dynamic module of python imported to Enigma2, so indirectly Enigma2 process use TLS backed needed by libcurl needed by PyCurl.

This was the main reason why WolfSSL was used. With WolfSSL even very old Enigma2 image can support all HTTPS connections.

 

Regards,

SSS

Edited by samsamsam, 6 November 2018 - 09:21.

[littlesat]

So this is the main reason...

With WolfSSL even very old Enigma2 image can support all HTTPS connections.

?

[samsamsam]

Hello,

 

Yes this is the main reason why libcurl was compiled with the WolfSSL as TLS backed (the second reason is support for TLS 1.3) .

New version of WolfSSL could be safty installed on all Enigma2 distributions because normally Enigma2 does not use it and nor Enigma2's components have dependency to it.

Unlike OpenSSL.

 

PyCurl should be used because of performance on client site but it also reduces server load with session reusing mechanism.

 

Regards,

SSS

[WanWizard]

Apart from the fact we don't really care about "old" Enigma's and 10-15 year old hardware, where exactly is libcurl compiled with WolfSSL? If that were the case, WolfSSL would already be in the image as a dependency?

[samsamsam]

I think you  did not read the thread or you did not understand.

 

Apart from the fact we don't really care about "old" Enigma's and 10-15 year old hardware.

 

 

You are not interested, but users which use it are interested, because they do not have possibility to update image because there is no any new images for their hardware.

 

 

If that were the case, WolfSSL would already be in the image as a dependency?

You do not understand. None of Enigma2 distributions use WolfSSL. So, there is no problem with conflicts new version with the old one, because there is no old one.

 

 

 

where exactly is libcurl compiled with WolfSSL

I do not understand your question.

 

As I wrote libcurl support several TLS backends also based on the WolfSSL. So, anyone can compile libcurl with WolfSSL if he want.

 

Regards,

SSS

Edited by samsamsam, 6 November 2018 - 14:09.

[samsamsam]

I only want to clarify why WolfSSL was used by me instead of the OpenSSL, because @Kollegah wrote that this was due to performance. This is not true. 

 

@Kollegah probably thought about much better performance using PyCurl instead of urllib2.

But this much better performance is not directly related to the WolfSSL.

 

From my observation WolfSSL is a little bit slower than OpenSSL at least on STB based on MIPSEL architecture. But the difference is very, very, very small.

 

The WolfSSL was used because there is no symbol conflicts with OpenSSL and it support TLS 1.3 required by some servers and it performace is comparable to the OpenSSL.

 

I my opinion there is no reason to use WolfSSL instead of OpenSSL in the new distribution of the Enigma2. OpenSSL 1.1.X also support TLS 1.3

 

But, in my package for E2iPlayer I am using WolfSSL because I could not use OpenSSL 1.1.X on Enigma2 distro which already have older OpenSSL version.

 

I hope everything is clear now?

Edited by samsamsam, 6 November 2018 - 14:28.

[littlesat]

Now it is clear... but about what 'old' Enigma2 distro's do have old OpenSSL?

[samsamsam]

There are many such distribiutions for example Freebox OpenPLI, OE 2.0 and so on. 

 

But even OpenPLI 6 use OpenSSL 1.0.X without TLS 1.3 support. 

Edited by samsamsam, 6 November 2018 - 15:00.

[WanWizard]

You need at least OpenSSL 1.1.1 for TLS 1.3, current develop uses 1.0.2k-r0.1. Not sure what the current version in sumo is, I'll have to check. 

 

There is a bitbake recipe available for 1.1.1. so if there really is a need for it, we could upgrade to it for OpenPLi 7.

[littlesat]

so if there really is a need for it, we could upgrade to it for OpenPLi 7.

+0,95