From hoggins at radiom.fr Tue Dec 27 10:46:30 2016 From: hoggins at radiom.fr (Hoggins!) Date: Tue, 27 Dec 2016 11:46:30 +0100 Subject: [Icecast] dir.xiph.org : OPUS stream wrongly identified as Vorbis Message-ID: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> Hello, We started to publish an OPUS stream amongst others on our Icecast streaming server. That's cool, we're muxing it in an Ogg container, it works well ! So this is just a remark : as the Icecast shows its type as "application/ogg", it may be the reason why the Icecast directory shows this as an Ogg Vorbis stream although it's an Ogg OPUS one. Any idea how to correct this ? Also, it's worth noting that Icecast refuses to dynamically update the metadata update on such a mountpoint, responding "Mountpoint will not accept this URL update" / Return Code: 1. I know it's been quite difficult to allow dynamic updates for Ogg Vorbis, but hey, it's working. Whereas it's not with Ogg Opus. Thanks for the help ! Hoggins! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From phschafft at de.loewenfelsen.net Tue Dec 27 11:14:26 2016 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 27 Dec 2016 11:14:26 +0000 Subject: [Icecast] dir.xiph.org : OPUS stream wrongly identified as Vorbis In-Reply-To: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> References: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> Message-ID: <1482837266.2192.8.camel@de.loewenfelsen.net> Good morning, On Tue, 2016-12-27 at 11:46 +0100, Hoggins! wrote: > Hello, > > We started to publish an OPUS stream amongst others on our Icecast > streaming server. That's cool, we're muxing it in an Ogg container, it > works well ! > So this is just a remark : as the Icecast shows its type as > "application/ogg", it may be the reason why the Icecast directory shows > this as an Ogg Vorbis stream although it's an Ogg OPUS one. Ogg/Opus streams are audio/ogg or application/ogg[0]. The codec is given in the codec parameter[0]. It should be listed as 'sub type' on the Icecast status page. > Any idea how to correct this ? Which (exact!) version of Icecast2 you run? What is the URL to your stream? (you can also answer directly to me (but keep general questions to the list) or ask me on IRC[1]) I would have a look at it and see if the stream is valid. > Also, it's worth noting that Icecast refuses to dynamically update the > metadata update on such a mountpoint, responding "Mountpoint will not > accept this URL update" / Return Code: 1. > I know it's been quite difficult to allow dynamic updates for Ogg > Vorbis, but hey, it's working. Whereas it's not with Ogg Opus. This interface is only for ICY streams (MP3 and AAC). For all other streams the metadata is to be send along the data stream as per codec and mapping standard. The API only 'works'[2] for Ogg/Vorbis for historical reasons. Have a nice day. Looking forward to your reply, with best regards, [0] https://wiki.xiph.org/MIMETypesCodecs [1] #icecast on irc.freenode.net [2] It breaks many things like exact timing or bitrate efficiency. Just don't use it. -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- 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: From hoggins at radiom.fr Tue Dec 27 14:52:38 2016 From: hoggins at radiom.fr (Hoggins!) Date: Tue, 27 Dec 2016 15:52:38 +0100 Subject: [Icecast] dir.xiph.org : OPUS stream wrongly identified as Vorbis In-Reply-To: <1482837266.2192.8.camel@de.loewenfelsen.net> References: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> <1482837266.2192.8.camel@de.loewenfelsen.net> Message-ID: Hello Philipp, Thank you for your answers ! Le 27/12/2016 ? 12:14, Philipp Schafft a ?crit : > Good morning, > > On Tue, 2016-12-27 at 11:46 +0100, Hoggins! wrote: >> Hello, >> >> We started to publish an OPUS stream amongst others on our Icecast >> streaming server. That's cool, we're muxing it in an Ogg container, it >> works well ! >> So this is just a remark : as the Icecast shows its type as >> "application/ogg", it may be the reason why the Icecast directory shows >> this as an Ogg Vorbis stream although it's an Ogg OPUS one. > Ogg/Opus streams are audio/ogg or application/ogg[0]. The codec is given > in the codec parameter[0]. It should be listed as 'sub type' on the > Icecast status page. Sniffing what is being sent to the Directory (by using my own little gateway and dumping the contents), I can see that : - for Vorbis streams : - "type" = "application/ogg" - "stype" = "Vorbis" - for OPUS streams : - "type" = "application/ogg" - "stype" = "" That would explain why the Directory assumes that it's also Vorbis. > > >> Any idea how to correct this ? > Which (exact!) version of Icecast2 you run? I'm running 2.4.0-kh3. I know it's not the official stream, but I was guessing these basic functionalities were handled by the main branch. If not, I'll ask somewhere else. > What is the URL to your stream? (you can also answer directly to me (but > keep general questions to the list) or ask me on IRC[1]) I would have a > look at it and see if the stream is valid. The URL is http://live.radiom.fr:80/live600.ogg > > >> Also, it's worth noting that Icecast refuses to dynamically update the >> metadata update on such a mountpoint, responding "Mountpoint will not >> accept this URL update" / Return Code: 1. >> I know it's been quite difficult to allow dynamic updates for Ogg >> Vorbis, but hey, it's working. Whereas it's not with Ogg Opus. > This interface is only for ICY streams (MP3 and AAC). For all other > streams the metadata is to be send along the data stream as per codec > and mapping standard. The API only 'works'[2] for Ogg/Vorbis for > historical reasons. Yes, that's what I read somewhere else. No problem for that, I'll try to have this updated by the app. I'm using GStreamer, but I'm afraid the shout2send element I'm using does not allow to set the currently played title. > > > Have a nice day. Looking forward to your reply, > > with best regards, > > > [0] https://wiki.xiph.org/MIMETypesCodecs > [1] #icecast on irc.freenode.net > [2] It breaks many things like exact timing or bitrate efficiency. Just > don't use it. > > > Thanks ! Hoggins! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From phschafft at de.loewenfelsen.net Tue Dec 27 15:09:33 2016 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 27 Dec 2016 15:09:33 +0000 Subject: [Icecast] dir.xiph.org : OPUS stream wrongly identified as Vorbis In-Reply-To: References: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> <1482837266.2192.8.camel@de.loewenfelsen.net> Message-ID: <1482851373.2192.15.camel@de.loewenfelsen.net> Good afternoon, On Tue, 2016-12-27 at 15:52 +0100, Hoggins! wrote: > Hello Philipp, > > Thank you for your answers ! > > Le 27/12/2016 ? 12:14, Philipp Schafft a ?crit : > > Good morning, > > > > On Tue, 2016-12-27 at 11:46 +0100, Hoggins! wrote: > >> Hello, > >> > >> We started to publish an OPUS stream amongst others on our Icecast > >> streaming server. That's cool, we're muxing it in an Ogg container, it > >> works well ! > >> So this is just a remark : as the Icecast shows its type as > >> "application/ogg", it may be the reason why the Icecast directory shows > >> this as an Ogg Vorbis stream although it's an Ogg OPUS one. > > Ogg/Opus streams are audio/ogg or application/ogg[0]. The codec is given > > in the codec parameter[0]. It should be listed as 'sub type' on the > > Icecast status page. > > Sniffing what is being sent to the Directory (by using my own little > gateway and dumping the contents), I can see that : > - for Vorbis streams : > - "type" = "application/ogg" > - "stype" = "Vorbis" > - for OPUS streams : > - "type" = "application/ogg" > - "stype" = "" > > That would explain why the Directory assumes that it's also Vorbis. Yes, I talked with Thomas. He said that the yp uses the file extention to guess the subtype if stype is empty. If you rename your mount to .opus it should work. Also there seems there was a bug in Icecast to not set the subtype for Opus in Icecast2 2.4.x, I fixed it this morning (will be included in 2.4.4) (2.5.x will include full Ogg/Opus metadata support). > >> Any idea how to correct this ? > > Which (exact!) version of Icecast2 you run? > > I'm running 2.4.0-kh3. I know it's not the official stream, but I was > guessing these basic functionalities were handled by the main branch. If > not, I'll ask somewhere else. -kh is not a branch but a private fork. The Foundation has no control over it nor do any updates on the official Icecast automatically go into that fork. (Also: the code is generally considered incompatible) > > What is the URL to your stream? (you can also answer directly to me (but > > keep general questions to the list) or ask me on IRC[1]) I would have a > > look at it and see if the stream is valid. > > The URL is http://live.radiom.fr:80/live600.ogg Ok. that seems to be fine expect for the notes above and that it does not contain metadata. > >> Also, it's worth noting that Icecast refuses to dynamically update the > >> metadata update on such a mountpoint, responding "Mountpoint will not > >> accept this URL update" / Return Code: 1. > >> I know it's been quite difficult to allow dynamic updates for Ogg > >> Vorbis, but hey, it's working. Whereas it's not with Ogg Opus. > > This interface is only for ICY streams (MP3 and AAC). For all other > > streams the metadata is to be send along the data stream as per codec > > and mapping standard. The API only 'works'[2] for Ogg/Vorbis for > > historical reasons. > > Yes, that's what I read somewhere else. No problem for that, I'll try to > have this updated by the app. > I'm using GStreamer, but I'm afraid the shout2send element I'm using > does not allow to set the currently played title. The metadata is not related to Icecast or libshout at all. They are part of the bitstream as generated by the encoder. Hope that helped you, with best regards, > > [0] https://wiki.xiph.org/MIMETypesCodecs > > [1] #icecast on irc.freenode.net > > [2] It breaks many things like exact timing or bitrate efficiency. Just > > don't use it. -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- 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: From hoggins at radiom.fr Tue Dec 27 15:15:30 2016 From: hoggins at radiom.fr (Hoggins!) Date: Tue, 27 Dec 2016 16:15:30 +0100 Subject: [Icecast] dir.xiph.org : OPUS stream wrongly identified as Vorbis In-Reply-To: <1482851373.2192.15.camel@de.loewenfelsen.net> References: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> <1482837266.2192.8.camel@de.loewenfelsen.net> <1482851373.2192.15.camel@de.loewenfelsen.net> Message-ID: <530c9474-b79c-5157-5dd4-bbf12fe85ccc@radiom.fr> Hello, Le 27/12/2016 ? 16:09, Philipp Schafft a ?crit : > Good afternoon, > > > On Tue, 2016-12-27 at 15:52 +0100, Hoggins! wrote: >> Hello Philipp, >> >> Thank you for your answers ! >> >> Le 27/12/2016 ? 12:14, Philipp Schafft a ?crit : >>> Good morning, >>> >>> On Tue, 2016-12-27 at 11:46 +0100, Hoggins! wrote: >>>> Hello, >>>> >>>> We started to publish an OPUS stream amongst others on our Icecast >>>> streaming server. That's cool, we're muxing it in an Ogg container, it >>>> works well ! >>>> So this is just a remark : as the Icecast shows its type as >>>> "application/ogg", it may be the reason why the Icecast directory shows >>>> this as an Ogg Vorbis stream although it's an Ogg OPUS one. >>> Ogg/Opus streams are audio/ogg or application/ogg[0]. The codec is given >>> in the codec parameter[0]. It should be listed as 'sub type' on the >>> Icecast status page. >> Sniffing what is being sent to the Directory (by using my own little >> gateway and dumping the contents), I can see that : >> - for Vorbis streams : >> - "type" = "application/ogg" >> - "stype" = "Vorbis" >> - for OPUS streams : >> - "type" = "application/ogg" >> - "stype" = "" >> >> That would explain why the Directory assumes that it's also Vorbis. > Yes, I talked with Thomas. He said that the yp uses the file extention > to guess the subtype if stype is empty. If you rename your mount > to .opus it should work. > > Also there seems there was a bug in Icecast to not set the subtype for > Opus in Icecast2 2.4.x, I fixed it this morning (will be included in > 2.4.4) (2.5.x will include full Ogg/Opus metadata support). > > >>>> Any idea how to correct this ? >>> Which (exact!) version of Icecast2 you run? >> I'm running 2.4.0-kh3. I know it's not the official stream, but I was >> guessing these basic functionalities were handled by the main branch. If >> not, I'll ask somewhere else. > -kh is not a branch but a private fork. The Foundation has no control > over it nor do any updates on the official Icecast automatically go into > that fork. (Also: the code is generally considered incompatible) > > >>> What is the URL to your stream? (you can also answer directly to me (but >>> keep general questions to the list) or ask me on IRC[1]) I would have a >>> look at it and see if the stream is valid. >> The URL is http://live.radiom.fr:80/live600.ogg > Ok. that seems to be fine expect for the notes above and that it does > not contain metadata. > > > >>>> Also, it's worth noting that Icecast refuses to dynamically update the >>>> metadata update on such a mountpoint, responding "Mountpoint will not >>>> accept this URL update" / Return Code: 1. >>>> I know it's been quite difficult to allow dynamic updates for Ogg >>>> Vorbis, but hey, it's working. Whereas it's not with Ogg Opus. >>> This interface is only for ICY streams (MP3 and AAC). For all other >>> streams the metadata is to be send along the data stream as per codec >>> and mapping standard. The API only 'works'[2] for Ogg/Vorbis for >>> historical reasons. >> Yes, that's what I read somewhere else. No problem for that, I'll try to >> have this updated by the app. >> I'm using GStreamer, but I'm afraid the shout2send element I'm using >> does not allow to set the currently played title. > The metadata is not related to Icecast or libshout at all. They are part > of the bitstream as generated by the encoder. > > > Hope that helped you, > > with best regards, > > >>> [0] https://wiki.xiph.org/MIMETypesCodecs >>> [1] #icecast on irc.freenode.net >>> [2] It breaks many things like exact timing or bitrate efficiency. Just >>> don't use it. > Very helpful, thanks ! Hoggins! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hoggins at radiom.fr Tue Dec 27 15:16:40 2016 From: hoggins at radiom.fr (Hoggins!) Date: Tue, 27 Dec 2016 16:16:40 +0100 Subject: [Icecast] dir.xiph.org : OPUS stream wrongly identified as Vorbis In-Reply-To: <1482851373.2192.15.camel@de.loewenfelsen.net> References: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> <1482837266.2192.8.camel@de.loewenfelsen.net> <1482851373.2192.15.camel@de.loewenfelsen.net> Message-ID: Yes, Le 27/12/2016 ? 16:09, Philipp Schafft a ?crit : > -kh is not a branch but a private fork. The Foundation has no control > over it nor do any updates on the official Icecast automatically go into > that fork. (Also: the code is generally considered incompatible) I'm only using the -kh fork because it supports the X-Forwarded-For header. Hoggins! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From phschafft at de.loewenfelsen.net Tue Dec 27 16:29:02 2016 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 27 Dec 2016 16:29:02 +0000 Subject: [Icecast] dir.xiph.org : OPUS stream wrongly identified as Vorbis In-Reply-To: References: <50b936a5-87d5-37aa-3531-1df7fca872e3@radiom.fr> <1482837266.2192.8.camel@de.loewenfelsen.net> <1482851373.2192.15.camel@de.loewenfelsen.net> Message-ID: <1482856142.2192.19.camel@de.loewenfelsen.net> Good evening, On Tue, 2016-12-27 at 16:16 +0100, Hoggins! wrote: > Yes, > > Le 27/12/2016 ? 16:09, Philipp Schafft a ?crit : > > -kh is not a branch but a private fork. The Foundation has no control > > over it nor do any updates on the official Icecast automatically go into > > that fork. (Also: the code is generally considered incompatible) > I'm only using the -kh fork because it supports the X-Forwarded-For header. I have a patch adding that to the official Icecast. But that patch is for 2.5.x. Not sure if it applies to 2.4.x (stable). Hm. with best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- 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: From walteryork at hotmail.com Tue Dec 27 20:22:02 2016 From: walteryork at hotmail.com (Walter York) Date: Tue, 27 Dec 2016 20:22:02 +0000 Subject: [Icecast] How to secure IceCast (Secure login page and disable SSL/TLS versions. Message-ID: I have used the options successfully to enable secure streams with icecast. This is so great because I don't have to loose the green lock on pages that have streams... However after reviewing the security, I have the following questions. 1. How do I require the login pop-up to be secure so I don't send creds unencrypted? If the answer is to disable or use firewall to restrict http, will the players still be able to gather meta-data from status-json.xsl unencrypted? 2. How do I restrict the site from using vulnerable protocols such as: SSL and TLS 1.0? I have used the option to restrict ciphers but that does not positively restrict the protocol. Although restricting the list of ciphers can alter the availability of protocol, some of the newer ciphers are backwards compatible to non-secure protocols thus allowing selection to a more vulnerable protocol. I absolutely love being able to use Icecast, which has proven reliable and stable. If I can just flesh out these security concerns, it would make it all the better! -------------- next part -------------- An HTML attachment was scrubbed... URL: