[icecast-dev] icecast 2 auth problem with (old?) ices, MuSe

Brendan Cully brendan at xiph.org
Tue Jan 13 04:55:07 PST 2004

On Tuesday, 13 January 2004 at 11:12, Mihai RUSU wrote:
> Hash: SHA1
> Hi Michael and thanks for answer!
> On Tue, 13 Jan 2004, Michael Smith wrote:
> > This shouldn't be being passed to _check_pass_icy() at all - this isn't the 
> > "icy" (shoutcast nasty ugly) protocol at all. We support that (icy) protocol 
> > because it's widely used - but it's a horribly ugly hack to pretend that it's 
> > HTTP-like. We're not adding more not-HTTP-but-somewhat-similar protocols.
> Ok, let me get this straight, its a client bug right ? (ie ices, MuSe) In 
> that case I need to update my ices ? (I thought both ices and MuSe use 
> libshout for client-server low-level comunication in which case this 
> libshout would need to be fixed). I will contact MuSe and ices devs if 
> this is the case... 

ices uses libshout 2 as of ices 0.3. You need to upgrade.

> Another question, if this is some old/broken protocol, is there a libshout
> version that supports some protocol to connect as a source to shoutcast,
> icecast1, icecast2 ?

yes, libshout 2.
--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.

More information about the Icecast-dev mailing list