Mathias Gygax wrote:>On Son, Jan 05, 2003 at 08:24:45 +0100, tcheer@gmx.de wrote: > > >>Hi all, >> >> > >hi there, >Hi again...> > > >>1. >>I have just installed ices 0.2.3 and icecast 1.3.12 and I am trying to >>run them. >>In my etc/icecast.const i have kept the 3 default passwords for the >>encoder, admin and oper (hackme) and modified my etc/ices.conf as follow: >>... >> <!-- Encoder password on the icecast server --> >> <Password>hackme</Password> >>... >>But I have the problem that ices fails to run properly due to a bad >>password error >> >>ices.log: >>Error during send: Error opening: No such file or directory >>... >>Error during send: Mount failed on http://127.0.0.1:8000/ices, error: >>Could not login on server. Server message: ERROR - Bad Password >>Error during send: Mount failed on http://127.0.0.1:8000/ices, error: >>Could not login on server. Server message: ERROR - Bad Password >>Error during send: Mount failed on http://127.0.0.1:8000/ices, error: >>Could not login on server. Server message: ERROR - Bad Password >>Error during send: Mount failed on http://127.0.0.1:8000/ices, error: >>Could not login on server. Server message: ERROR - Bad Password >>Too many stream errors, giving up >> >> > >did you compile with -lcrypt? > >in this case you need to generate the crypt(3) (DES) hashes and put them >into icecast.conf, instead of the plaintext password. with ices you can >use the plaintext password. in icecast.conf, there has to be the hash of >the password. > >Yes I did compile with -lcrypt,> > >>2. >>It is sayed that there is a mkpasswd.c file thatcomes with the sources >>for generating crypted passwords, it seems to be missing! >> >> > >you can also generate a pair with "makepasswd --crypt" or with perl. >perl -e 'print crypt("hackme", "icecastrules") . "\n";' (this is >slightly insecure, use a better or more random salt). put the output (13 >chars hash) to the password configurations (e.g. encoder_password) >in icecast.conf. it should work then. > >HTH > >OK I did so and pasted the result (icxDriEO6Fgt.) in the icecast.conf file (and later in both icecast.conf and ices.conf) entries, but the error remains.... :-( BTW, when starting icecast I have the following error message: [05/Jan/2003:21:49:00] ERROR: Bind to udp interface failed, shutting down udp traffic what does it mean? Thank you again for answering and a happy new year.... -- Eric> - turrican >--- >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-request@xiph.org' >containing only the word 'unsubscribe' in the body. No subject is needed. >Unsubscribe messages sent to the list will be ignored/filtered. > > > ><p>--- >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-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> BTW, when starting icecast I have the following error message: > [05/Jan/2003:21:49:00] ERROR: Bind to udp interface failed, shutting > down udp traffic > what does it mean? >No udp traffic of course :-), but what I wanted to know is what is the cause of it , can I just ignore it? does it hav eto deal with my problem? Thanks again -- Eric <p>--- >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-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Sun, Jan 05, 2003 at 09:52:25PM +0100, tcheer@gmx.de wrote:> >you can also generate a pair with "makepasswd --crypt" or with perl. > >perl -e 'print crypt("hackme", "icecastrules") . "\n";' (this is > >slightly insecure, use a better or more random salt). put the output (13 > >chars hash) to the password configurations (e.g. encoder_password) > >in icecast.conf. it should work then. > > OK I did so and pasted the result (icxDriEO6Fgt.) in the icecast.conf > file (and later in both icecast.conf and ices.conf) entries, but the > error remains.... :-(according to FAQ: Q13: What's the story with crypted passwords? A13: Normally, icecast and shoutcast servers keep the passwords uncrypted, either in a configfile, or specified on the command line. This is pretty poor security. Newer versions of icecast provide a configuration option (--with-crypt). With this option, then the passwords in the configuration file (icecast.conf) and the ones specified on the command line, should be crypted. To produce these crypted passwords, use the mkpasswd program distributed with icecast. Be careful in the configuration file not to leave any junk chars after the passwords. remind the last sentence. there should be no junk before and after the encrypted password.> BTW, when starting icecast I have the following error message: > [05/Jan/2003:21:49:00] ERROR: Bind to udp interface failed, shutting > down udp traffic > what does it mean?do you have some other instances of icecast running? i had to kill running instances with the SIGKILL signal. killall -9 icecast hould do the trick. then do a clean restart of icecast.> Thank you again for answering and a happy new year....no problemo. - turrican --- >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-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> > >according to FAQ: > >Q13: What's the story with crypted passwords? >A13: Normally, icecast and shoutcast servers keep the passwords uncrypted, > either in a configfile, or specified on the command line. This is pretty > poor security. Newer versions of icecast provide a configuration option > (--with-crypt). With this option, then the passwords in the configuration > file (icecast.conf) and the ones specified on the command line, should > be crypted. To produce these crypted passwords, use the mkpasswd program > distributed with icecast. Be careful in the configuration file not to > leave any junk chars after the passwords. > >remind the last sentence. there should be no junk before and after the >encrypted password. > >I did. But in the sources i downloaded, there was no mkpasswd prog., i might check it out from their CVS server.> > >>BTW, when starting icecast I have the following error message: >>[05/Jan/2003:21:49:00] ERROR: Bind to udp interface failed, shutting >>down udp traffic >>what does it mean? >> >> > >do you have some other instances of icecast running? > >i had to kill running instances with the SIGKILL signal. > >killall -9 icecast > >should do the trick. then do a clean restart of icecast. > >That was it! <p>--- >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-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.