Re: [qubes-users] Re: Updating Fedora 27 errors in Qubes 4.0?
What I did was in a command window on the template...Qubes 3.2 sudo dnf upgrade --allowerasing --best and note the modules removed. Then I installed the modules in the same window... sudo dnf install puleaudio (I forget their exact names right now, but there were two) This appears to have worked, as I am now running that fedora-28 template for sys-net, sys-firewall, sys-usb etc... with no bootup issues. Just be sure and clone it before you do in case you have to restore it. It still doesn't work with a straight "upgrade" from the VM manager. If this doesn't work for 4... well, that's why you clone it first. On Wed, 1 Aug 2018 09:25:27 -0700 (PDT) sm...@tutamail.com wrote: >While this seems to be a Fedora issue, I am still getting stuck on updating my >now new fedora 28 templates(I had to reinstall my Qubes OS due to a crash). It >appears that not being able to update pulse audio is preventing all the other >updates in my Fedora 28 template. > >Is there a recommended solution? > >I am a newbie so any basic commands would be surely appreciated > >Thx > -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180801122821.5815cc14%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 3840x2160 Resolution - How to change: Icon, Windows and Text Sizes?
Hi, On 08/01/2018 07:15 PM, Daniil .Travnikov wrote: > Hi, > > I bought Oryx Pro recently which has 3840x2160 resolution. > > > Do you know how to change in Dom0 Windows, Texts and Icon sizes? Maybe > existing some software for this options? Or it could be done in setings > somwhere? This may help: https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md > > > Screenshot of my situation: > https://drive.google.com/open?id=1V8Yg2nGd5A44laCGwMvAo71kHxb5DCqi > -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/54ea1430-9954-3c22-9f5f-7d4ba9986fee%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Dell Latitude E6340
-- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAHfYbWTLHnDyow7kbU7zevseef5xO6azS8AnmgPWEMB7KTnRrQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Latitude_E6430-20180801-224137.yml Description: application/yaml
[qubes-users] HCL - Dell Latitude E6430
This replaces previous email with wrong laptop model number. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAHfYbWQyGvA9m3%3DkSqFebzYPuy%3DntixAGYZQVxLPY5N5rAVcyw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Latitude_E6430-20180801-224137.yml Description: application/yaml
[qubes-users] HCL - Dell Latitude E6430
Third attempt with more information -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAHfYbWQqg5Z5CpTM06vuO%3DCurReJtrt4wBnL5FrnDe46mTT-OQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Latitude_E6430-20180801-224137.yml Description: application/yaml
Re: [qubes-users] Re: Qubes Routing and NAT
On Wednesday, August 1, 2018 at 6:46:00 PM UTC+10, Unman wrote: > On Mon, Jul 30, 2018 at 10:41:30PM -0700, 'Epinsion Polickye' via qubes-users > wrote: > > On Tuesday, July 31, 2018 at 12:03:45 PM UTC+10, Epinsion Polickye wrote: > > > Hi All, > > > > > > I've been following this guide to set up routing and NAT to an internal > > > machine: https://www.qubes-os.org/doc/firewall/ > > > > > > sys-net and my machines are currently working on the internal network, > > > and the internet perfectly outbound, but I'm having troubles exposing > > > services from sys-net (which I only intend to do for testing with this > > > VM), or internal VMs (what I actually want to do). > > > > > > My machine is connecting directly to sys-net (no sys-firewall middle man). > > > > > > My first step is to simply run "nc -nlv 444" on sys-net to telnet into it > > > from and internal device, and be able to ping the sys-net machine from an > > > internal device. I'm having issues just at this step however, even if > > > I've disabled nftables and iptables. qvm-ls -n lists a different sys-net > > > ip than what's set up as the internal private address on the network. > > > > > > I can ping from sys-net to a particular machine, but not back to the > > > machine. > > > > > > I suspect I'm misunderstanding networking and firewalls in Qubes. I > > > expect sys-net to function like a router (along with any other > > > intermediary VMs for firewalls, net/vpns and the like), and for the > > > firewalls to be handled by nftables and iptables, which shouldn't > > > function when the services are disabled on systems. > > > > > > Thanks. > > > > And also on VM: sudo iptables -I INPUT -s 10.137.0.5 -j ACCEPT > > > > Your assumptions are quite correct about what should be happening. > You haven't said what Qubes version you have or what template you are > using for sys-newt and sys-firewall. Can you add that? I'm using qubes-4. sys-net and sys-firewall are fedora-26. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/199d85a5-130e-4256-b718-27d0b8371d73%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Routing and NAT
On Wed, Aug 01, 2018 at 03:54:23PM -0700, 'Epinsion Polickye' via qubes-users wrote: > On Wednesday, August 1, 2018 at 6:46:00 PM UTC+10, Unman wrote: > > On Mon, Jul 30, 2018 at 10:41:30PM -0700, 'Epinsion Polickye' via > > qubes-users wrote: > > > On Tuesday, July 31, 2018 at 12:03:45 PM UTC+10, Epinsion Polickye wrote: > > > > Hi All, > > > > > > > > I've been following this guide to set up routing and NAT to an internal > > > > machine: https://www.qubes-os.org/doc/firewall/ > > > > > > > > sys-net and my machines are currently working on the internal network, > > > > and the internet perfectly outbound, but I'm having troubles exposing > > > > services from sys-net (which I only intend to do for testing with this > > > > VM), or internal VMs (what I actually want to do). > > > > > > > > My machine is connecting directly to sys-net (no sys-firewall middle > > > > man). > > > > > > > > My first step is to simply run "nc -nlv 444" on sys-net to telnet into > > > > it from and internal device, and be able to ping the sys-net machine > > > > from an internal device. I'm having issues just at this step however, > > > > even if I've disabled nftables and iptables. qvm-ls -n lists a > > > > different sys-net ip than what's set up as the internal private address > > > > on the network. > > > > > > > > I can ping from sys-net to a particular machine, but not back to the > > > > machine. > > > > > > > > I suspect I'm misunderstanding networking and firewalls in Qubes. I > > > > expect sys-net to function like a router (along with any other > > > > intermediary VMs for firewalls, net/vpns and the like), and for the > > > > firewalls to be handled by nftables and iptables, which shouldn't > > > > function when the services are disabled on systems. > > > > > > > > Thanks. > > > > > > And also on VM: sudo iptables -I INPUT -s 10.137.0.5 -j ACCEPT > > > > > > > Your assumptions are quite correct about what should be happening. > > You haven't said what Qubes version you have or what template you are > > using for sys-newt and sys-firewall. Can you add that? > > I'm using qubes-4. sys-net and sys-firewall are fedora-26. > Fedora uses nftables rather than iptables. If you switched the sys-net and sys-firewall to Debian, I suspect that your existing rules might work. Otherwise recast them in nftables. qvm-ls -n shows the IP address of sys-net within Qubes - not the IP address of the external interface on the network, as you have already noticed. So you will need to open the firewall to allow traffic to tcp 444 on ens5. You can run a sniffer like tcpdump on the external interface of sys-net to make sure that traffic from the local networking is actually arriving. You might find this and the linked projects interesting: https://github.com/QubesOS/qubes-issues/issues/3556 unman -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180802005258.q5dqwotlopl72a3j%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Routing and NAT
On Thursday, August 2, 2018 at 10:53:01 AM UTC+10, Unman wrote: > On Wed, Aug 01, 2018 at 03:54:23PM -0700, 'Epinsion Polickye' via qubes-users > wrote: > > On Wednesday, August 1, 2018 at 6:46:00 PM UTC+10, Unman wrote: > > > On Mon, Jul 30, 2018 at 10:41:30PM -0700, 'Epinsion Polickye' via > > > qubes-users wrote: > > > > On Tuesday, July 31, 2018 at 12:03:45 PM UTC+10, Epinsion Polickye > > > > wrote: > > > > > Hi All, > > > > > > > > > > I've been following this guide to set up routing and NAT to an > > > > > internal machine: https://www.qubes-os.org/doc/firewall/ > > > > > > > > > > sys-net and my machines are currently working on the internal > > > > > network, and the internet perfectly outbound, but I'm having troubles > > > > > exposing services from sys-net (which I only intend to do for testing > > > > > with this VM), or internal VMs (what I actually want to do). > > > > > > > > > > My machine is connecting directly to sys-net (no sys-firewall middle > > > > > man). > > > > > > > > > > My first step is to simply run "nc -nlv 444" on sys-net to telnet > > > > > into it from and internal device, and be able to ping the sys-net > > > > > machine from an internal device. I'm having issues just at this step > > > > > however, even if I've disabled nftables and iptables. qvm-ls -n lists > > > > > a different sys-net ip than what's set up as the internal private > > > > > address on the network. > > > > > > > > > > I can ping from sys-net to a particular machine, but not back to the > > > > > machine. > > > > > > > > > > I suspect I'm misunderstanding networking and firewalls in Qubes. I > > > > > expect sys-net to function like a router (along with any other > > > > > intermediary VMs for firewalls, net/vpns and the like), and for the > > > > > firewalls to be handled by nftables and iptables, which shouldn't > > > > > function when the services are disabled on systems. > > > > > > > > > > Thanks. > > > > > > > > And also on VM: sudo iptables -I INPUT -s 10.137.0.5 -j ACCEPT > > > > > > > > > > Your assumptions are quite correct about what should be happening. > > > You haven't said what Qubes version you have or what template you are > > > using for sys-newt and sys-firewall. Can you add that? > > > > I'm using qubes-4. sys-net and sys-firewall are fedora-26. > > > > Fedora uses nftables rather than iptables. > If you switched the sys-net and sys-firewall to Debian, I suspect that > your existing rules might work. Otherwise recast them in nftables. > > qvm-ls -n shows the IP address of sys-net within Qubes - not the IP > address of the external interface on the network, as you have already > noticed. > So you will need to open the firewall to allow traffic to tcp 444 on > ens5. > You can run a sniffer like tcpdump on the external interface of sys-net > to make sure that traffic from the local networking is actually > arriving. > > You might find this and the linked projects interesting: > https://github.com/QubesOS/qubes-issues/issues/3556 > > unman Thanks for your help and for sharing the link. I'm going to set aside some time to read the Qubes doco on networking, learn nftables and iptables, and read the link. Regardless I've found ssh tunneling from sys-net to be very handy, and could be very useful with ssh jumps if there are intermediary firewalls and network services. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/689fb902-0799-480c-a855-5448f4b8cd9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4, copy/paste not working between AppVM's
Hi, I have a Qubes 4 installation on my laptop, and copy/paste between appVMs is not working. I usually(on other Qubes installations) get an infobox on copy/paste to the clipboard in upper right corner whenever I press the sequence (ctrl-c, ctrl-shift-c) and again in the destination vm (ctrl-shift-v, ctrl-v). But there is nothing and nothing gets copied. I tried the instructions here: https://www.qubes-os.org/doc/copy-paste/ and removed the # on the 2 lines in /etc/qubes/guid.conf to enforce it's usage: secure_copy_sequence = "Ctrl-Shift-c"; secure_pate_sequence = "Ctrl-Shift-v"; I also checked the /etc/qubes-rpc/policy/qubes.ClipboardPaste and ensured that it had the follwoing: dom0 $anyvm ask $anyvm $anyvm ask Restarting the whole laptop, after changes did not help. Am I missing something somewhere, from the switch from 3.2 to 4, or is my install broken? Any ideas are greatly appreciated. Sincerely Max -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/161d6dea-8cbf-4f7b-b4d6-b70db9eae038%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
