Marek Marczykowski-Górecki 6139ed59a3 (redo) updates-proxy: explicitly block connection looping back to the proxy IP ... Explicitly block something like "curl http://127.0.0.1:8082" and return error page in this case. This error page is used in Whonix to detect if the proxy is torrified. If not blocked, it may happen that empty response is returned instead of error. See linked ticket for details. This was previously done for 10.137.255.254, but since migration to qrexec-based connection, 127.0.0.1 is used instead. Fixes QubesOS/qubes-issues#1482		2017-09-15 05:00:05 +02:00
..
00notify-hook
30-qubes-external-ip
80-qubes.conf
ip6tables
iptables	network: rewrite qubes-firewall daemon	2016-09-12 05:22:53 +02:00
iptables-updates-proxy
network-manager-prepare-conf-dir
nm-30-qubes.conf
qubes-fix-nm-conf.sh	Revert "network: use drop-ins for NetworkManager configuration (#1176)"	2015-11-28 17:43:15 +01:00
qubes-iptables
qubes-nmhook
qubes-setup-dnat-to-ns	If there is only 1 DNS server make both DNAT rules point to it	2017-03-19 21:56:34 +00:00
setup-ip
show-hide-nm-applet.desktop
show-hide-nm-applet.sh	Clean up early initialization and setup of /rw	2016-10-23 20:19:51 +00:00
tinyproxy-updates.conf
udev-qubes-network.rules
update-proxy-configs	Implement qrexec-based connection to updates proxy	2017-05-26 05:25:29 +02:00
updates-blacklist
vif-qubes-nat.sh
vif-route-qubes