https://wiki.archlinux.org/api.php?action=feedcontributions&user=Darioshanghai&feedformat=atomArchWiki - User contributions [en]2024-03-29T13:06:43ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Plex&diff=415508Talk:Plex2016-01-15T18:49:24Z<p>Darioshanghai: /* Outdated page */ new section</p>
<hr />
<div>== Permissions/ACL ==<br />
<br />
I had some trouble figuring out how to allow plex to access media on a removable device mounted in /run/media/<username>.<br />
The solution was adding an extended permission to allow plex to traverse the directory:<br />
# setfacl -m user:plex:--x /run/media/<username><br />
I expect this has to be re-set each time the user directory is created, but thought it might be worth mentioning in the article or at least mentioning here in case it helps anyone else or I forget. [[User:Kit|Kit]] ([[User talk:Kit|talk]]) 02:51, 26 April 2015 (UTC)<br />
<br />
:We're talking about mounting with udisks2, right? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:03, 26 April 2015 (UTC)<br />
<br />
== Plugins directory ==<br />
<br />
Inform {{ic|/opt/plexmediaserver/Resources/Plug-ins}} is better than inform {{ic|$PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR/Plex Media Server/Plug-ins}} only. Moreover, this last "information" is wrong.<br />
<br />
[[User:Alexandre|Alexandre]] ([[User talk:Alexandre|talk]]) 09:13, 2 August 2015 (UTC)<br />
<br />
== Outdated page ==<br />
<br />
This page is currently outdated. There is currently no trace of a plex directory inside /etc/systemd/system, and nowhere else to set things like the plex user. The only configuration file currently available seems to be the, quite bare, /etc/conf.d/plexmediaserver file, and the only way to discover this is by looking inside the package.</div>Darioshanghaihttps://wiki.archlinux.org/index.php?title=Privoxy&diff=283835Privoxy2013-11-21T00:34:55Z<p>Darioshanghai: Switched AdBlocker with Opera's Urlfilter. The second has a working AUR, not so the first one.</p>
<hr />
<div>[[Category:Proxy servers]]<br />
[[it:Privoxy]]<br />
{{Article summary start}}<br />
{{Article summary text|This article explains how to install and configure Privoxy alongside the [[Tor]] network.}}<br />
{{Article summary heading|Required software}}<br />
{{Article summary link|Tor|https://www.torproject.org/download/download.html.en}}<br />
{{Article summary link|Privoxy|http://www.privoxy.org/}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Tor}}<br />
{{Article summary wiki|Polipo}}<br />
{{Article summary end}}<br />
<br />
[http://www.privoxy.org/ Privoxy] is a filtering proxy for the HTTP protocol, frequently used in combination with [[Tor]]. Privoxy is a web proxy with advanced filtering capabilities for protecting privacy, filtering web page content, managing cookies, controlling access, and removing ads, banners, pop-ups, etc. It supports both stand-alone systems and multi-user networks.<br />
<br />
Using Privoxy is necessary when they use a [[Wikipedia:SOCKS|SOCKS]] proxy directly because browsers leak your DNS requests, which reduces your anonymity.<br />
<br />
==Installation and setup==<br />
[[pacman | Install]] the {{Pkg|privoxy}} package from the [[official repositories]].<br />
# pacman -S privoxy<br />
<br />
When Privoxy is used in conjunction with [[Tor]] the two applications need to exchange information through a chain, which requires the specification of forwarding rules.<br />
<br />
{{warning|If you do not want to use Tor or another proxy there is no need to edit {{ic|/etc/privoxy/config}}. In fact, chaining to an invalid target will prevent your browser from opening any website.}}<br />
<br />
Edit your {{ic|/etc/privoxy/config}} file and add this line at the end (be sure to include the . at the end and preserve the file owner and group permissions as {{Ic|privoxy}}):<br />
forward-socks5 / localhost:9050 .<br />
<br />
This example uses the default port used by Tor. If you changed the port number modify the example accordingly. The same basic example is valid for other targets. If you plan on chaining to another proxy specify the method (here [[Wikipedia:SOCKS#SOCKS5|SOCKS5]]) and the port to suit your needs. Refer to section 5 of the manual inside {{ic|/etc/privoxy/config}} for a complete list of options and examples.<br />
<br />
The above will forward all browser traffic through Tor. To only forward .onion sites through Tor, use this instead:<br />
forward-socks4a .onion localhost:9050 .<br />
<br />
To forward .i2p sites through the [[I2P]] router, add the following to {{ic|/etc/privoxy/config}}:<br />
forward .i2p localhost:4444<br />
<br />
Finally, if you plan to make Privoxy available to other computers in your network, just add:<br />
listen-address [SERVER-IP]:[PORT]<br />
<br />
For example:<br />
listen-address 192.168.1.1:8118<br />
<br />
==Ad Blocking with Privoxy==<br />
Using an ad blocking extension in a web browser can increase page load time. Additionally, extensions like AdBlock Plus are not supported by all browsers. A useful alternative is to install system-wide ad blocking by setting a proxy address in your preferred browser.<br />
<br />
Once Privoxy has been installed download and install the Opera urlfilter importer from [[AUR]] (i.e. [https://aur.archlinux.org/packages/blocklist-to-privoxy/?ID=63431 blocklist-to-privoxy]). You can optionally use an [[AUR Helper]] to do so.<br />
<br />
To block tracking via embedded Facebook "Like" button, Twitter "follow", and Google Plus "+1", edit {{ic|/etc/privoxy/user.action}} and add these lines to the end:<br />
{+block-as-image{Facebook "like" and similar tracking URLs.}}<br />
www.facebook.com/(extern|plugins)/(login_status|like(box)?|activity|fan)\.php<br />
platform.twitter.com/widgets/follow_button?<br />
plusone.google.com<br />
<br />
==Usage==<br />
Start the Privoxy service:<br />
# systemctl start privoxy.service<br />
<br />
Enable the Privoxy service at boot:<br />
# systemctl enable privoxy.service<br />
<br />
Configure your program to use Privoxy. The default address is:<br />
localhost:8118<br />
<br />
For Firefox, go to:<br />
Preferences > Advanced > Network > Settings<br />
<br />
For Chromium you can use:<br />
<br />
$ chromium --proxy-server="localhost:8118"<br />
<br />
==Troubleshooting==<br />
If errors appear when accessing {{ic|/var/log/privoxy/}}, user can add the following after {{Ic|/bin/bash}} in {{ic|/etc/rc.d/privoxy}} and then restart privoxy.<br />
if [ ! -d /var/log/privoxy ] then<br />
mkdir /var/log/privoxy<br />
touch /var/log/privoxy/errorfile<br />
touch /var/log/privoxy/logfile<br />
chown -R privoxy:adm /var/log/privoxy<br />
fi<br />
<br />
==External Links==<br />
* [http://www.privoxy.org/ Official Website]<br />
* [http://thestegemans.com/2011/06/03/blocking_ads_on_arch_linux_with_privoxy/ Blocking Ads on Arch Linux with Privoxy]</div>Darioshanghaihttps://wiki.archlinux.org/index.php?title=Polkit&diff=143133Polkit2011-05-29T18:42:25Z<p>Darioshanghai: /* ConsoleKit */</p>
<hr />
<div>[[Category:Security (English)]]<br />
{{i18n|PolicyKit}}<br />
{{Expansion}}<br />
<br />
From [http://hal.freedesktop.org/docs/PolicyKit/introduction.html PolicyKit Library Reference Manual]:<br />
<br />
:''PolicyKit is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes: It is a framework for centralizing the decision making process with respect to granting access to privileged operations for unprivileged applications. PolicyKit is specifically targeting applications in rich desktop environments on multi-user UNIX-like operating systems. It does not imply or rely on any exotic kernel features.''<br />
<br />
PolicyKit is used for controlling system-wide privileges. It provides an organized way for non-privileged processes to communicate with privileged ones. In contrast to systems such as sudo, it does not grant root permission to an entire process, but rather allows a finer level of control of centralized system policy. <br />
<br />
==ConsoleKit==<br />
Please note: to correct issues with automount and shutdown, please check the [[ConsoleKit]] page.<br />
<br />
==Practical examples==<br />
How to let all users in the group "wheel" have the same admin rights as root (so you don't have to enter root password, but the wheel user's password):<br />
<br />
Make a file like:<br />
<br />
/etc/polkit-1/localauthority.conf.d/60-localauthority.conf<br />
<br />
(higher numbers are prioritied over lower ones) containing:<br />
<br />
<pre>[Configuration]<br />
AdminIdentities=unix-user:0;unix-group:wheel<br />
</pre><br />
<br />
To let users alice and bob perform all [[PackageKit]] actions (but not necessarily other PolicyKit actions), make a file in e.g. <br />
<br />
/etc/polkit-1/localauthority/50-local.d/10-my-pkgkit-policy.pkla<br />
<br />
containing<br />
<br />
<pre>[Let Wheel Use PackageKit]<br />
Identity=unix-user:alice;unix-user:bob<br />
Action=org.freedesktop.packagekit.*<br />
ResultAny=no<br />
ResultInactive=no<br />
ResultActive=auth_self_keep<br />
</pre><br />
<br />
(Use the command <code>pkaction</code> to list all actions defined in your system.)</div>Darioshanghaihttps://wiki.archlinux.org/index.php?title=Polkit&diff=143132Polkit2011-05-29T18:41:27Z<p>Darioshanghai: Referencing ConsoleKit to solve automount/shutdown issues.</p>
<hr />
<div>[[Category:Security (English)]]<br />
{{i18n|PolicyKit}}<br />
{{Expansion}}<br />
<br />
From [http://hal.freedesktop.org/docs/PolicyKit/introduction.html PolicyKit Library Reference Manual]:<br />
<br />
:''PolicyKit is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes: It is a framework for centralizing the decision making process with respect to granting access to privileged operations for unprivileged applications. PolicyKit is specifically targeting applications in rich desktop environments on multi-user UNIX-like operating systems. It does not imply or rely on any exotic kernel features.''<br />
<br />
PolicyKit is used for controlling system-wide privileges. It provides an organized way for non-privileged processes to communicate with privileged ones. In contrast to systems such as sudo, it does not grant root permission to an entire process, but rather allows a finer level of control of centralized system policy. <br />
<br />
==ConsoleKit==<br />
Please note: to correct issues with automount and shutdown, please check the ConsoleKit page.<br />
<br />
==Practical examples==<br />
How to let all users in the group "wheel" have the same admin rights as root (so you don't have to enter root password, but the wheel user's password):<br />
<br />
Make a file like:<br />
<br />
/etc/polkit-1/localauthority.conf.d/60-localauthority.conf<br />
<br />
(higher numbers are prioritied over lower ones) containing:<br />
<br />
<pre>[Configuration]<br />
AdminIdentities=unix-user:0;unix-group:wheel<br />
</pre><br />
<br />
To let users alice and bob perform all [[PackageKit]] actions (but not necessarily other PolicyKit actions), make a file in e.g. <br />
<br />
/etc/polkit-1/localauthority/50-local.d/10-my-pkgkit-policy.pkla<br />
<br />
containing<br />
<br />
<pre>[Let Wheel Use PackageKit]<br />
Identity=unix-user:alice;unix-user:bob<br />
Action=org.freedesktop.packagekit.*<br />
ResultAny=no<br />
ResultInactive=no<br />
ResultActive=auth_self_keep<br />
</pre><br />
<br />
(Use the command <code>pkaction</code> to list all actions defined in your system.)</div>Darioshanghai