Examine individual changes
From Gentoo Wiki
This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.
Variables generated for this change
| Variable | Value |
|---|---|
Edit count of the user (user_editcount) | 347 |
Name of the user account (user_name) | 'Trickygnome' |
Age of the user account (user_age) | 100441729 |
Page ID (page_id) | 389904 |
Page namespace (page_namespace) | 2 |
Page title (without namespace) (page_title) | 'Trickygnome/Pulseaudio sandboxing' |
Full page title (page_prefixedtitle) | 'User:Trickygnome/Pulseaudio sandboxing' |
Action (action) | 'edit' |
Edit summary/reason (summary) | '' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | 'PulseAudio run as server by applications that require it. PulseAudio provide additional configuration interface for low-level ALSA system, hence many applications work directly with PulseAudio.
When we run applications under several users (for simple sandboxing) we need several PulseAudio daemons or clients configurations to connect to one daemon.
PulseAudio security model encourage us not to run one daemon under root and not to use direct file access. But instead relay on sockets configure with cookies authentification.
The simpliest way is to run isolated deamon per user this way:
{{FileBox|filename=run_firefox.sh|collapse-output=true|lang=bash|1=
export PULSE_RUNTIME_PATH=/home/ff/pulse
doas -u ff mkdir -p /home/ff/pulse/
doas -u ff /usr/bin/pulseaudio --start
doas -u ff firefox
}}
{{FileBox|filename=/etc/doas.conf|1=
permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/pulseaudio
permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/firefox
}}
To configure audio for "ff" user you may copy ALSA config .asoundrc to /home/ff/ folder or use pulseaudio tools.
We was able to escape pulseaudio configuration and and stich with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing.' |
New page wikitext, after the edit (new_wikitext) | 'PulseAudio run as server by applications that require it. PulseAudio provide additional configuration interface for low-level ALSA system, hence many applications work directly with PulseAudio.
When we run applications under several users (for simple sandboxing) we need several PulseAudio daemons or clients configurations to connect to one daemon.
PulseAudio security model encourage us not to run one daemon under root and not to use direct file access. But instead relay on sockets configure with cookies authentification.
The simpliest way is to run isolated deamon per user this way:
{{FileBox|filename=run_firefox.sh|collapse-output=true|lang=bash|1=
export PULSE_RUNTIME_PATH=/home/ff/pulse
doas -u ff mkdir -p /home/ff/pulse/
doas -u ff /usr/bin/pulseaudio --start
doas -u ff firefox
}}
{{FileBox|filename=/etc/doas.conf|1=
permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/pulseaudio
permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/firefox
}}
To configure audio for "ff" user you may copy ALSA config .asoundrc to /home/ff/ folder or use pulseaudio tools.
We was able to escape PulseAudio configuration and stick with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing where every PulseAudio daemon run isolated.
For less isolated approach see: {{See| https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon }}' |
Unified diff of changes made by edit (edit_diff) | '@@ -21,3 +21,5 @@
To configure audio for "ff" user you may copy ALSA config .asoundrc to /home/ff/ folder or use pulseaudio tools.
-We was able to escape pulseaudio configuration and and stich with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing.
+We was able to escape PulseAudio configuration and stick with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing where every PulseAudio daemon run isolated.
+
+For less isolated approach see: {{See| https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon }}
' |
Old page size (old_size) | 1254 |
Lines added in edit (added_lines) | [
0 => 'We was able to escape PulseAudio configuration and stick with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing where every PulseAudio daemon run isolated.',
1 => '',
2 => 'For less isolated approach see: {{See| https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon }}'
] |
Lines removed in edit (removed_lines) | [
0 => 'We was able to escape pulseaudio configuration and and stich with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing.'
] |
New page text, stripped of any markup (new_text) | 'PulseAudio run as server by applications that require it. PulseAudio provide additional configuration interface for low-level ALSA system, hence many applications work directly with PulseAudio.
When we run applications under several users (for simple sandboxing) we need several PulseAudio daemons or clients configurations to connect to one daemon.
PulseAudio security model encourage us not to run one daemon under root and not to use direct file access. But instead relay on sockets configure with cookies authentification.
The simpliest way is to run isolated deamon per user this way:
FILE run_firefox.sh export PULSE_RUNTIME_PATH=/home/ff/pulse
doas -u ff mkdir -p /home/ff/pulse/
doas -u ff /usr/bin/pulseaudio --start
doas -u ff firefox
FILE /etc/doas.conf permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/pulseaudio
permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/firefox
To configure audio for "ff" user you may copy ALSA config .asoundrc to /home/ff/ folder or use pulseaudio tools.
We was able to escape PulseAudio configuration and stick with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing where every PulseAudio daemon run isolated.
For less isolated approach see: See also https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><p>PulseAudio run as server by applications that require it. PulseAudio provide additional configuration interface for low-level ALSA system, hence many applications work directly with PulseAudio.
</p><p>When we run applications under several users (for simple sandboxing) we need several PulseAudio daemons or clients configurations to connect to one daemon.
PulseAudio security model encourage us not to run one daemon under root and not to use direct file access. But instead relay on sockets configure with cookies authentification.
</p><p>The simpliest way is to run isolated deamon per user this way:
</p>
<div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #54487A">FILE</span> <strong><code style="border: none; background: none; color: #54487A; margin-right: .5em;">run_firefox.sh</code></strong><strong></strong></div> <div class="mw-highlight mw-highlight-lang-bash mw-content-ltr" dir="ltr"><pre><span></span><span class="nb">export</span><span class="w"> </span><span class="nv">PULSE_RUNTIME_PATH</span><span class="o">=</span>/home/ff/pulse
doas<span class="w"> </span>-u<span class="w"> </span>ff<span class="w"> </span>mkdir<span class="w"> </span>-p<span class="w"> </span>/home/ff/pulse/
doas<span class="w"> </span>-u<span class="w"> </span>ff<span class="w"> </span>/usr/bin/pulseaudio<span class="w"> </span>--start
doas<span class="w"> </span>-u<span class="w"> </span>ff<span class="w"> </span>firefox
</pre></div>
<div class="box-caption"><span class="label" style="margin-right: .5em; background-color: #54487A">FILE</span> <strong><code style="border: none; background: none; color: #54487A; margin-right: .5em;">/etc/doas.conf</code></strong><strong></strong></div> <div class="mw-highlight mw-highlight-lang-text mw-content-ltr" dir="ltr"><pre><span></span>permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/pulseaudio
permit setenv { PULSE_RUNTIME_PATH } nopass larry cmd /usr/bin/firefox
</pre></div>
<p><br />
To configure audio for "ff" user you may copy ALSA config .asoundrc to /home/ff/ folder or use pulseaudio tools.
</p><p>We was able to escape PulseAudio configuration and stick with ALSA and able to configure Mozilla Firefox to run over pulseaudio in simple sandboxing where every PulseAudio daemon run isolated.
</p><p>
For less isolated approach see: </p><div class="alert alert-success gw-box" style="padding-top: 8px; padding-bottom: 8px; background-color: #f5f5f5; border-color: #b8adde; color: #4d4370 ;"><strong><i class="fa fa-search-plus"></i> See also</strong><br /> <a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon">https://wiki.gentoo.org/wiki/Simple_sandbox#Configure_Firefox_to_output_sound_to_larry.27s_PulseAudio_daemon</a> </div>
' |
Unix timestamp of change (timestamp) | 1747160730 |