> I haven't heard of anyone using mysql for anything directly with > icecast (people use it for playlist automation systems external to > icecast, though).mmm, i thought some of the listener authentication has been looked at with this ? ie. listener wants to connect, provides username,passowrd in URL, icecast goes and looks in a MySQL database. Obviously got the wrong end of the stick here, sorry.>> GET /<definable-string-containting-mountpoint> >> Authorisation: Basic <blah> >> Agent: Icecast >> >> Just curious, as it may allow integration some segments of the >> market. > > It isn't clear what you're trying to ask here. All authentication in > icecast (except when in backwards-compatibility modes for other > protocols) in done using HTTP Basic auth.Okies, very much like my comments above, but instead of Icecast connecting to MySQL it makes a HTTP request, with the credentials provided, and gets back, say 200 (OK) or 401 or 404, from the remote HTTP server, thus letting the user listen or not, or sending back 404 or 401 to the client etc. Hope i am being clear here :) ? regards, Andrew.
Hi:>From the News file in the Icecast source tree:Icecast now supports listener authentication. This provides a mechanism for creating/maintaining users and passwords for listeners. Currently, we only have implemented a simple, file-based storage for users and passwords. New authenticators are on the horizon (such as URL-based or possibly MySQL based) As far as I know, no work has actually been done on either of these authentication methods, but I could be wrong. Geoff. -- Geoff Shang <geoff@hitsandpieces.net> Phone: +61-418-96-5590 MSN: geoff@acbradio.org Make sure your E-mail can be read by everyone! http://www.betips.net/etc/evilmail.html Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
On Fri, 2004-12-31 at 00:16, andrew@tranceairwaves.com wrote:> > I haven't heard of anyone using mysql for anything directly with > > icecast (people use it for playlist automation systems external to > > icecast, though). > > mmm, i thought some of the listener authentication has been looked at with > this ? ie. listener wants to connect, provides username,passowrd in URL, > icecast goes and looks in a MySQL database. > > Obviously got the wrong end of the stick here, sorry.The only work that has anything like this is in my branch where I've implemented url auth. It works as-is but I do want to change some of the internal thread parts of it. In theory mysql auth could also be done, but that has not been implemented. karl.
At 06:53 PM 12/30/2004, you wrote:>On Fri, 2004-12-31 at 00:16, andrew@tranceairwaves.com wrote: > > mmm, i thought some of the listener authentication has been looked at with > > this ? ie. listener wants to connect, provides username,passowrd in URL, > > icecast goes and looks in a MySQL database. > >The only work that has anything like this is in my branch where I've >implemented url auth. It works as-is but I do want to change some of >the internal thread parts of it. > >In theory mysql auth could also be done, but that has not been >implemented. > >karl.merging in karl's URL-based auth is on the todo for the next release. There has been quite a number of requests for this, and I think it is about time we deliver on it. I'm pretty sure we'll just do URL based since that provides the most flexibility (and thats what karl has implemented). I don't think there is any reason to provide a "Mysql" authentication mechanism, because that is a fairly trivial thing once URL-based auth is implemented. oddsock