Icecast Streaming Media Server

[DJ-Zath]

Hi karl!

is there a way to have Icecast read a file containing a password list for a single mount?

currently, I have it where my DJs all share a single common mount which is SHOUTCAST-enabled and using a single shared password..

I had a problem arise where a scheduled broadcaster forgot to disconnect his stream and it continued on into the next few DAYS completely throwing off the schedule.. I ended up having to completely shut down the system so that I can add him to the perma-ban list (so that Icecast wouldn't see his input)

I tried multi-mounts, but I can't have them "equal" priority into a single broadcast mount.. instead they want to daisy-chain.. and this means one caster is always priority over another.. and, in all, only ONE of them can be shoutcast-enabled.. (the rest has to be icecast)

the situation, though an accident, shows that I have a vunrability in the design.. the solution to this would either be the ability for multiple shoutcast mounts to converge into a single mount.. or a mount that can accept multiple passwords

any ideas?
_________________
-DjZ-

[DJ-Zath]

oh. I see I asked this question before... OOPS!

I completely FORGOT (wow I'm a dork...)


though I didn't understand the instructions..

"a <authentication> tag in the <mount> tag to where the shoutcast is called up.."

that part I understand.. (I think)

what goes inside the <authentication> tag? the password?
can the mount contain multiple auth tags?
_________________
-DjZ-

[karlH]

Without trigging a reload of the xml, the only way to have multiple source passwords for a mount is to use the stream_auth option

<mount>
....
<authentication type="url">
<option name="stream_auth" value="http://...../php" />
</authentication>

the php then decides which passwords are accepted or not. At least that allow for multiple passwords

One option I have in the KH build is to allow a hijack of the stream. This is because a client can be authenticated but still dropped because a mount is already active, however, by returning a header like

icecast-auth-user: hijack

on a stream_auth request, then the new client will be swapped into place and the previous client will be dropped. Obviously, you will want the php to have time slots so that it would reject a reconnection attempt or else you would get a ping pong effect between competing sources.

karl.