Bug 75300 - Documentation: native tcp module docs should mention that audio can be played without auth (assuming that is true)
Summary: Documentation: native tcp module docs should mention that audio can be played...
Status: RESOLVED INVALID
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: misc (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-21 06:20 UTC by jonasthiem
Modified: 2014-03-07 11:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description jonasthiem 2014-02-21 06:20:49 UTC
Hi,

Another suggestion for the tcp native section. Someone told me on IRC that simply enabling that module WITHOUT giving anyone auth access as described with the module options will already allow anyone with network access to play audio:

http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#index22h3

However, to a beginner like me that is really not obvious. I thought at first that without auth access, this module would pretty much do nothing for anyone. Assuming this information from IRC is correct, I would suggest the following doc update:

1. Add a note that by simply loading up the module, it is possible to play audio on the server.
2. Add a note that authentication is only required for full control access, not for basic audio playback.

If I was told incorrect things I am very sorry, I'm really just basing those suggestions on what people said in freenode/#pulseaudio. If all of this is incorrect, please consider some other sort of clarification anyway to make this more obvious for pulseaudio noobs like me.
Comment 1 Tanu Kaskinen 2014-03-07 11:36:08 UTC
You were given false information. module-native-protocol-tcp gives either full access to everything or no access at all.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.