>> It would be ideal if icecast would get the credentials from the GET >> parameters, something similar to >> >> http://example.com:8000/mystream?user=username&pass=password >> > > You can do that if you use the URL auth backend: > http://icecast.org/docs/icecast-2.4.1/auth.html#url >Thanks! Appending parameters to the url is possible because it passed to the external url in the mount property, and icecast doesn't mind serving the right mount point. I don't remember seeing this in the docs though, I think it would be good addition. Also, sorry about the HTML, gmail changed the format to "rich text" for some reason. On Tue, Jan 13, 2015 at 6:25 PM, renan jegouzo <renan at aestesis.org> wrote:> Would be better to try directly https protocol, to be more secure.You are right, that would be more secure. The credentials are now sent unencrypted. But this means icecast must support this functionality and I have not seen anything in the docs. Is this supported ?
Fairly certain icecast does support SSL, and if not, you could just use an SSL terminator in front of it. ? Micheil On 13 Jan 2015, at 17:33, dtouch3d completely <dtouch3d at gmail.com> wrote:>>> It would be ideal if icecast would get the credentials from the GET >>> parameters, something similar to >>> >>> http://example.com:8000/mystream?user=username&pass=password >> >> You can do that if you use the URL auth backend: >> http://icecast.org/docs/icecast-2.4.1/auth.html#url > > Thanks! Appending parameters to the url is possible because it passed > to the external url in the mount property, and icecast doesn't mind > serving the right mount point. I don't remember seeing this in the > docs though, I think it would be good addition. > > Also, sorry about the HTML, gmail changed the format to "rich text" > for some reason. > > On Tue, Jan 13, 2015 at 6:25 PM, renan jegouzo <renan at aestesis.org> wrote: >> Would be better to try directly https protocol, to be more secure. > > You are right, that would be more secure. The credentials are now sent > unencrypted. But this means icecast must support this functionality > and I have not seen anything in the docs. Is this supported ? > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev
Thank you, somehow I missed that. On Tue, Jan 13, 2015 at 7:41 PM, Micheil Smith <micheil at brandedcode.com> wrote:> Fairly certain icecast does support SSL, and if not, you could just use an SSL terminator in front of it. > > ? Micheil > > On 13 Jan 2015, at 17:33, dtouch3d completely <dtouch3d at gmail.com> wrote: > >>>> It would be ideal if icecast would get the credentials from the GET >>>> parameters, something similar to >>>> >>>> http://example.com:8000/mystream?user=username&pass=password >>> >>> You can do that if you use the URL auth backend: >>> http://icecast.org/docs/icecast-2.4.1/auth.html#url >> >> Thanks! Appending parameters to the url is possible because it passed >> to the external url in the mount property, and icecast doesn't mind >> serving the right mount point. I don't remember seeing this in the >> docs though, I think it would be good addition. >> >> Also, sorry about the HTML, gmail changed the format to "rich text" >> for some reason. >> >> On Tue, Jan 13, 2015 at 6:25 PM, renan jegouzo <renan at aestesis.org> wrote: >>> Would be better to try directly https protocol, to be more secure. >> >> You are right, that would be more secure. The credentials are now sent >> unencrypted. But this means icecast must support this functionality >> and I have not seen anything in the docs. Is this supported ? >> _______________________________________________ >> Icecast-dev mailing list >> Icecast-dev at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast-dev