--BwCQnh7xodEAoBMC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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...

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.
=20
Conclusion: If you need authentication esound is pretty dull and
even if all the workaround worked, would you trust such a flawed
software?

--=20
Christian

--BwCQnh7xodEAoBMC
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFACuvz0KQix3oyIMcRAoIlAJ9YcBuStIeuxtU7R3sfMH0DWxCk1ACgzmxy
+fOtQxo87kDA2VCBOdXNZDQ=
=53bJ
-----END PGP SIGNATURE-----

--BwCQnh7xodEAoBMC--