search for: icecast_admin

Hi all, I apologize for the following questions - some may be more general Linux questions while others hopefully relate directly to Icecast: 1) With regards to the recent buffer-overflow exploit and the recommendation of running icecast as a non-root user, how exactly does one do that? I've changed the UID and GUID of the icecast directory and files and binaries to nobody, but what user

...01:48:55 wuhoo icecast: warning: /etc/hosts.allow, line 1: can't verify hostname: gethostbyname(localhost.localdomain) failed Could any of you inform me what I have done wrong? Included in my /etc/hosts.allow file is the following: ALL:ALL@.princeton.edu icecast: ALL@.princeton.edu,localhost icecast_admin: ALL@.princeton.edu,localhost icecast_client: ALL@.princeton.edu,localhost icecast_source: 1.2.3.4,localhost . . . where 1.2.3.4 corresponds to my actual IP and in my /etc/hosts.deny I have # Mandrake-Security : if you remove this comment, remove the next line too. ALL:ALL@ALL EXCEPT localhost...

...saving the computer the need to look up anything at all. Hope that helps, Harvey > > > Could any of you inform me what I have done wrong? > > Included in my /etc/hosts.allow file is the following: > > ALL:ALL@.princeton.edu > icecast: ALL@.princeton.edu,localhost > icecast_admin: ALL@.princeton.edu,localhost > icecast_client: ALL@.princeton.edu,localhost > icecast_source: 1.2.3.4,localhost > > . > . > . > > > where 1.2.3.4 corresponds to my actual IP > > and in my /etc/hosts.deny I have > > # Mandrake-Security : if you remove thi...

...are the steps I've taken to open access to the web admin interface for icecast. If anyone can find mistakes I have made or a step I have left out please let me know. I have been unable to access the interface. In my hosts.allow I have... ALL: *.mydomain.com In my hosts.deny I have... ALL: ALL icecast_admin: ALL EXCEPT*.mydomain.com In the mount.aut files I have... /group:mygroup /admin:mygroup /oper:mygroup In the groups.aut file I have... mygroup:host Now here am I wondering if you can specify a host name like myhost.mydomain.com? If not, how would icecast be able to identify a remote login to th...

...passed, in case of url backend this is done in the URL query: action (see above) mount (the mount that triggered the action) port (icecast port) client (icecast server name) role username ip agent duration admin for exec they are passed as environment variables: ICECAST_VERSION ICECAST_HOSTNAME ICECAST_ADMIN ICECAST_LOGDIR EVENT_URI EVENT_TRIGGER SOURCE_ACTION CLIENT_IP CLIENT_ROLE CLIENT_USERNAME CLIENT_USERAGENT MOUNT_NAME MOUNT_DESCRIPTION MOUNT_URL MOUNT_GENRE SOURCE_MOUNTPOINT SOURCE_PUBLIC SOURCE_HIDDEN > > Cheers, > Rob Stanford > _______________________________________________ &gt...

Hello, I?d like to use the new event triggers in 2.5, but the docs haven?t been updated yet. I?ve managed to gather from the source that the config xml needs to contain an ?event? node with a ?trigger? attribute, but I don?t know what the trigger options are. Anyone used this or have any idea? Cheers, Rob Stanford

Hi all, I help administer a Linux(RH6.1) box running icecast 1.3.5. I'm going to go ahead and upgrade to 1.3.10 shortly. Recently a user from a strange(to us) dial-in account logged in as operator and issued a shutdown command. I changed the passwords to see if someone in our group had let it out, but the same thing happened two days latter. I'm trying to figure out how this was

Before the official release of icecast2 1.0 (non beta) i would like to see pid file management, ive discussed this before on how to capture the pid, but ended up with alot of bash rigamaroo that mounted to even more headaches. omething in the config file like <pid>/path/to/icecast.pid</pid> I would be willing to donate some bandwidth to xiph, to aleaviate this issue that causes sever

...st", which controls _all_ connections, and kick in before # anything is written or read on the socket. If a connection is denied here # then it's bye bye. If it is allowed then depending on the type of the # connection (admin/client/source), the controls "icecast_client", # "icecast_admin", "icecast_source" describe who gets in. # So to deny all clients except those matching *.se, add # "icecast_client: ALL EXCEPT *.se" to hosts.deny. There are millions of # variations on how to build a complete defence, and it's quite simple too. # libwrap is a very pow...

...", which controls _all_ connections, and kick in before # anything is written or read on the socket. If a connection is denied here # then it's bye bye. If it is allowed then depending on the type of the # connection (admin/client/source), the controls "icecast_client", # "icecast_admin", "icecast_source" describe who gets in. # So to deny all clients except those matching *.se, add # "icecast_client: ALL EXCEPT *.se" to hosts.deny. There are millions of # variations on how to build a complete defence, and it's quite simple too. # libwrap is a very pow...

David Dennis wrote: > welcome to the list. > > Check the archives. > > There you will find about one newbie a month minimum discovering that the > widely distributed and still available shout package version 0.8.0 > is actually deprecated and highly broken in exactly the manner you > describe. > > Thanks but one point I can make is I get the same results when not

...", which controls _all_ connections, and kick in before # anything is written or read on the socket. If a connection is denied here # then it's bye bye. If it is allowed then depending on the type of the # connection (admin/client/source), the controls "icecast_client", # "icecast_admin", "icecast_source" describe who gets in. # So to deny all clients except those matching *.se, add # "icecast_client: ALL EXCEPT *.se" to hosts.deny. There are millions of # variations on how to build a complete defence, and it's quite simple too. # libwrap is a very pow...