#6 m3u problem when login is required

[tda]

Ample is just great. Simple to use and exactly the right product for CISCO NSLU2 :-D

BUT:

When I assign a username and a password in /etc/ample.conf the m3u file does not contain these information. (Which is secure!)

I would prefer it to be more insecure and provide the links to each track *including* login information like
http://myname:mypass@myserver:1234/Jazz/Amy%20Winehouse/index.m3u
pointing to
http://myname:mypass@myserver:1234/Jazz/Amy Winehouse/Amy Winehouse - Back To Black.mp3

Leaving out myname:mypass will prevent my player (amarok) from playing it. (Yep, amarok should rock better here)

Is this a bug? Or a "feature" or just an insecurity request?

Maybe for the sake of insecurity a flag in ample.conf would let the decision to the admin.

Cheers,
Torsten