13. Nov 2016 02:54 by tas...@openmailbox.org:
> On 11/12/2016 05:47 PM, > hed...@tutanota.com> wrote:
>>
>> I guess the question still stands: is the latest version materially superior
>> to the March 2015 version? (And enough to want to re-create over a dozen
>> proxyVMs?)
>
> Yes, the VPN
On 11/12/2016 05:47 PM, hed...@tutanota.com wrote:
I guess the question still stands: is the latest version materially
superior to the March 2015 version? (And enough to want to re-create
over a dozen proxyVMs?)
Yes, the VPN doc method is better in the sense that it separates packets
12. Nov 2016 20:39 by tas...@openmailbox.org:
>
> By 'template' you mean the setup at my github repo? If you look closely, they
> are 90% the same except the doc version uses rc.local to start the client and
> the one on github creates a systemd service for it. What makes it look
> simpler
On 11/12/2016 06:26 AM, David Hobach wrote:
> I would also advise users *not* to
> rely on firewall settings in Qubes Manager/VM Settings as the options
> are too limited to stop compromised VMs that are supposed to be
confined
> to the VPN tunnel from leaking data to clearnet (e.g. a hostile
> I would also advise users *not* to
> rely on firewall settings in Qubes Manager/VM Settings as the options
> are too limited to stop compromised VMs that are supposed to be
confined
> to the VPN tunnel from leaking data to clearnet (e.g. a hostile access
> point or other upstream node)
> You might get more interest if you explained which features of the AirVPN GUI
> are worth having. The Github README is blank.
>
> I think most openvpn users are content to use the official client since it's
> simpler and better audited. The current fail-close solution has also been
>
Sec Tester:
> On Saturday, 12 November 2016 04:22:37 UTC+10, Chris Laprise wrote:
>>>
>>
>> A tip for stopping DNS leaks with the GUI: You have to run a script like
>> 'qubes-setup-dnat-to-ns' (in Qubes) or 'qubes-vpn-handler.sh' (in the
>> VPN doc) after the client connects or else DNS packets
On 11/11/2016 01:24 PM, David Hobach wrote:
On 11/10/2016 10:07 PM, Chris Laprise wrote:
> On 11/10/2016 01:28 PM, David Hobach wrote:
>> I'd recommend to avoid any tools employing iptables which were not
>> written explicitly for Qubes as well.
>
> This. Or at least don't use them without
On 11/10/2016 10:07 PM, Chris Laprise wrote:
> On 11/10/2016 01:28 PM, David Hobach wrote:
>> I'd recommend to avoid any tools employing iptables which were not
>> written explicitly for Qubes as well.
>
> This. Or at least don't use them without careful inspection.
Might be worth to put some
On 11/11/2016 07:20 AM, Sec Tester wrote:
I have successfully applied the setup and scripting in
https://www.qubes-os.org/doc/vpn/
No more DNS leaks.
This means i can atleast use my vpn, until i find a way to make things work
with the AirVPN GUI.
A tip for stopping DNS leaks with the GUI:
I have successfully applied the setup and scripting in
https://www.qubes-os.org/doc/vpn/
No more DNS leaks.
This means i can atleast use my vpn, until i find a way to make things work
with the AirVPN GUI.
--
You received this message because you are subscribed to the Google Groups
After further testing, more specifically its a DNS IP leak with the AirVPN GUI
with network lock off.
I also leak DNS when running OpenVPN in the VPN-Proxy-VM,
Havent yet applied Qubes scripts to stop leaks.
--
You received this message because you are subscribed to the Google Groups
Thank you Chris & David for the replies.
Unfortunately at this stage no one seems to know a solution. I will try out the
Qubes VPN guide, as i really need to use my vpn. But will miss the AirVPN GUI
features.
I hope in time i'll find a way to secure from leaks while still using the GUI.
On 11/09/2016 01:51 PM, SEC Tester wrote:
Im trying to setup a VPN ProxyVM on Qubes R3.2
==
Here's what works:
==
Ive got AirVPN GUI setup and working on Fedora-23-minimal
My AppVM can proxy through VPN ProxyVM
whatismyip.com shows the VPN IP
14 matches
Mail list logo
