> Wojciech Puchar wrote:
> > does esound has ANY way of authentication?
>
> AFAIK esound puts a cookie into ~/.esd_auth and if a program linked
> against libesd wants to open the audio device, libesd read this
> file and passes it to the server. This means all users would put
> a symlink to ~esd/.esd_auth into their homes and the user esd
> would be running esd. Well, but ~/.esd_auth is created with 0600
> and it's only created when the first request comes in...

i will then do something in Xsession to install that file when user logs
in.

>
> Though, maybe you don't want to share the audio device but have
> each user have his own esd. That should work *but* if you want
> to use a unix socket, it's created as /tmp/.esd/socket and I guess
> it can't handle running more than one esd on a single machine.
>
> Conclusion: If you need authentication esound is pretty dull and
> even if all the workaround worked, would you trust such a flawed
> software?

on local network only - not bad

still better than nasd which has in theory better authentication, which
simply fails to work ;)