[qubes-users] Re: HOWTO: Compiling Kernels for dom0
Le lundi 14 août 2017 00:29:41 UTC+2, Yethal a écrit : > W dniu niedziela, 13 sierpnia 2017 22:45:01 UTC+2 użytkownik Grzesiek > Chodzicki napisał: > > W dniu niedziela, 13 sierpnia 2017 14:17:33 UTC+2 użytkownik Epitre napisał: > > > Le dimanche 13 août 2017 09:41:53 UTC+2, Foppe de Haan a écrit : > > > > On Sunday, August 13, 2017 at 9:38:06 AM UTC+2, Epitre wrote: > > > > > Le dimanche 13 août 2017 09:19:25 UTC+2, Epitre a écrit : > > > > > > Le dimanche 13 août 2017 07:24:29 UTC+2, Foppe de Haan a écrit : > > > > > > > For any newcomers: can you tell me if this covers all the bases? > > > > > > > https://github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md > > > > > > > (or if not, what's missing?) > > > > > > > > > > > > Hi, > > > > > > > > > > > > It seems right for me. Just a a comment for the version in > > > > > > devel-4.11, the last working version (at least for me, and need to > > > > > > be confirmed) is 4.11.8: > > > > > > > > > > > > The 4.11.12 has a Xen bug which has to be fixed and prevent Xen to > > > > > > work. > > > > > > The 4.12.5 has also the same bug but need to have also 3 patches > > > > > > updated. > > > > > > > > > > > > In both cases, qubes-core status: > > > > > > > > > > > > août 11 21:37:07 dom0 startup-misc.sh[2712]: xenstore-write: > > > > > > xs_open: No such file or directory > > > > > > août 11 21:37:07 dom0 startup-misc.sh[2712]: xenstore-write: > > > > > > xs_open: No such file or directory > > > > > > août 11 21:37:07 dom0 startup-misc.sh[2712]: xc: error: Could not > > > > > > obtain handle on privileged command interface (2 = No such file or > > > > > > directory): Internal error > > > > > > août 11 21:37:07 dom0 startup-misc.sh[2712]: libxl: error: > > > > > > libxl.c:116:libxl_ctx_alloc: cannot open libxc handle: No such file > > > > > > or directory > > > > > > août 11 21:37:07 dom0 startup-misc.sh[2712]: cannot init xl context > > > > > > > > > > > > I will dig more into the problem in the next week but if someone > > > > > > would like to test to confirm or not, it would help. > > > > > > > > > > > > Moreover, for those who have problem with NOUVEAU driver (see my > > > > > > first post asking help: > > > > > > https://groups.google.com/d/msg/qubes-devel/koDHzHJICEs/M5B19MBgCgAJ) > > > > > > and their GTX970 with 4G of VRAM, I patched the qubes kernel > > > > > > (https://github.com/fepitre/qubes-linux-kernel) for version 4.9 and > > > > > > 4.11. The major problem is in the computation of VRAM which has > > > > > > been completely remade and solved in kernel 4.12. > > > > > > > > > > Sorry for the quick updates but writing the message it came to mind > > > > > that it would maybe something related to Grub...and yes...I boot the > > > > > my dev machine and I don't know why but the grub conf was badly > > > > > updated... > > > > > > > > > > I can confirm that the lastest working version is 4.11.12. I will > > > > > also update properly my repo for the patches in devel-4.12. > > > > > > > > np. I had a look, but didn't see any error messages akin to yours > > > > (running 4.11.12). 4.12.6 indeed only built for me if I disabled 3 > > > > kernel patches, 1 related to xsa155. > > > > > > Now building and running properly kernel-4.12 is ok. I pushed on my > > > devel-4.12 branch the updated 3 kernel patches who failed at first > > > instance (rewrite in the kernel sources to obtain properly updated lines). > > > > > > We can now go on the next releases (especially if someone like has Ryzen > > > or Kaby Lake CPU or latest NVIDIA cards). > > > > Interestingly enough, your 4.12 branch compiles fine in the AppVM > > previously used to (unsuccessfully) compile Reg's 4.11 kernel. > > Just booted into the 4.12 slim kernel. Works great so far. > I use Reg's slim config as a baseline and then as much stuff I safely could. > Final kernel size is 44mb. I can paste the final config here if anybody's > interested. Hi, I'm interested :) -- 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/2baf3734-c64d-488c-9062-2e47e1decdc3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL Dell Latitude 7480 + dock usb-c problems (dell wd15)
It is a dock in thunderbolt* -- 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/5cdf896e-19c0-46f3-8bed-0372b94ae318%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL Dell Latitude 7480 + dock usb-c problems (dell wd15)
Hi, I have successfully install qubes-os 3.2 and 4.0 on this new laptop, I must build hid_alps for get the touchpad working. All was almost good but, the big big problem, is i can't working with the dock. I don't find how to play correctly with http://www.dell.com/en-us/shop/dell-dock-wd15-with-180w-adapter/apd/450-aeuo/pc-accessories * display output are working, * the network and usb are NOT working, i can't attach them to the sys-usb/sys-net VM, is see sort of 4 "bridges" in devices list, i suppose for usb and network but this is not clear. If I valid the form after enable those bridge, i get an error. Somebody allready get working a such device? Thanks for your help. -- 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/0a5c568a-8abc-410f-a9f6-4a07f4fd8906%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Lenovo ThinkPad T450s 20BX001LUS
Le dimanche 13 août 2017 19:49:50 UTC+2, Malin Fylking a écrit : > Hello, will > https://www.amazon.com/Lenovo-ThinkPad-20BX001LUS-14-Inch-Laptop/dp/B00TO8IYV6 > be able to run qubes? > Best regards Malin yes -- 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/4bdd690c-d824-4af5-b6ba-c46e2279e08c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Xorg and Oom killer, i3
Sorry, and i use last 3.2 version, fully updated, some debian/fedora/whonix qubes. Le samedi 15 juillet 2017 19:55:16 UTC+2, cyrinux a écrit : > Hi, > I have 20gb memory, but I use a lot of VM. > Sometimes xorg is randomly kill. > I would like to protect xorg from being killed. I'm trying to play with > overcommit but is it a good idea? > Must I boot dom0 minimal memory? > > Bonus: after a xorg crash, I can't reconnect to guid daemon. How to do? I use > i3, is it a i3 problem? > Regards -- 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/ac93bc6b-254f-4e39-b0a5-3f05b6576b38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Xorg and Oom killer, i3
Le samedi 15 juillet 2017 20:20:55 UTC+2, Noor Christensen a écrit : > On Sat, Jul 15, 2017 at 10:55:16AM -0700, cyrinux wrote: > > Hi, > > I have 20gb memory, but I use a lot of VM. > > Sometimes xorg is randomly kill. > > I would like to protect xorg from being killed. I'm trying to play with > > overcommit but is it a good idea? > > Must I boot dom0 minimal memory? > > > > Bonus: after a xorg crash, I can't reconnect to guid daemon. How to do? I > > use i3, is it a i3 problem? > > Regards > > What version of Qubes are you running on your dom0? > > By "using a lot of VM", do you mean virtual memory or virtual machines? > For clarity, I will use the term meaning the latter, and "virtual > memory" when referring to the former. > > Just want to make clear since the topic makes it a bit ambiguous :-) > > Is it your dom0 Xorg process that is being killed, or one that is > running in a VM? > > You might want to take a look at how your resources are being used by > dom0 and any running VMs. Run "xentop" in a dom0 terminal for a nice > realtime summary. > > -- noor > > |_|O|_| > |_|_|O| Noor Christensen > |O|O|O| n...@fripost.org ~ 0x401DA1E0 Hi Noor, By VM, i mean Virtual Machine (we can say Qubes), I have at minimum 15 Qubes running. It is xorg in dom0 which is killed, I type 'dmesg' in dom0 terminal and see it is killed. I will retry to play with xentop. In idle my dom0 use 700MB (and 2200MB cache)/~3000MB. About reconnect to guid, before i use 'qvm-run --all true' to reconnect to them, but after this OOM this doesn't work. Do you have an idea? Regards -- 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/5d6ce952-cc22-4efd-9da6-4c78dadc85b8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Xorg and Oom killer, i3
Hi, I have 20gb memory, but I use a lot of VM. Sometimes xorg is randomly kill. I would like to protect xorg from being killed. I'm trying to play with overcommit but is it a good idea? Must I boot dom0 minimal memory? Bonus: after a xorg crash, I can't reconnect to guid daemon. How to do? I use i3, is it a i3 problem? Regards -- 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/a964a0d8-4f25-44c4-bef2-e9224e8c0519%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How to restart qubes-guid after a OOM?
Hi, I'm using i3, and sometimes, after start a lot a VM, oomkiller kill my session, I'm redirect to lightdm, when I reconnect me, all vms in qubes-manager are yellow, not green. I tried "qvm-run --all true" but this doesn't help me, openned windows not come back. How can I manage this issue without lose, if I don't want to reboot? Regards -- 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/d7ec9aff-edb7-490c-a6b5-f1a72d16cc93%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Request for feedback: 4.9 Kernel
Thanks I have done this, i will try next 4.9.29 ;) Le mercredi 24 mai 2017 20:43:11 UTC+2, Reg Tiangha a écrit : > On 05/24/2017 12:37 PM, cyrinux wrote: > > Hi, > > > > I have a T450s, and it works well, just this: > > > > Seems to have a problem for me, i often miss wireless after suspend. > > I need to stop firewall and wlan vm to reload iwlwifi driver. > > No easy to unload iwlwifi, faster to stop and start. > > I don't remember i have this problem before. > > > > No other problems. > > > > Thx > > Thanks for the feedback. There should be a work-around in the next > kernel release, so keep an eye out for a 4.9.29 or higher to appear in > one of the Qubes repositories and try that one when it comes out. I > *think* the kernel workaround will work, but it could use some testing > when it's out. > > In the meantime, you can also work around it locally by blacklisting the > iwlwifi power management module. In your sys-net, edit > /rw/config/suspend-module-blacklist and add: > > iwlmvm iwlwifi > > and then reboot the vm. According to other people, that should make the > wifi stuff work again too. -- 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/7bcae4d8-546d-4ad3-8b5e-a8ee6b53b27b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Request for feedback: 4.9 Kernel
Hi, I have a T450s, and it works well, just this: Seems to have a problem for me, i often miss wireless after suspend. I need to stop firewall and wlan vm to reload iwlwifi driver. No easy to unload iwlwifi, faster to stop and start. I don't remember i have this problem before. No other problems. Thx Le samedi 20 mai 2017 21:42:50 UTC+2, Reg Tiangha a écrit : > People may not have noticed, but there is now a 4.9 kernel in > current-testing (4.9.28 to be specific). > > If the release schedule holds, then that should be migrated to stable > soon, however, before that happens, some feedback on that kernel would > be useful before it gets pushed to the majority of users. > > Specifically, it'd be nice to know if: > > 1) Hardware that used to work with 4.4 or 4.8 no longer works with 4.9. > > 2) Hardware that didn't work with 4.4 or 4.8 still doesn't work. > > 3) If newer Intel platforms (i.e. Haswell or newer) works with this > kernel (I took out the Intel ME driver and the newest machine I have > access to is a Sandy Bridge machine; I have no issues, but I wonder if > Haswell or newer is tied more strongly to the Intel ME such that it > actually needs that driver in order t work properly). If there are Intel > hardware issues with this kernel, then I'll re-enable the driver in my > next Pull Request. > > 4) General feedback on the 4.9 kernel. > > 4.9.29 was just released today, so before I send in a Pull Request, let > me know how 4.9.28 performs and if changes to the kernel config may need > to be made. -- 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/d42cb309-f745-4916-9da7-ed97858d9285%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Hardware acceleration in Chrome (or "make google maps great again!")
Le dimanche 11 décembre 2016 07:52:29 UTC+1, Jean-Philippe Ouellet a écrit : > Hello, > > Google Chrome disabled the chrome://flags mechanism to disable WebGL > some time ago, but now it appears that it is back as "Use hardware > acceleration when available" at the bottom of the Advanced section of > chrome://settings. > > Disabling this makes google maps not lag/crash for me! :) > > Perhaps everyone has already done this and I'm just late to the party, > but I don't remember seeing it discussed in a capacity other than > "yeah... this is a problem", so I figured I'd share. > > Cheers, > Jean-Philippe Thanks!!! -- 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/0430a091-0329-4762-bc60-e4a2487eb431%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Thinkpad T460
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 03/12/2016 à 21:53, Jan Betlach a écrit : > On Saturday, December 3, 2016 at 8:41:49 PM UTC+1, Bernd Lorenzen > wrote: >> Hello, >> >> my Question is how i set the charge thresholds for my Lenovo >> Thinkpad T460. >> >> I have installed the following packages tlp, >> tlp-rdw,tp-smapi-dkms and acpi-call-dkms in both fedora aind >> debian template. Afterwards i changed the thresholds in the >> config file /etc/default/tlp in both templates and in dom0. But >> it doesn`t work. Do you know a workaround for this. I hope did >> not forget some useful information for you. >> >> Kind regards >> >> >> Bernd Lorenzen > > > Has the service been started? # systemctl status tlp > Hi, If this is like the T450, ensure that you have correctly compile the acpi_call module. Do you really have it? lsmod|grep -q acpi_call && echo "Installed" Personnaly I have allways trouble with dkms, I have manually build from /usr/src/akmods/*.src.rpm, -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJYRdAIAAoJEN6tUq35EFbDzgkP/A/WFRueW2GXGRZ16vCAIMcA o0Q5hjGFtvolD4fPiogW8a0KGE9k/ejggn45FaIGki+IS/QyjmZhhFkiADAhx1j0 x3WkBIn55sesWZOOzU4L6g+a5YPfU8B/DS0k0nJ59d6IUAExoW9tI5447a35fJ0Y DCM/4CRpCIH8ArVJxNq2kn9LY1TGNZyE2ddMqMSlDFF6JNDNaFsMEhPvKaPBDq++ 64Ul6QyWwnX9Q0zhBEBZux6CySh4IgYg6poWs6JBBEOnq3zcyAxSxoAdM1evzLrS bDZZzpS3zmTHhJ3cpX+sUKS2rP1gCdanqMuCzmIpn1O0OLP6/Qw+WQsGPYuX6UUw vTgegwmLGZnlHik+7pRjfTRpXup+0RXDQFwW0AKfoHJiCVfRtSP3oXuMxf5N/boy UeyeKzTrkculZUp7Ltd+r0+7xwOvibl2jQE8Jg+YozDLUBJhGWLfXhoA+IL42lxc 2DS4flwQIZ3fzc9Bo2VybXJHv6TrUAWXZUMk1F4vTCm479H37sAvSau3mYTQDgZV qb2xybMr1NBy+UEcSxVMmd2yHWv6+Yt+vPj8T2A/gZBm744Bn14HQbbTG8Y5Smja J0owh7stLToSA7tSKjDq2q57dPtz7C7uCnBf0ov2LJjy4MYyEMP6F77tAcNBrJxq 3A840duc9pRxuXZGNGfT =qtrp -END PGP SIGNATURE- -- 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/o24j6d%24mhn%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: ANN: Qubes network server
Le mardi 11 octobre 2016 21:31:21 UTC+2, Manuel Amador (Rudd-O) a écrit : > Folks, it gives me great pleasure to announce the product of over two > years of work (primarily because I never paid enough attention to this > project to bring it to completion): Qubes network server. > > The traditional Qubes OS networking model contemplates a client-only use > case. User VMs (AppVMs or StandaloneVMs) are attached to ProxyVMs, which > give the user control over outbound connections taking place from user > VMs. ProxyVMs in turn attach to NetVMs, which provide outbound > connectivity for ProxyVMs and other user VMs alike. > > Qubes network server changes all that. With the Qubes network server > software, it becomes possible to make network servers in user VMs > available to other machines, be them peer VMs in the same Qubes OS > system or machines connected to a physical link shared by a NetVM. You > get actual, full, GUI control over network traffic, both exiting the VM > and entering the VM, with exactly the same Qubes OS user experience you > are used to. > > This is all, of course, opt-in, so the standard Qubes OS network > security model remains in effect until you decide to share network servers. > > Anyway, without further ado: > > https://github.com/Rudd-O/qubes-network-server > > Real easy: clone, build, install, test. I tested it with Qubes 3.1, but > it's very likely that it'll work fine in Qubes 3.2. I recommend you > test this on a Qubes machine that is not your main Qubes machine, but > the code does not do anything funky, and uninstalling the program should > be enough to revert your system back to its original state. > > I hope we can turn this add-on into a core Qubes feature. As always, > contributions to the project — reports, code enhancements, pull > requests, other items — are very much welcome! > > -- > Rudd-O > http://rudd-o.com/ Hi, run 'sudo dnf install rpm-build' and try again, you don't have rpm tools -- 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/78773d11-093d-4fe8-8426-0437595a6b3a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: ANN: git-remote-qubes: Inter-VM Git for Qubes OS
Le jeudi 27 octobre 2016 13:47:14 UTC+2, Manuel Amador (Rudd-O) a écrit : > It gives me great pleasure to announce the inter-VM Git bridge for Qubes > OS, which allows you to git push and git pull from VMs stored in other > repos, with no networking involved whatsoever, and observing full > compliance with Qubes OS qrexec policy. > > This should usher in a new era of software development that allows > people to segregate their secure Git repos from insecure build VMs and > other engineering constructs I can't even think of (after doing > low-level socket programming for a week, which has left my brain utterly > fried). > > Find the software at https://github.com/Rudd-O/git-remote-qubes > > --- > > # Inter-VM Git for Qubes OS > > This is a very simple Git protocol bridge between Qubes OS VMs. With it, > you can `git pull` and `git push` between VMs without having to grant > any of the VMs any special policy privileges other than access to Git. > > ## Using the software > > These instructions assume you have installed the software. See the > *Installing the software* heading below for more information. > > ### Creating a repository > > We'll assume for illustration purposes that you want to access a repository > stored in `/home/user/xyz` on your VM `servervm`. > > Run the following commands on `servervm`: > > ``` > cd /home/user > mkdir -p xyz > cd xyz > git --bare init > ``` > > That's it. Your new and empty repository is ready to use. > > ### Adding a remote to a local repository > > For illustration purposes, you'll be pushing and pulling `servervm`'s `xyz` > repo on your vm `clientvm`. Run the following commands on `clientvm`: > > ``` > cd /home/user > git clone qubes://clientvm/home/user/xyz > ``` > > You will get a permission dialog from dom0 asking for `ruddo.Git` access. > Accept it. Note that accepting the permission dialog implicitly gives > Git access to all Git repos stored in `servervm`, but only for that one > execution (unless you say *Yes to all*, in which case the permission > is remembered within the policy file that you installed earlier with the > `dom0` package). > > This should have cloned `xyz` from `servervm` into your `/home/user/xyz` > directory in `clientvm`. > > From this point on, you can push and pull in `clientvm` from > `servervm:/home/user/xyz` to your heart's content. > > If, instead of cloning, you have an existing repo, you can add a new remote > just as easily: > > ``` > cd /home/user/existingxyz > git remote add qubesremotevm qubes://servervm/home/user/xyz > ``` > > That addition will enable to push and pull from the remote `qubesremotevm` > which represents the repo `/home/user/xyz` in the remote VM `servervm`. > > ## Installing the software > > There are two components for this software: > > * Component 1 is the VM side of things, which implements the Git protocol > across VMs. > * Component 2 is the dom0 side of things, which is a simple text file > declaring > the initial Git access policy for your VMs. > > First, build the software, After cloning this repository on a suitable VM, > run the command: > > ``` > make rpm > ``` > > This will generate two installable packages on the local directory: > > * `git-remote-qubes-.noarch.rpm`, which contains the Git > protocol implementation. > * `git-remote-qubes-dom0-.noarch.rpm`, which contains the > default policy. > > Copy the `git-remote-qubes-.noarch.rpm` file to the template VM > or standalone VM where you plan to pull or push to / from a Git repo > stored in another Qubes VM. Install the RPM with > `dnf install `. At this point, this VM, as well as > any VMs using this as a template, have gained the ability to push and pull > from Git repos stored in other VMs, as well as the ability to listen on > push / pull requests from different VMs in the same system. > > Now copy the `git-remote-qubes-dom0-.noarch.rpm` file to > your dom0. At this point, the default policy (`deny`) is active on > your Qubes OS system, and you can begin pushing and pulling. > > Those clever among you will have discovered that there is a `Makefile` > included, and that you can use the `Makefile` to install the software on > other non-RPM templates. I welcome pull requests to add support for > other distro packages and Qubes OS templates. > > ## Troubleshooting and debugging > > If you are experiencing problems communicating with a Git repo in a VM, > export the variable `QUBES_DEBUG` on the side of your client (where your > local Git repo is), and look at the debugging output that appears. > > As always, you can file new issues on the repo of this project for help > with fixing bugs that the programs may have. Pull requests also welcome. > > -- > Rudd-O > http://rudd-o.com/ I installed it yestarday, no problem, documentation is clear, well done yet :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group.
Re: [qubes-users] ANN: Leakproof Qubes VPN
Le mercredi 26 octobre 2016 14:38:24 UTC+2, Manuel Amador (Rudd-O) a écrit : > Apologies for the reply to self, but I have received great news. > > The first piece of great news is that a user of Qubes VPN found a bug > that made it impossible for Qubes VPN to work with tun-style VPN > providers. We have fixed that bug thanks to his cooperation, and you > can see the result of our bug report and conversation here: > > https://www.reddit.com/r/Qubes/comments/57acz8/add_a_leakproof_vpn_to_your_qubes_os_with_this/ > > The second piece of great news is that, based on what he reported there, > ABSOLUTELY NO TRAFFIC ever leaked from his VPN-protected AppVM to any > sort of network device, as the VPN VM still prevented the traffic from > going anywhere else except over the VPN. > > That means: even under an environment where a critical bug rendered VPN > operation impossible, Qubes VPN still managed to prevent leaks 100%. > > I am quite happy to see that the engineering gone into this thing > actually paid off big time. > > Have you tried Qubes VPN yet? > > -- > > Rudd-O > http://rudd-o.com/ Hi Rudd-o, just for say I use Qubes VPN since 2 weeks, with mullad, and no problem, this seems perfect ;) -- 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/7cf989a6-91cf-4281-94b5-32701272fa4b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to Install acpi_call on dom0? ( Usefull for lenovo )
Le lundi 24 octobre 2016 17:42:34 UTC+2, cyrinux a écrit : > Hi, > > I would like to know if anyone success on install acpi_call, or more > globally, how to build a module on dom0? > > For lenovo users, we need acpi_call for manage batteries thresholds with tlp. > > Thanks you -- 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/8e03dd42-b2f9-42bc-9eb4-6bbb020436df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2rc1 installation issues on a Lenovo T550
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 24/06/2016 à 19:23, nicklausmcclen...@gmail.com a écrit : > When I run the installer, it loads the initrd.img, gets to the line > where it says dom0 has maximum 4 vCPUs, and the cuts to black and > restarts the laptop. I have tried UEFI and BIOS, and have attempted > using the text installer. Any ideas on how I might get the > installation up and running? > Hi, just for say I just get the same error here on my lenovo x1c where 3.1 run without problem. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXbXUFAAoJEN6tUq35EFbDGF4P/1zztDe6OtpbsgZB4QC/nix5 3R/1R/sfYHJ7bo4M0UjiAS4sNXYV11X4KrKKwagIpvOXMvZAGB6b/du4f/dsjgTw hTA14OtjpOIiwyBr+dhNBWzzW7dwPG1xmC066E7gURHqiAoy1XiozAkKMCBggo4S QYlq2atqllgrR2ZshSnNngmD7beSiYpdIk0OqnJjwW6mEak4zLBH+wP+pFRUphaE jmQ8lNeSkVhJUaLhkumyDul+WridMFdhFBztMu+3T2gUNkSdVr08dKJQJdXx7sx+ dP5hw4lC+DMKl1jS03TMAd2h0DTgoAJzXUAFm6F1NdY79fuiCSAJf9g31P3YXxI5 DruqqtbvH4WVyXgC0nwwXAoMTUhaIueJQ5ZKyYRlwc3som3ylNZvdGNNZFgHto9e /5N2+GTB3s1srbY9X31HaN2DPB4AeZdNipPanIaD5XW9XDWIrIJRy5JeQ95SkG4C mZ5c01LKgAruTcm5bKwQHKMtoMI0jw9AsW3S0lKbZWgHlP8wJtpi1WzZwKNAxHIx H/iQ8HJSzXtVWot62ZREMY/rfiX8hyaaCXr3Sc8r8fW5dKs7qOfbBKfuun6edBCS 3VwgwgCT4VbtL7EyOwJ9m97dT61v+C77WN0b6qIiKP5CraDObAJ6knxQsYOVFRc+ 0HoT4OZGirx3+rrdxMwD =x2BL -END PGP SIGNATURE- -- 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/nkjsej%24doh%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 3.2 rc1 has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Great! Thanks! Le 18/06/2016 à 10:48, Marek Marczykowski-Górecki a écrit : > Details here: > https://www.qubes-os.org/news/2016/06/18/qubes-OS-3-2-rc1-has-been-rel eased/ > > > As usual, you can download new image from: > https://www.qubes-os.org/downloads/ > > Keep in mind it is only release candidate, so not recommended for > daily use. > > -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXZbH9AAoJEN6tUq35EFbDkXAQAJAHMlYYxSGuHTkBIRfmxGsK zIM1jD8jPdsTCkkVeePvDFdVRDr/r0Kb/8UZu8eqMgyLV6xSvt+F+j+mHvVJMsuw nUcuG05QzPgqNDDLowyUAfQknApsHt/+TCX5/KzDWQ7GH0yHYftFoRCLxBfvIvvd mK+fqsV5lR0hCKFxkhS0cM71BNjbAf23XJw6FaxwAtAEpCk1QnM2sd+IimosbnS6 ou+zSlY2zwFp2OBBOsKWBTQXnSzwrrAqei8S9xSZQHUNInEWAR3aTlmmeGxymD0k P7E1Q2QEXzgcoXVwKdo3JE/amVY385HUzmNcFAp0HZZ8yLcei570Cp8ZOlKNwNaQ 8gDbHUx7E2LpGcVx1pRZ9MwXBAqk8yDdtgGrfnAuP1dIJs8CoNYMNtdBi4wT9F5F UdahFhJ+uv0jGcj+D4t0cZV0rhesuOjyxugtO8LgjpU+LJtUJwFhV2IpyOcQiR/G nOg3hEg9F2XAec4Pjo1u5G/zj3T+DUE3/WBsrwQT4SP5iJQ7EnhBJ1djPdbyUFer bvRjtSMQqN35HHRP+R3q5h8twpQYME3m3HC1N/nCmrZztpBHIz1b88cknf3dOo0D rwSZZKonIDAJSIVtT/Ti55R6YCbT/zu1WzV5veKfNQwMq2fnpe708WbUv0u5+y14 ETh4fgsPgZsrojIRlwZq =+YB7 -END PGP SIGNATURE- -- 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/nk4bm9%24me8%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout.
