Icecast dev - Sep 2006 - URL authentication

In my case that's not needed, but yes it would be really nice if all 
mount options could be retrieved from the database using an 
authenticated URL.

KJ

Stefan de Konink wrote:
> On Fri, 8 Sep 2006, Klaas Jan Wierenga wrote:
>
>   
>> I guess if the <authentication type="url> section could be
used as a
>> top-level tag (instead of  as a sub-tag of <mount>), then  that
could do
>> the trick.  The mount_add URL would be used to check the validity of
>> the/any mountpoint. The listener_add authenticates the users.
>>
>> Would this be hard to implement? It would certainly make administration
>> a lot easier for icecast users that keep mountpoint names, username and
>> passwords in a database.
>>
>> Any help would be appreciated.
>>     
>
> I think the implementation is not that hard, but is this the only thing
> you want to store for your customer, not things like: bandwidth, max
> users?
>
>
> Probably it could be more easy to store all mounts in SQL, and fetch
> info on aauthentication.
>
>
>
> Stefan
>
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/icecast-dev/attachments/20060908/3b95ff2e/attachment.html

Klaas Jan Wierenga wrote:
> 
> In my case that's not needed, but yes it would be really nice if all 
> mount options could be retrieved from the database using an 
> authenticated URL.
The work I have currently extends the auth settings to include source 
authentication, but whether all mount options should be possible to be 
set via the auth engine I'm not sure, certain settings could be like the 
listener timelimit is now.

karl.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The other thing noticed about this is the strange behavior of passwords
that may include non-alphanumeric characters such as !:,.<>/?`~@#$%^&
... Icecast doesn't seem to translate them right, and on the URL line,
as it calls http://username:password@server:port/mount

you can obviously tell that if the password containt any of the above
characters, authorization does not proceed. Is there a work around for
this other than eliminating the characters from being entered as a password?


Sincerely,
Shon Elliott
MiS Productions
http://www.misproductions.com/


Karl Heyes wrote:
> Klaas Jan Wierenga wrote:
>>
>> In my case that's not needed, but yes it would be really nice if
all
>> mount options could be retrieved from the database using an
>> authenticated URL.
> 
> The work I have currently extends the auth settings to include source
> authentication, but whether all mount options should be possible to be
> set via the auth engine I'm not sure, certain settings could be like
the
> listener timelimit is now.
> 
> karl.
> 
> 
> 
> _______________________________________________
> Icecast-dev mailing list
> Icecast-dev@xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)

iD8DBQFFAagRiGOEZDUaLHIRAn51AKCPciXuwKYT4j/qz8XDio+44aTxCwCeMrRI
QD6PzHjarPzKx2HDzsC4hPc=PAGK
-----END PGP SIGNATURE-----

'The work' are you referring to http://svn.xiph.org/icecast/branches/kh
?

Most important is that I shouldn't have to edit the icecast 
configuration file when a new mountpoint needs to be added. Therefor all 
authentication of source and listener should go through the URL's.

KJ

Karl Heyes schreef:
> Klaas Jan Wierenga wrote:
>>
>> In my case that's not needed, but yes it would be really nice if
all
>> mount options could be retrieved from the database using an 
>> authenticated URL.
>
> The work I have currently extends the auth settings to include source 
> authentication, but whether all mount options should be possible to be 
> set via the auth engine I'm not sure, certain settings could be like 
> the listener timelimit is now.
>
> karl.
>
>
>
>
>