Re: [qubes-users] Big problem?
But how can I reinstall it if the onlt thing I can do/see is to eneter my disk password? Could you explain to me how you did that? -- 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/4f9fc4b3-d22a-44c5-9682-aa4e591cf3b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Anbox?
On 04/13/2017 10:57 PM, elsiebuck...@gmail.com wrote: > This sounds interesting: > https://www.slashgear.com/anbox-runs-android-apps-on-linux-just-like-native-apps-13481922/ > > Will this work on Qubes? > Since it looks like it's based on simple containerization instead of virtualization it should work. A little background: I usually do docker / rkt development on a "work" appVM in qubes, and it works just out of the box. I've had a nasty but simple quirk with flatpak, because of the already-mounted /proc/xen, but unmounting that seems not to break anything and let some flatpak archives work. I really hope that this could be a viable solution for debugging application: that would really speed up my qubes-based android development tasks, instead of using the emulator with arm images which is - to put it mildly - kinda slow. -- Alex -- 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/9d727b6b-41f3-9493-4bf1-bc0d180a4300%40gmx.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Re: remote code execution via UDP packets (CVE-2016-10229) in the context of Qubes // and kernel update recommendations
On 04/14/2017 06:00 AM, Reg Tiangha wrote: > On 04/13/2017 09:33 PM, cooloutac wrote: >> On Thursday, April 13, 2017 at 11:26:07 PM UTC-4, cooloutac wrote: >>> So probably the kernels are not actually vulnerable, They fixed it a year >>> ago with patches, and with Qubes you assume this sort of priv escl thing >>> regardless which is why they don't even bother with sudo. >> Actually when it comes to redhat they claim the code was never there to >> exploit. But redhat might not apply to fedora kernel so I'm kind of curious >> myself now. >> > For those who are concerned, this is what is currently in the Qubes > repository for dom0: > > current: kernel-4.4.38, kernel-qubes-vm-4.4.38 > > current-testing: kernel-4.4.55, kernel-qubes-vm-4.4.55 > > > From what I can tell, the Qubes Kernel is built from the stock kernel > source, so if this bug was fixed months ago, you could probably install > either and be fine (assuming you're running R3.2). > [...] According to [1], linux <= 4.4.60 is affected. The patch was but on 4.5-rc1 branch on Dec. 15, but this doesn't mean it got backported to older kernels as it was not tagged as a security issue before (eg. debian's DSA mentioned "A regression in the UDP implementation prevented freeradius and some other applications from receiving data." as the reason for their backporting the patch, if I read correctly) Which, unless fedora's (or qubes') kernel has been using a patch for this despite it not being tagged as a security issue until now, would mean qubes' current kernels are all vulnerable. HTH, Leo [1] https://nvd.nist.gov/vuln/detail/CVE-2016-10229 -- 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/86219df3-c3a2-bcfd-196a-5dec6b714cec%40gaspard.io. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Re: remote code execution via UDP packets (CVE-2016-10229) in the context of Qubes // and kernel update recommendations
On 04/13/2017 10:00 PM, Reg Tiangha wrote: > On 04/13/2017 09:33 PM, cooloutac wrote: >> On Thursday, April 13, 2017 at 11:26:07 PM UTC-4, cooloutac wrote: >>> So probably the kernels are not actually vulnerable, They fixed it a year >>> ago with patches, and with Qubes you assume this sort of priv escl thing >>> regardless which is why they don't even bother with sudo. >> Actually when it comes to redhat they claim the code was never there to >> exploit. But redhat might not apply to fedora kernel so I'm kind of curious >> myself now. >> > For those who are concerned, this is what is currently in the Qubes > repository for dom0: > > current: kernel-4.4.38, kernel-qubes-vm-4.4.38 > > current-testing: kernel-4.4.55, kernel-qubes-vm-4.4.55 > > > From what I can tell, the Qubes Kernel is built from the stock kernel > source, so if this bug was fixed months ago, you could probably install > either and be fine (assuming you're running R3.2). > > > If you're really paranoid, you can build the latest 4.4 kernel (as of > now, it's 4.4.61) yourself and install via rpm with very little > modification using the existing Qubes build scripts. > > Assuming you have a Fedora 23 VM with git, gcc and make installed (maybe > a few other things; I'm not sure), run: > > git clone https://github.com/QubesOS/qubes-linux-kernel.git > > - Switch to the 4.4 branch: > > git checkout stable-4.4 > > - Edit the 'version' file and replace 4.4.55 with 4.4.61 > > - Then compile: > > make rpms > > And then copy the kernel and kernel-qubes-vm rpms to dom0 and install > them there using rpm or dnf. > > I just did it myself with the 4.4 branch and it builds fine. I haven't > installed it though since I run 4.10 (which is a bit more involved since > some of the patches need to be migrated; I've been applying them by hand > using diff -Nuar so I just need to figure out how to create a patch file > *properly* that doesn't require manual intervention, and then I'll > probably throw up my work on GitHub so others can use it for both 4.9 > and 4.10; this GitHub stuff and figuring out how to patch things isn't > my forte yet). > > Actually, you'll need a few more things, most notably qubes-kernel-vm-support. I believe that package will pull in everything you need to compile a kernel for Qubes. If you're going to attempt to build a 4.9 kernel or higher, grab version 3.2.4 (install both in your build vm and dom0) out of current-testing since it hasn't been pushed into stable yet and 3.2.3 only works with kernels up to 4.8. -- 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/ocpkq8%24fr%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: remote code execution via UDP packets (CVE-2016-10229) in the context of Qubes // and kernel update recommendations
On 04/13/2017 09:33 PM, cooloutac wrote: > On Thursday, April 13, 2017 at 11:26:07 PM UTC-4, cooloutac wrote: >> So probably the kernels are not actually vulnerable, They fixed it a year >> ago with patches, and with Qubes you assume this sort of priv escl thing >> regardless which is why they don't even bother with sudo. > Actually when it comes to redhat they claim the code was never there to > exploit. But redhat might not apply to fedora kernel so I'm kind of curious > myself now. > For those who are concerned, this is what is currently in the Qubes repository for dom0: current: kernel-4.4.38, kernel-qubes-vm-4.4.38 current-testing: kernel-4.4.55, kernel-qubes-vm-4.4.55 >From what I can tell, the Qubes Kernel is built from the stock kernel source, so if this bug was fixed months ago, you could probably install either and be fine (assuming you're running R3.2). If you're really paranoid, you can build the latest 4.4 kernel (as of now, it's 4.4.61) yourself and install via rpm with very little modification using the existing Qubes build scripts. Assuming you have a Fedora 23 VM with git, gcc and make installed (maybe a few other things; I'm not sure), run: git clone https://github.com/QubesOS/qubes-linux-kernel.git - Switch to the 4.4 branch: git checkout stable-4.4 - Edit the 'version' file and replace 4.4.55 with 4.4.61 - Then compile: make rpms And then copy the kernel and kernel-qubes-vm rpms to dom0 and install them there using rpm or dnf. I just did it myself with the 4.4 branch and it builds fine. I haven't installed it though since I run 4.10 (which is a bit more involved since some of the patches need to be migrated; I've been applying them by hand using diff -Nuar so I just need to figure out how to create a patch file *properly* that doesn't require manual intervention, and then I'll probably throw up my work on GitHub so others can use it for both 4.9 and 4.10; this GitHub stuff and figuring out how to patch things isn't my forte yet). -- 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/ocphg4%24ag4%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: remote code execution via UDP packets (CVE-2016-10229) in the context of Qubes // and kernel update recommendations
On Thursday, April 13, 2017 at 11:26:07 PM UTC-4, cooloutac wrote: > So probably the kernels are not actually vulnerable, They fixed it a year ago > with patches, and with Qubes you assume this sort of priv escl thing > regardless which is why they don't even bother with sudo. Actually when it comes to redhat they claim the code was never there to exploit. But redhat might not apply to fedora kernel so I'm kind of curious myself now. -- 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/30177442-2381-4c2e-8db5-bb16171a939f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: remote code execution via UDP packets (CVE-2016-10229) in the context of Qubes // and kernel update recommendations
So probably the kernels are not actually vulnerable, They fixed it a year ago with patches, and with Qubes you assume this sort of priv escl thing regardless which is why they don't even bother with sudo. -- 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/a7b2a30e-a7e9-4059-8e25-585d7139e2e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: remote code execution via UDP packets (CVE-2016-10229) in the context of Qubes // and kernel update recommendations
On Thursday, April 13, 2017 at 8:18:20 PM UTC-4, Joonas Lehtonen wrote: > https://nvd.nist.gov/vuln/detail/CVE-2016-10229 > > udp.c in the Linux kernel before 4.5 allows remote attackers to > > execute arbitrary code via UDP traffic [...] > > fixed in [1] (2015-12-30) > > It never affected Fedora according to: > https://bugzilla.redhat.com/show_bug.cgi?id=1439740#c2 > > This fix was committed upstream in the 4.5 kernel merge window (Dec > > 2015). It has never impacted any of the currently supported versions of > > Fedora. > > In Debian it got fixed on 2016-01-5 > https://www.debian.org/security/2016/dsa-3434 > 3.16.7-ckt20-1+deb8u2 > https://security-tracker.debian.org/tracker/CVE-2016-10229 > > Since Qubes VMs depend on dom0 for kernel updates, Qubes user do not get > kernel updates from upstream distros. > > - Qubes currently ships kernel 4.4.38 for VMs > Kernel 4.4.38 has been released on 2016-12-10 so I assume it contains > the fix? > > - Have Qubes VM kernels (provided by dom0) ever been affected (in the > past of R3.2)? > > Since Qubes does not frequently release VM kernel updates*: > Do you recommend to switch to pvgrub and in-VM kernels to be able to > take advantage of regular distro kernel updates? > > The upcoming/planed binary packages of coldkernel probably address this > topic as well. > > thanks! > Joonas > > > *) I know, that in-VM security is/should not be relevant for the > isolation between VMs but if someone can compromise all networked VMs > via vulnerabilities in the UDP/TCP/IP stack it is probably as bad as > having no isolation. > > > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=197c949e7798fbf28cfadc69d9ca0c2abbf93191 read this discussion, kernel verison might not mean much here. https://news.ycombinator.com/item?id=14105718 -- 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/5dba8d6a-3eea-4eda-b583-9c1c953f2901%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Status of dvm support
On Thursday, April 13, 2017 at 1:06:11 PM UTC-4, justus...@gmail.com wrote: > I've experienced problems with DVMs on every Qubes install I've ever done. I > currently have no devices running Qubes on which dvms work. > > Based on several threads from last year I found on this issue, and this issue: > > https://github.com/QubesOS/qubes-issues/issues/2182 > > Is it correct that once this bug with the dvm savefile is triggered, then > dvms will never work on your system again unless you manually patch xen and > recompile? > > Are there instructions anywhere for doing this? I never heard of that. Have you tried to just delete the dvm from qubes manager, then from dom0 terminal type qvm-create-default-dvm fedora-24? That always works for me. -- 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/d4ad3b21-0812-4429-aaa7-25df592861ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Big problem?
I've done that before man, it can happen to anybody. Just reinstall qubes from the usb stick again and do the password over, this time one that will work for both keyboard if possible. Or one you can remember how to type on both. I also have a similar issue on raspberry pi where no matter what I do when I reboot ro plug in my kb it goes to uk layout and some keys are diff so in the passwords so I have to use one that works for both. -- 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/1e445d6f-52a8-496e-8c91-3037f3ba2ec7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] remote code execution via UDP packets (CVE-2016-10229) in the context of Qubes // and kernel update recommendations
https://nvd.nist.gov/vuln/detail/CVE-2016-10229 > udp.c in the Linux kernel before 4.5 allows remote attackers to > execute arbitrary code via UDP traffic [...] fixed in [1] (2015-12-30) It never affected Fedora according to: https://bugzilla.redhat.com/show_bug.cgi?id=1439740#c2 > This fix was committed upstream in the 4.5 kernel merge window (Dec > 2015). It has never impacted any of the currently supported versions of > Fedora. In Debian it got fixed on 2016-01-5 https://www.debian.org/security/2016/dsa-3434 3.16.7-ckt20-1+deb8u2 https://security-tracker.debian.org/tracker/CVE-2016-10229 Since Qubes VMs depend on dom0 for kernel updates, Qubes user do not get kernel updates from upstream distros. - Qubes currently ships kernel 4.4.38 for VMs Kernel 4.4.38 has been released on 2016-12-10 so I assume it contains the fix? - Have Qubes VM kernels (provided by dom0) ever been affected (in the past of R3.2)? Since Qubes does not frequently release VM kernel updates*: Do you recommend to switch to pvgrub and in-VM kernels to be able to take advantage of regular distro kernel updates? The upcoming/planed binary packages of coldkernel probably address this topic as well. thanks! Joonas *) I know, that in-VM security is/should not be relevant for the isolation between VMs but if someone can compromise all networked VMs via vulnerabilities in the UDP/TCP/IP stack it is probably as bad as having no isolation. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=197c949e7798fbf28cfadc69d9ca0c2abbf93191 -- 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/639daa54-56a6-abba-4e78-3fdd18a25518%40openmailbox.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Anbox?
This sounds interesting: https://www.slashgear.com/anbox-runs-android-apps-on-linux-just-like-native-apps-13481922/ Will this work on Qubes? -- 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/7d73c79a-4226-4f92-8293-56c7f44736fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Big problem?
On Thursday, April 13, 2017 at 4:22:28 PM UTC-4, rubb...@gmail.com wrote: > I know I could solve it that way but the only thing on my pc I can do right > now is to try the 'disk password'. I think there is no way that I can get > into my bios from that only screen I can see. Yes, by the time you see the Qubes "disk password" it is too late. Anything is possible, but it would be a strange BIOS that gave you no way to get into BIOS setup. The answer might be in the motherboard manual or whatever else came with your new computer. Or just randomly try pressing F2, F12, F9, Del, Esc, Tab right after power-on. Usually some of those do things. -- 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/9e562225-4422-4fe5-a63b-7f114e5efee8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Big problem?
I know I could solve it that way but the only thing on my pc I can do right now is to try the 'disk password'. I think there is no way that I can get into my bios from that only screen I can see. -- 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/39585921-c62e-4074-a646-346fced86dc3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Status of dvm support
I've experienced problems with DVMs on every Qubes install I've ever done. I currently have no devices running Qubes on which dvms work. Based on several threads from last year I found on this issue, and this issue: https://github.com/QubesOS/qubes-issues/issues/2182 Is it correct that once this bug with the dvm savefile is triggered, then dvms will never work on your system again unless you manually patch xen and recompile? Are there instructions anywhere for doing this? -- 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/d0e928b1-f08d-42ab-9a13-f851e99c2e0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Big problem?
On Thursday, April 13, 2017 at 4:04:26 AM UTC-4, rubb...@gmail.com wrote: > I will try with qwerty keyboard. But there is no possibilitie to undo the > qubes installation and get everything back to my windows? Because I think > it's safer for me to use windows instead of Qubes Disk encryption can't stop you from erasing the disk. I don't know how Windows is installed, but if you can get any installer to load and run, it should work fine. See what boot options your BIOS has. -- 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/aa4cd553-639e-466e-ad5d-bd2baaa0dce1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] My Windows VM always stops after a while
On Thursday, 13 April 2017 14:41:16 UTC+8, Robert Fisk wrote: > I notice this problem when a Windows VM is left running, but doesn't > receive any user input for 30min or more. The window will disappear > when I'm not looking and I later find the VM stopped. > > In my case the solution is to use the VM, and it is reliable until the > work is finished and I shut it down. Just a thought - have a look > through the power saving & sleep options. It might be trying to "save > power" and causing problems with Xen. Thank you. That seems to be the cause. Power saving was indeed enabled with the system configured to suspend after 30 minutes. I turned it off, and the Windows VM hasn't crashed yet. -- 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/0e3b2c2b-9133-466e-b74c-c37a860c60cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: M.2 SSD Not recognized as a bootable device
Hey, thats for your reply. I ll try to run a tool to clone it, and i will let you know. My M.2 is working, i used windows 10 on it, and kali linux. but when i installed kali linux, i needed to run a couple of commands after the installation end. I dont remember what commands haha. I tried to install qubes on my m.2 without encryption and its the same, so i ll just try to clone it. 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/0541a736-8ec3-48b7-866e-efcec43ce36e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Question to Mirage OS firewall users
On Thursday, April 13, 2017 at 11:08:11 AM UTC+1, Foppe de Haan wrote: > On Thursday, April 13, 2017 at 10:00:20 AM UTC+2, Thomas Leonard wrote: > > On Wednesday, April 12, 2017 at 10:32:11 PM UTC+1, Foppe de Haan wrote: > > > Any clue why Windows 7 won't boot when I have MirageOS selected as the > > > firewall? > > > > I've never tried it. Do the mirage-firewall logs show anything interesting > > when you try to boot Windows? > > No, but I do have this log (guest-windows-dm). First log doesn't boot > (MirageOS), 2nd does (sys-firewall). Is that of any use? Oh, that's more useful than I was expecting! Looks like the Windows boot process starts by running MiniOS! It's hanging at close network: backend at /local/domain/4/backend/vif/79/0 I guess it asked the firewall to close the network, and never got a reply (because the firewall doesn't have any code to do that). -- 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/6867f02a-7300-48e9-95a8-e7315b372a6b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Stripping down dom0 kernels: Any tips?
On Tuesday, April 11, 2017 at 6:29:40 PM UTC-4, Reg Tiangha wrote: ... > I'll probably start playing around with seeing how far I can cut down > the dom0 kernel this weekend, but figured in the meantime I'd ask the > list if they have any advice or tips if they've tried something like > this in the past. Very interesting. Please keep us posted. -- 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/9525ae03-ee56-40e3-abea-23f273db7df4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: M.2 SSD Not recognized as a bootable device
On Thursday, 13 April 2017 00:30:51 UTC+2, mystre...@gmail.com wrote: > Hello, i hope you can help me. > After I install Qubes to the SSD and reboot, it does not recognize the SSD as > a bootable device. Using the same install procedures on another SSD (SATA), > everything works fine. When using Qubes from the SSD (SATA) to access the M.2 > SSD, the BOOT file is empty, so there are no files to rename as you've > directed in the UEFI troubleshooting. Also, I cannot access the /BOOT/EFI/ > file on my SSD (SATA), it says I don't have the required permissions. > I have also compared the Partitions from my M.2 SSD and the other SSD and > they are the same. > M.2 SSD PARTITIONS: http://imgur.com/a/GPCYh > SSD PARTITIONS: http://imgur.com/a/QIzph hey! Here is something you could try: install qubes on your normal functioning ssd, then use a disk cloning program like Symantec Ghost to basically clone the ssd with your working Qubes install on it, and saving it onto the M.2 drive. further more, have you tried installing other OS's onto your m.2 drive? Because it could be a problem with the drive itself instead of a software problem. I think this is likely, since it Qubes appears to work normally on a non-M.2 drive (according to you. so the problem should be something drive specific, I think. i would like to hear from you if it works or not, good luck best regards, blacklight447 -- 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/89e7e621-4bd4-4407-97c6-2b3aca2d2d16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Question to Mirage OS firewall users
On Thursday, April 13, 2017 at 10:00:20 AM UTC+2, Thomas Leonard wrote: > On Wednesday, April 12, 2017 at 10:32:11 PM UTC+1, Foppe de Haan wrote: > > Any clue why Windows 7 won't boot when I have MirageOS selected as the > > firewall? > > I've never tried it. Do the mirage-firewall logs show anything interesting > when you try to boot Windows? No, but I do have this log (guest-windows-dm). First log doesn't boot (MirageOS), 2nd does (sys-firewall). Is that of any use? -- 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/38844a39-e377-4585-bcba-877a9f4ed32b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Doesn't boot: Xen Minimal OS! start_info: 0x58(VA) nr_pages: 0x2c00 shared_inf: 0x87323000(MA) pt_base: 0x583000(VA) nr_pt_frames: 0x7 mfn_list: 0x56a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: -d 78 stack: 0x528cc0-0x548cc0 MM: Init _text: 0x0(VA) _etext: 0x1185d2(VA) _erodata: 0x16a000(VA) _edata: 0x170528(VA) stack start: 0x528cc0(VA) _end: 0x5695c8(VA) start_pfn: 58d max_pfn: 2c00 Mapping memory range 0x80 - 0x2c0 setting 0x0-0x16a000 readonly skipped 1000 MM: Initialise page allocator for 59f000(59f000)-2c0(2c0) MM: done Demand map pfns at 2c01000-0x2002c01000. Heap resides at 2002c02000-4002c02000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x2c01000. Initialising scheduler Thread "Idle": pointer: 0x0x2002c02050, stack: 0x0x5c Thread "xenstore": pointer: 0x0x2002c02800, stack: 0x0x5d xenbus initialised on irq 1 mfn 0x172037 Thread "shutdown": pointer: 0x0x2002c02fb0, stack: 0x0x5e main.c: dummy main: start_info=0x548dc0 Thread "main": pointer: 0x0x2002c03760, stack: 0x0x5f Thread "pcifront": pointer: 0x0x2002c03f50, stack: 0x0x60 pcifront_watches: waiting for backend path to appear device/pci/0/backend dom vm is at /vm/c94a758f-71be-492b-b863-b78eb48f93b3 "main" "-d" "78" "-d" "78" "-domain-name" "w7-h" "-vnc" "none" "-videoram" "16" "-std-vga" "-boot" "dc" "-usb" "-usbdevice" "tablet" "-acpi" "-vcpus" "2" "-vcpu_avail" "0x03" "-net" "nic,vlan=0,macaddr=00:16:3e:5e:6c:11,model=rtl8139" "-net" "tap,vlan=0,ifname=vif78.0-emu,bridge=(null),script=no,downscript=no" "-net" "lwip,client_ip=10.137.4.28,server_ip=10.137.4.254,dns=10.137.4.1,gw=10.137.4.1,netmask=255.255.255.0" domid: 78 domid: 78 NETFRONT for device/vif/0 ** net TX ring size 256 net RX ring size 256 backend at /local/domain/4/backend/vif/79/0 mac is 00:16:3e:5e:6c:11 ** tap_open((null)) -> 3 Waiting for network. IP a8904fe netmask ff00 gateway a890401. TCP/IP bringup begins. Thread "tcpip_thread": pointer: 0x0x2002c07d80, stack: 0x0x72 TCP/IP bringup ends. registering DHCP server Network is ready. xs_daemon_open -> 5, 0x16eea8 Using xvda for guest's hda *** BLKFRONT for /local/domain/79/device/vbd/51712 ** backend at /local/domain/0/backend/vbd/79/51712 47104000 sectors of 512 bytes ** blk_open(/local/domain/79/device/vbd/51712) -> 6 Using xvdb for guest's hdb *** BLKFRONT for /local/domain/79/device/vbd/51728 ** backend at /local/domain/0/backend/vbd/79/51728 10338304 sectors of 512 bytes ** blk_open(/local/domain/79/device/vbd/51728) -> 7 xs_directory(/local/domain/79/device/vkbd): ENOENT xs_directory(/local/domain/79/device/vfb): ENOENT xs_watch(device-model/78/logdirty/cmd, logdirty) Watching device-model/78/logdirty/cmd xs_watch(device-model/78/command, dm-command) Watching device-model/78/command xs_watch(/local/domain/78/cpu, vcpu-set) Watching /local/domain/78/cpu xs_read(/local/domain/0/backend/pci/78/0/msitranslate): EACCES xs_read(/local/domain/0/backend/pci/78/0/power_mgmt): EACCES qemu_map_cache_init nr_buckets = 1 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = c94a758f-71be-492b-b863-b78eb48f93b3 xs_watch(/local/domain/0/backend/console/78, be:0x15925d:78:0x16a400) xs_directory(/local/domain/0/backend/console/78): EACCES xs_watch(/local/domain/0/backend/vkbd/78, be:0x15593e:78:0x16a3a0) xs_directory(/local/domain/0/backend/vkbd/78): EACCES evtchn_open() -> 8 xc_evtchn_bind_interdomain(78, 3) = 0 xc_evtchn_bind_interdomain(78, 5) = 0 xc_evtchn_bind_interdomain(78, 4) = 0 populating video RAM at ff00 mapping video RAM from ff00 xs_read(device-model/78/disable_pf): ENOENT Register xen platform. Done register platform. xs_watch(/local/domain/78/log-throttling, /local/domain/78/log-thro
Re: [qubes-users] Big problem?
I will try with qwerty keyboard. But there is no possibilitie to undo the qubes installation and get everything back to my windows? Because I think it's safer for me to use windows instead of Qubes -- 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/f80d-2c35-43e7-9421-46fe7920a486%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Big problem?
Yes, When you have to input the decryption key, a lot, if not all of your Operating system isn't loaded yet, so it didn't apply your custom keyboard layout settings yet. On 13/04/2017 09:56, rubboe...@gmail.com wrote: > During the installation I choose azerty, is it possible that it is now qwerty? > -- 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/01a7633c-bf92-a443-04a5-8234911ca255%40nopping.eu. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Question to Mirage OS firewall users
On Wednesday, April 12, 2017 at 10:32:11 PM UTC+1, Foppe de Haan wrote: > Any clue why Windows 7 won't boot when I have MirageOS selected as the > firewall? I've never tried it. Do the mirage-firewall logs show anything interesting when you try to boot Windows? -- 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/e36e3c71-1c55-41e6-98d4-ad4731809857%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Big problem?
During the installation I choose azerty, is it possible that it is now qwerty? -- 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/b2373eeb-40b4-4ba5-a733-9698b7ebeb35%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Big problem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/13/2017 09:15 AM, rubboe...@gmail.com wrote: > Hi, > > I'm new to Qubes and yesterday i've installed qubes, everything > went fine. When qubes was almost done it asked me for my disk > password. So I thought that that would be the passphrase, i entered > the passphrase but it was wrong. I litteraly tried evey possible > answer. Is there a possibbilitie to delete qubes or something > because i'm completely stuck. I can't do something else with my > pc I hope someone could help, because this is just a new pc and > this is already a big problem... > It can be a keyboard layout problem, if you not using the default US - -- Zrubi -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJY7yp7AAoJEH7adOMCkunmo7MP/jIsvK3g9Ltl82ix/md9bJ2p yG79shhf5hbAfhueEKvBPssPrGOhlHYeebT1usjJ7Qw6sQcCnGoe24cuX+PFM4wr K3uejNw70eN7vwSA4KHXzMNjKclCBnd8vUCfZuirGJ8Dj2R/q4b3rSCDZZjdreJl elfmHW0567cVCIR59IFLm5GVLXVHNQZjFDd3EVgmwPAMQIo1NVZVn1t6Dumickvp dUk3nUYqJZOlh/+Z34qYiaLpX4YCUebpyaqtzBTpAdUFwTm0TJ9yAbe1NGhJVboU V3C1aoMIr/zrzEfiYUeV0vfKQXIKEqwe5B0mZ7L+nYbPYGGJeJvS/G27hUj4WIe8 HUx5RCS5JRtYdAaKWzPKVmZB7zPvp3KEv+pwiHLuLDRZ6hqD3v2lk0YCj8RGmdmk t0hZHPY4HNIlrgC9lIM5/m/tiIjy3QYrQheMLDKXkE1HrM3RpSh4aQ86gkhiBiV+ 6lKAZwMXONoahiscdMUoXv7bQV0P6b4OwMsNVRDjKQ8xUTF1fVWMupBtCnqEA8cL kL3XeaugTgX3Fdz588TEAra7yfmzBQr/KQN7TRp7WyUY71iOMXkJyw7vktHZIoWl Wu2F1ZiQPg6c7YeixW+FLEhsO2ZSHEmZ1jc6xsKFSjnnY/3Ee2gVDDeZ1451aNcd Gnn99RhsIpVPnBG6oNoH =JEqX -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/92f2c467-abf5-f18b-d026-7af8ad2fbfcf%40zrubi.hu. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Big problem?
Hi, I'm new to Qubes and yesterday i've installed qubes, everything went fine. When qubes was almost done it asked me for my disk password. So I thought that that would be the passphrase, i entered the passphrase but it was wrong. I litteraly tried evey possible answer. Is there a possibbilitie to delete qubes or something because i'm completely stuck. I can't do something else with my pc I hope someone could help, because this is just a new pc and this is already a big problem... -- 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/e9e8fba3-beb9-40c7-8b1b-7c4ba6a42c62%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: off topic - invite codes to 'riseup'
Hi im in need also of invite code. I would really appreciate it if you anyone could give me one. Thank 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/f4ba2cc0-8027-405e-8f12-13f9dfe91bb6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Adding more users/pass phrases to Qubes default disk encryption?
On Sun, 2017-04-09 at 20:40 -0700, Andrew David Wong wrote: > On 2017-04-08 10:20, Johannes Graumann wrote: > > Hello, > > > > Are there any pointers at how to achieve adding more users/pass > > phrases to the disk encryption setup as produced by a default Qubes > > install? > > > > Sincerely, Joh > > > > This is not Qubes-specific, so you can do this with cryptsetup as you > normally would on a standard Linux distro. Trivial indeed (and figured out now). Joh -- 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/1492067147.7285.0.camel%40graumannschaft.org. For more options, visit https://groups.google.com/d/optout.
