[Icecast] Source can't connect to Icecast with SSL enabled

Philipp Schafft lion at lion.leolix.org
Thu Jan 15 09:00:49 UTC 2015


On Wed, 2015-01-14 at 12:32 +0000, "Thomas B. Rücker" wrote:
> On 01/14/2015 11:59 AM, dtouch3d completely wrote:
> > No I haven't because I thought SSL would be only enabled for the
> > listener auth, not source auth.
> OK, then you should have two separate listener sockets.
> One for SSL and one without.
> Point the source client to the one without.
> Advertize the one with SSL to listeners.

Please note that this is a limitation of HTTP and how it works with TLS.
Not a Icecast limitation. HTTP uses port separation for TLS/non-TLS
unlike e.g. SMTP wich uses a STARTTLS command to upgrade to TLS on the
fly if requested.

 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150115/8470d55e/attachment.sig>

More information about the Icecast mailing list