> Other than the current approach of shipping without SSL support,.
> alternative options are to a) link with another TLS library providing an
> OpenSSL-compatible shim, b) patch the code to link against another TLS.
> library natively, or c) convince Icecast2 developers to relicense to a.
>
Quoting Jamie McClelland (2017-01-26 22:26:10)
> I see that this is an old bug and would really like to see it
> resolved.
>
> I have had mixed success getting apache2 or ngninx to proxy icecast2.
> It makes trouble shooting a lot harder.
>
> And, without be able to access icecast2 over https,
I see that this is an old bug and would really like to see it resolved.
I have had mixed success getting apache2 or ngninx to proxy icecast2. It
makes trouble shooting a lot harder.
And, without be able to access icecast2 over https, we get mixed content
warnings when displaying a stream on an
3 matches
Mail list logo
