[qubes-users] No wireless network detected inside StandaloneVM
In my standalone VMs one running Kali and one running Kodachi the never detect any wireless network's in my windows 7 standalone VM it shows and detects and connects to the wireless network. If I boot kali or kodachi from the UDB it detects the wireless network fine but inside the qube it does not. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6e7d75e2-51b0-4208-a517-52456522c9fa%40googlegroups.com.
Re: [qubes-users] Is there a Step-by-step?
V C: I am a layman that gets Qubes to work...the only thing different I do different then awokd, is I use a Mac and terminal to create a bootable thumb with .iso. Tons of articles and tutorials...likely not as secure. Default to awokd he/she is smarter... Don't defer to me, I used dd from Linux to make mine! Rufus in Windows might be broken, but the first thing for him to check is that he is running it per the documentation. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a8aaa437-bdf2-764b-36e3-b1e88d14e7c0%40danwin1210.me.
Re: [qubes-users] Autoconnect to VPN not working in fedora based AppVM
On 8/6/19 6:28 PM, 'awokd' via qubes-users wrote: 799: Hello, For my corporate work I am running a custom build AppVM which is based on a fedora-30-minimal package with some additional packages. I am using the gnome network manager applet with the openconnect plugin to connect to our corporate VPN (Cisco Anyconnect). This is working fine, but I would like to have the VPN started as soon as the VM boots up. Normally this can be done, by right clicking network manager icon, choose "Edit Connection" then edit the settings for the Ethernet connection (VM uplink eth0), open the "General Tab" and enable "[x] Automatically connect to vpn" and choose the VPN connection which I have configured. Unfortunately this setting will not survive the boot of the AppVM, therefore I think the setting is saved somewhere where the AppVM has no write possibility and therefore the setting will be forgotten when I shutdown the AppVM. QUESTION: How can I make this change permanent or do you another idea how to launch the VPN connection upon start of the AppVM? I think /rw/config/NM-system-connections is a bind-dir to /etc/NetworkManager/system-connections, which is where network connections usually get saved. You would think the edit you described would be saved in the same place. Try making it, then doing a sudo grep -ris vpnhostname inside /etc to see where it is getting saved. You should then be able to https://www.qubes-os.org/doc/bind-dirs/ it to have it persist. The connection files are plain text so they might give a hint where to look too. You could also maybe put a script command in /rw/config/rc.local to start openconnect. FWIW, I always got erratic behavior from NM's VPN autostart; I don't know if they've fixed that issue. The VPN doc has a section about making NM start the VPN using an external script (its step 4): https://www.qubes-os.org/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-networkmanager -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/74d8038c-44bf-c4a0-e4a8-16cf71d27957%40posteo.net.
Re: [qubes-users] handling DNS resolution when running comercial VPNs
On 8/6/19 7:57 PM, thecodingninjaisb...@gmail.com wrote: Running ```sudo iptables -C FORWARD -o eth0 -j DROP``` throws an error itself: iptables: Bad rule (does matching rule exist in that chain?). So how can this ever run if running it directly in bash from inside the appvm does not work? On Tuesday, August 6, 2019 at 7:47:53 PM UTC-4, thecodingn...@gmail.com wrote: So apparently the tasket repo does not work|out of the box (obviously). Working through everything, now ran into an unfamiliar issue: pre-start firewall check fails with status 1. Looking at the code it seems the firewall rules are not there although firewall service is running actively. Executing the for loop in a standalone bash throws:| | | Fatal:can't open lock file /run/xtables.lock: Permission denied | The file is there, but i'm thinking this denial is purposeful and i prob should not sudo the loop execution. Any advice? FYI, the qubes lists discourage top-posting. Please reply at the bottom. The firewall rules should be in /rw/config/qubes-firewall.d/90_tunnel-restrict. If they're not, this may indicate the setup steps were not followed through to completion (i.e. if you installed to your template, but forgot step 4). -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8a77bc32-2dff-64f6-55fd-0f25acdf5faf%40posteo.net.
[qubes-users] Re: Receive-only email VM
Couldn't you just use a dedicated VM and thunderbird, don't set up outbound in thunderbird? On Tuesday, August 6, 2019 at 1:11:32 AM UTC-5, alex@gmail.com wrote: > > Some time ago there was a post on reddit ( > https://www.reddit.com/r/Qubes/comments/9q76f2/splitmail_setup/) that > described setting up an offline mail vm. Just kill the "send" part there > and you'll get a mail black hole that receivs but never sends. Seems like > this is more or less what you want. > > On Tuesday, August 6, 2019 at 5:06:54 AM UTC+3, redd...@vfemail.net wrote: >> >> In Qubes, is it possible to set up a VM that can receive email, but not >> send information out, via email or otherwise? >> >> The motivation is: Many online accounts rely on an email address to reset >> passwords. However, the VM that handles inbound emails, processes a lot of >> untrusted input. If the VM gets compromised by an attacker, the attacker >> can then send password reset emails and read them. So to defend against >> this, I want to prevent the compromised VM from communicating out the >> contents of these password reset emails. >> >> Specifically: >> 1. Assume the VM is compromised (can't rely on in-VM enforcement >> mechanisms). >> 2. Assume the email provider is not compromised >> >> To further illustrate the problem, here are example setups and why they >> don't work: >> >> Setup 1: Use qubes firewall to restrict to the email provider's server >> and IMAP port. Block UDP requests using qvm-firewall. >> Why it doesn't work: Attacker can create an account on the same email >> provider and connect to their account (the firewall rules will not prevent >> this). They can then sync emails containing any data, to their account. >> >> Setup 2: Like Setup 1, but use POP3. >> Why it doesn't work: Attacker creates account at provider, transmits data >> via POP3 delete operations. >> >> Does anyone have a email setup with this inbound-only property, ideally >> that does not require running their own email server? >> >> Thank you. >> >> >> - >> This free account was provided by VFEmail.net - report spam to >> ab...@vfemail.net >> >> *ONLY AT VFEmail!* - Use our *Metadata Mitigator*™ to keep your email >> out of the NSA's hands! >> $24.95 ONETIME Lifetime accounts with Privacy Features! >> No Bandwidth Quotas! 15GB disk space! >> Commercial and Bulk Mail Options! >> >> -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9973f5d0-72a8-494f-bb6b-65124b247392%40googlegroups.com.
[qubes-users] Re: Runing qubes on macbook air (11 ince) mid 2012
Never seen any body do it...would be cool to see! On Saturday, August 3, 2019 at 1:20:00 PM UTC-5, 27casa...@gmail.com wrote: > > will it work to run qubes on this macbook? > > After all it has a i5 processor 4 gigs of ram. > > In my opinion this is by far the best ultrabook around in this price range. > > Would be grate if some one could tell me. > > Thanks for youre time and support > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ff0b99ee-5b2d-4a31-977f-5dcbf8150a0b%40googlegroups.com.
Re: [qubes-users] Is there a Step-by-step?
I am a layman that gets Qubes to work...the only thing different I do different then awokd, is I use a Mac and terminal to create a bootable thumb with .iso. Tons of articles and tutorials...likely not as secure. Default to awokd he/she is smarter... Other tips: 1) I had to play with my bios to install (F1 and ctrl/shift to enter?) 2) Get a Lenovo or well documented , compatible laptop. Start with that then upgrade if you can/want...Lenovo T450 and 420 has worked for me. Qubes is the only way to go for me...thanks Qubes devs and others! Don't give up... On Tuesday, August 6, 2019 at 1:35:09 AM UTC-5, awokd wrote: > > Ryan Michael: > > > > More details below, but they're irrelevant to my question: is there a > > clear, step-by-step how-to guide for installing qubes? Like, without all > > the jargon and knowledge.. assumptions, I guess? If so, could you please > > link me or help me find it? I'm struggling so much (see below). If one > > doesn't exist, I really think one is crucial to qubes being accessible. > > Despite my research and determination, i'm about to give up, aha. > > https://www.qubes-os.org/doc/installation-guide/ is probably the closest > there is. I gently suggest considering learning a bit of GNU/Linux > first. I went from Windows 7 to a year or two on Debian desktop before > Qubes, but you could also set up an Ubuntu VM in Virtualbox on Windows > to get some practice with it. > > If you want to dive in to Qubes, the abbreviated steps are > -do a full system backup > -download ISO > -copy to USB drive per Rufus screenshot in above link > -boot from USB drive > -follow prompts, noting you can erase your entire hard drive so be sure > to do a full backup first > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/73b32ddc-f33e-4012-ba92-aade50f78dcb%40googlegroups.com.
Re: [qubes-users] handling DNS resolution when running comercial VPNs
Running ```sudo iptables -C FORWARD -o eth0 -j DROP``` throws an error itself: iptables: Bad rule (does matching rule exist in that chain?). So how can this ever run if running it directly in bash from inside the appvm does not work? On Tuesday, August 6, 2019 at 7:47:53 PM UTC-4, thecodingn...@gmail.com wrote: > > So apparently the tasket repo does not work out of the box (obviously). > Working through everything, now ran into an unfamiliar issue: pre-start > firewall check fails with status 1. Looking at the code it seems the > firewall rules are not there although firewall service is running actively. > Executing the for loop in a standalone bash throws: > Fatal: can't open lock file /run/xtables.lock: Permission denied > The file is there, but i'm thinking this denial is purposeful and i prob > should not sudo the loop execution. Any advice? > > > On Tuesday, August 6, 2019 at 11:09:27 AM UTC-4, Chris Laprise wrote: >> >> On 8/6/19 10:42 AM, thecodingn...@gmail.com wrote: >> > Hello, >> > >> > I have a commercial VPN that does not have any options to pass a DNS >> > handling script. Following how i setup my qubes: sys-net <> >> sys-firewall >> > <> VPN <> AppVm. As you see here I've setup a service vm named VPN >> where >> > the VPN software is installed. I've also tried the other variation >> which >> > is to have an additional firewall between VPN and AppVm. Neither setup >> > works for browsing although the VPN is connecting as expected and AppVm >> > can do IP pings (DNS ping for same address fails), but no web browsing >> > is available which i suspect is due to no DNS handling setups. I have >> > spent so much time trying to figure this out that I'm now left >> > frustrated. Is there a way to do this DNS handling at system level >> > rather than relying on VPN software to do that? If so, then how do i go >> > about it? >> > >> > PS: Is there a difference between the two setups at all? what is the >> > advantage of having an additional firewall between VPN and AppVm? >> > >> > OS: Qubes 4 >> > VPN Software: Proprietary based on openvpn >> >> Hi, >> >> There is a VPN guide in the doc section: >> >> https://www.qubes-os.org/doc/vpn/ >> >> The CLI section is a very manual way to do it, but it shows how DNS >> support is implemented in Qubes and provides some Qubes-specific >> firewall protection. The Network Manager section can be useful if your >> VPN provider has instructions for setting up the connection in NM. >> >> A more automated and reliable way to setup VPNs is to use >> Qubes-vpn-support: >> >> https://github.com/tasket/Qubes-vpn-support >> >> Most VPN services that are based on openvpn will offer downloadable >> configuration files for openvpn. You can drop such config files into >> Qubes-vpn-support and they should work. >> >> OTOH, the 'proprietary' VPN apps are not a good fit for Qubes >> networking. You can probably use them in each AppVM where you run your >> browsers or other apps, but they won't handle DNS or firewall security >> properly in a ProxyVM (the kind of 'provides network' VM you setup like >> a firewall). >> >> A separate firewall VM is not required as your ProxyVM will behave just >> like a firewall in Qubes 4. This is assuming you trust the VPN software >> not to be attacked/exploited in some way (and IMO this is a rather low >> risk). >> >> -- >> >> Chris Laprise, tas...@posteo.net >> https://github.com/tasket >> https://twitter.com/ttaskett >> PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 >> > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/59fc239b-3e65-4f80-bc4e-569a44e1fff3%40googlegroups.com.
Re: [qubes-users] handling DNS resolution when running comercial VPNs
So apparently the tasket repo does not work out of the box (obviously). Working through everything, now ran into an unfamiliar issue: pre-start firewall check fails with status 1. Looking at the code it seems the firewall rules are not there although firewall service is running actively. Executing the for loop in a standalone bash throws: Fatal: can't open lock file /run/xtables.lock: Permission denied The file is there, but i'm thinking this denial is purposeful and i prob should not sudo the loop execution. Any advice? On Tuesday, August 6, 2019 at 11:09:27 AM UTC-4, Chris Laprise wrote: > > On 8/6/19 10:42 AM, thecodingn...@gmail.com wrote: > > Hello, > > > > I have a commercial VPN that does not have any options to pass a DNS > > handling script. Following how i setup my qubes: sys-net <> sys-firewall > > <> VPN <> AppVm. As you see here I've setup a service vm named VPN where > > the VPN software is installed. I've also tried the other variation which > > is to have an additional firewall between VPN and AppVm. Neither setup > > works for browsing although the VPN is connecting as expected and AppVm > > can do IP pings (DNS ping for same address fails), but no web browsing > > is available which i suspect is due to no DNS handling setups. I have > > spent so much time trying to figure this out that I'm now left > > frustrated. Is there a way to do this DNS handling at system level > > rather than relying on VPN software to do that? If so, then how do i go > > about it? > > > > PS: Is there a difference between the two setups at all? what is the > > advantage of having an additional firewall between VPN and AppVm? > > > > OS: Qubes 4 > > VPN Software: Proprietary based on openvpn > > Hi, > > There is a VPN guide in the doc section: > > https://www.qubes-os.org/doc/vpn/ > > The CLI section is a very manual way to do it, but it shows how DNS > support is implemented in Qubes and provides some Qubes-specific > firewall protection. The Network Manager section can be useful if your > VPN provider has instructions for setting up the connection in NM. > > A more automated and reliable way to setup VPNs is to use > Qubes-vpn-support: > > https://github.com/tasket/Qubes-vpn-support > > Most VPN services that are based on openvpn will offer downloadable > configuration files for openvpn. You can drop such config files into > Qubes-vpn-support and they should work. > > OTOH, the 'proprietary' VPN apps are not a good fit for Qubes > networking. You can probably use them in each AppVM where you run your > browsers or other apps, but they won't handle DNS or firewall security > properly in a ProxyVM (the kind of 'provides network' VM you setup like > a firewall). > > A separate firewall VM is not required as your ProxyVM will behave just > like a firewall in Qubes 4. This is assuming you trust the VPN software > not to be attacked/exploited in some way (and IMO this is a rather low > risk). > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fe56a8c0-1163-4bbb-b0c5-50aa9b31d1ba%40googlegroups.com.
[qubes-users] Re: [QubesOS/qubes-issues] Support for HiDPI (#1951)
On 8/6/19 9:46 AM, Abdullah Alansari wrote: > 2. I will try to figure out how to use `xrandr` to add a 3840x2160 with 200% > zoom. I did some research before but I couldn't find any fast solutions and > will need to understand `xrandr` more to do what I need. xrandr knows nothing about "200% zoom" it only deals in resolution (e.g. 3840x2160) Your "200% zoom" is implemented by GTK/Gnome and Qt. The easiest way to get there is to use gnome-tweaks and qt5ct. Also: this is an issue tracker for Qubes and since you understand now that it's actually not an issue with Qubes it would be kind if you'd close the issue and move further discussion over to the qubes-users@googlegroups.com mailing list. /Sven -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/18f18291-e844-6836-6271-2be3f3236cf1%40SvenSemmler.org. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Autoconnect to VPN not working in fedora based AppVM
799: > Hello, > > For my corporate work I am running a custom build AppVM which is based on a > fedora-30-minimal package with some additional packages. > I am using the gnome network manager applet with the openconnect plugin to > connect to our corporate VPN (Cisco Anyconnect). > This is working fine, but I would like to have the VPN started as soon as > the VM boots up. > Normally this can be done, by right clicking network manager icon, choose > "Edit Connection" then edit the settings for the Ethernet connection (VM > uplink eth0), open the "General Tab" and enable "[x] Automatically connect > to vpn" and choose the VPN connection which I have configured. > > Unfortunately this setting will not survive the boot of the AppVM, > therefore I think the setting is saved somewhere where the AppVM has no > write possibility and therefore the setting will be forgotten when I > shutdown the AppVM. > > QUESTION: > How can I make this change permanent or do you another idea how to launch > the VPN connection upon start of the AppVM? > I think /rw/config/NM-system-connections is a bind-dir to /etc/NetworkManager/system-connections, which is where network connections usually get saved. You would think the edit you described would be saved in the same place. Try making it, then doing a sudo grep -ris vpnhostname inside /etc to see where it is getting saved. You should then be able to https://www.qubes-os.org/doc/bind-dirs/ it to have it persist. The connection files are plain text so they might give a hint where to look too. You could also maybe put a script command in /rw/config/rc.local to start openconnect. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a481f1ef-e3d0-c288-38d7-3940a747e745%40danwin1210.me.
[qubes-users] Autoconnect to VPN not working in fedora based AppVM
Hello, For my corporate work I am running a custom build AppVM which is based on a fedora-30-minimal package with some additional packages. I am using the gnome network manager applet with the openconnect plugin to connect to our corporate VPN (Cisco Anyconnect). This is working fine, but I would like to have the VPN started as soon as the VM boots up. Normally this can be done, by right clicking network manager icon, choose "Edit Connection" then edit the settings for the Ethernet connection (VM uplink eth0), open the "General Tab" and enable "[x] Automatically connect to vpn" and choose the VPN connection which I have configured. Unfortunately this setting will not survive the boot of the AppVM, therefore I think the setting is saved somewhere where the AppVM has no write possibility and therefore the setting will be forgotten when I shutdown the AppVM. QUESTION: How can I make this change permanent or do you another idea how to launch the VPN connection upon start of the AppVM? - O. PS: those are the steps to build my office AppVM (initiated from dom0): basetemplate=fedora-30-minimal worktemplatevm=t-fedora-30-work WorkAppVM=my-office qvm-clone $basetemplate $worktemplatevm qvm-run --auto --user root --pass-io --no-gui $worktemplatevm \ 'dnf install -y emacs keepass libreoffice gedit gimp gnome-terminal firefox \ nano git mc terminus-fonts less unzip dejavu-sans-fonts pinentry-gtk \ qubes-gpg-split qubes-core-agent-networking qubes-usb-proxy pulseaudio-qubes \ gstreamer gstreamer-plugins-base libffi libpng12 libXScrnSaver libsigc++20 \ pangox-compat xclip iputils iproute \ # qubes-core-agent-qrexec qubes-core-agent-systemd polkit notification-daemon qubes-input-proxy-sender' ### AnyConnect VPN - OpenConnect qvm-run --auto --pass-io --no-gui --user root $worktemplatevm \ 'dnf -y install NetworkManager-openconnect network-manager-applet qubes-core-agent-network-manager \ NetworkManager-openconnect-gnome NetworkManager-vpnc-gnome NetworkManager-openvpn-gnome NetworkManager-openvpn' # Add network-manager to Qubes Settings > Services qvm-service --enable $WorkAppVM network-manager -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2vhk1WGQ9R8qr%2BycqTFhGy%2BVKGguyC0vLQ7NzDeqWJqHg%40mail.gmail.com.
Re: [qubes-users] handling DNS resolution when running comercial VPNs
On 8/6/19 10:42 AM, thecodingninjaisb...@gmail.com wrote: Hello, I have a commercial VPN that does not have any options to pass a DNS handling script. Following how i setup my qubes: sys-net <> sys-firewall <> VPN <> AppVm. As you see here I've setup a service vm named VPN where the VPN software is installed. I've also tried the other variation which is to have an additional firewall between VPN and AppVm. Neither setup works for browsing although the VPN is connecting as expected and AppVm can do IP pings (DNS ping for same address fails), but no web browsing is available which i suspect is due to no DNS handling setups. I have spent so much time trying to figure this out that I'm now left frustrated. Is there a way to do this DNS handling at system level rather than relying on VPN software to do that? If so, then how do i go about it? PS: Is there a difference between the two setups at all? what is the advantage of having an additional firewall between VPN and AppVm? OS: Qubes 4 VPN Software: Proprietary based on openvpn Hi, There is a VPN guide in the doc section: https://www.qubes-os.org/doc/vpn/ The CLI section is a very manual way to do it, but it shows how DNS support is implemented in Qubes and provides some Qubes-specific firewall protection. The Network Manager section can be useful if your VPN provider has instructions for setting up the connection in NM. A more automated and reliable way to setup VPNs is to use Qubes-vpn-support: https://github.com/tasket/Qubes-vpn-support Most VPN services that are based on openvpn will offer downloadable configuration files for openvpn. You can drop such config files into Qubes-vpn-support and they should work. OTOH, the 'proprietary' VPN apps are not a good fit for Qubes networking. You can probably use them in each AppVM where you run your browsers or other apps, but they won't handle DNS or firewall security properly in a ProxyVM (the kind of 'provides network' VM you setup like a firewall). A separate firewall VM is not required as your ProxyVM will behave just like a firewall in Qubes 4. This is assuming you trust the VPN software not to be attacked/exploited in some way (and IMO this is a rather low risk). -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/341bd739-021a-6c80-756c-eb890cde7179%40posteo.net.
[qubes-users] handling DNS resolution when running comercial VPNs
Hello, I have a commercial VPN that does not have any options to pass a DNS handling script. Following how i setup my qubes: sys-net <> sys-firewall <> VPN <> AppVm. As you see here I've setup a service vm named VPN where the VPN software is installed. I've also tried the other variation which is to have an additional firewall between VPN and AppVm. Neither setup works for browsing although the VPN is connecting as expected and AppVm can do IP pings (DNS ping for same address fails), but no web browsing is available which i suspect is due to no DNS handling setups. I have spent so much time trying to figure this out that I'm now left frustrated. Is there a way to do this DNS handling at system level rather than relying on VPN software to do that? If so, then how do i go about it? PS: Is there a difference between the two setups at all? what is the advantage of having an additional firewall between VPN and AppVm? OS: Qubes 4 VPN Software: Proprietary based on openvpn -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4f8203be-70e6-4196-8d35-2f3881f028a7%40googlegroups.com.
[qubes-users] Re: Runing qubes on macbook air (11 ince) mid 2012
Also you can post about your try here :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b526c80a-98f7-4dc7-b14e-ed381c2f389a%40googlegroups.com.
