search for: woxi

Hello, I have stumbled upon your email address in my search for finding an answer to a problem I'm looking into for school. I attend the Univ. of Cincinnati and am working on my Senior Design Capstone project. I am working with a local independent radio station, WOXY, which is interested in updating its streaming radio to Icecast. I have taken this project under my wing and have tried

On Mon, 2003-11-03 at 19:54, Dave St John wrote: > Good question Amy, here is a snippet of the icecast2.xml file that i do > believe is for this function > --------------------- > <mount> > <mount-name>/test2</mount-name> > > <username>admin</username> > <password>holycow</password> > >

Good question Amy, here is a snippet of the icecast2.xml file that i do believe is for this function --------------------- <mount> <mount-name>/test2</mount-name> <username>admin</username> <password>holycow</password> <max-listeners>1</max-listeners> <!--

>I can have a look at implementing this when I get chance. That would be great as the devs at shoutcast have absolutely no interest or so it seems in adding this feature, which causes people to rely on 3rd party scripts to handle the authentication, which is shotty at best. <p><p>Dave St John (CEO) Mediacast1.com ----- Original Message ----- From: "Karl Heyes"

Thanks for the tips. I did find a detailed article on how to run Icecast 1.3.x in a chroot jail at incidents.org (actually it's in Google's cache, couldn't find it on incidents.org site anymore): http://216.239.37.100/search?q=cache:8Jnwn-j8Yh4C:www.incidents.org/protect/borland.php+icecast+chroot+jail&hl=en&ie=UTF-8 It doesn't really solve the problem of running Icecast

There's been discussion on the list regarding source authentication schemes, but I haven't yet heard anything or seen anything in the source regarding client authentication (users.aut, groups.aut, mounts.aut). Is this or a similar scheme planned for icecast2 and if so, will it be in the beta release? I'm considering modifying icecast to store it's client authentication info in

Wondering if anyone else is having this problem compiling the latest version in CVS. autogen.sh runs fine, configure runs fine, make fails with the following: gcc -DPACKAGE=\"icecast\" -DVERSION=\"2.0\" -DHAVE_DLFCN_H=1 -DHAVE_IPV6=1 -DSTDC_HEADERS=1 -DHAVE_STDINT_H=1 -DCHUID=1 -DCHROOT=1 -I. -I. -I./net -I./thread -I./avl -I./httpp -I./log -I./timing -g -O20

After reviewing the discussion from early November regarding user authentication and subscription schemes in Icecast, I've been chewing on some ideas to implement this in a flexible way that has benefit to everyone and minimal impact on the core server. Because everyone's subscription/authentication needs are going to differ, it probably is best to keep as much of the auth logic

This may seem simple but I've looked all over and come up with nothing. I'm interested in running Icecast 1.3.12 on port 80 to get around the firewall issue. Obviously it's not prudent to run Icecast at root so I'm wondering is there any way to safely run Icecast on port 80 using either setuid or port redirection? Has anyone accomplished this and if so, how'd you do it?