On Thu, Jul 16, 2020 at 10:40:47PM +0200, 'cubit' via qubes-users wrote:
> Is there any way to control the sound level once it is passed to an
> AppVM? It would also be nice to control my mic levels but so far
> people have not complained about me being too quiet so not as
On Fri, Jul 03, 2020 at 11:01:48AM +0200, Qubes wrote:
> Using sys-whonix as UpdateVM to download updates for Dom0; this may take
> some time...
> error: could not delete old database at
> I don't have a /var/lib/qubes/dom0-updates/ folder
On Thu, Jul 02, 2020 at 07:08:27PM +0200, Joo Nasss wrote:
> How to Change qubes OS dom0 to Debian?
short answer: if you have to ask, you dont.
You received this message because you are subscribed to the Google Groups
On Sat, Jun 27, 2020 at 01:28:57AM -0700, Frogfessor wrote:
> that it doesn't support virtualization. But, either way, I was planning to
> just flash it onto a live USB anyways. But, my 64gb USB, which has been
> formatted to FAT32 and has no filed on it, is said to have only about 900
On Fri, Jun 26, 2020 at 06:38:09AM -0300, Franz wrote:
> Next time I would suggest a very simple and reliable backup of the old
> disk, install Qubes on the new disk, restore backup on the new disk and
> you'll have a clean new system with no problems.
uh. even in the best case, this is a _lot_
On Thu, Jun 25, 2020 at 10:29:33PM +, 'Matt Drez' via qubes-users wrote:
> How to safely raise it to the maximum size (1TB ) and not just an
> arbitrary number that's close enough?
if you bought a "1TB disk", that usualy means 931GiB.
the pvresize dance means the pv is now as
On Thu, Jun 25, 2020 at 08:54:51PM +, Matt Drez wrote:
> This is where I am at now (below). What would be the best course of
> action. What would you if this was your mess to clean up? :)
> WARNING: Device
> /dev/mapper/luks-55a20051-8c1a-435e-a1c8-862493f2d576 has size of
On Thu, Jun 25, 2020 at 08:05:11PM +, Matt Drez wrote:
> That makes total sense. Well, I'm glad I didn't screw everything up
> but now how do I reverse what I have done so I could achieve my goal?
> How can I "take away" the 100% free space I assigned to root and give
> it to the whole system?
On Wed, Jun 24, 2020 at 07:49:56PM +, Matt Drez wrote:
> [@dom0 ~]$ sudo lvextend -l +100%FREE /dev/mapper/qubes_dom0-root
this means you resized your dom0 root volume.
that is probably not what you were trying to do.
you can check if that worked with "df -h /" or
On Thu, Jun 25, 2020 at 11:03:19AM -0700, E. Foster wrote:
> I finally got latest version of Qubes installed. thanks for the
what version is that?
> version displayed did not change. From reading the documentation, The
> updater should have updated to Whonix 16, and Fedora 35 or 36 as
On Wed, Jun 24, 2020 at 04:38:21PM +, Matt Drez wrote:
> None of the three commands you gave showed 900+GB
you can doublecheck the partition and luks device already have the
right size with ...
lsblk -d /dev/nvme* /dev/mapper/luks-*
if these show 900+GB you are good to go with the lvm
On Tue, Jun 23, 2020 at 04:11:56PM +, 'Matt Drez' via qubes-users wrote:
> I was trying to move my Qubes to a bigger disk. I used clonezilla to
> clone it. I was able to successfully boot up but Qubes was still
> complaining that my disk is full. For some reason it doesn't want to
> use the
On Mon, Jun 22, 2020 at 04:54:18PM +, 'Matt Drez' via qubes-users wrote:
> Reading from proxy failed - read (104: Connection reset by peer) [IP:
> 127.0.0.1 8082]
qrexec-client-vm '$default' qubes.UpdatesProxy
... and/or ...
(echo -e 'GET http://google.com/
On Sat, Jun 20, 2020 at 11:12:51AM +0200, Joo Nasss wrote:
> How can I Install Network Intrusion system for the whole system
just as you would on any other fedora.
(or whatever distro template you are using for your netvm)
You received this message because you are subscribed to the Google
On Fri, Jun 12, 2020 at 12:49:04PM +, taran1s wrote:
> - - set a higher encryption from qubes default to aes 512-bit full disk
a) there is no "aes 512".
b) the qubes default is aes-xts-512. (which is really aes-256 with
two different keys since whoever implemented it for
On Wed, Jun 10, 2020 at 10:28:22PM -0700, ramboman...@gmail.com wrote:
please dont top-post here.
> The reason I was specifying virtual hard drives and not partitions, is
> functionalities it offers, I am trying to reproduce a virtual file server
> containing many hard drives so I can
On Fri, Jun 05, 2020 at 08:05:50AM -0700, romandash...@gmail.com wrote:
> I can passthrough GPU to *one* of the VMs for computational purposes. But
> for display purposes, I still must connect my monitor to the motherboard
> display port only. Correct?
the question of where the physical port is
On Thu, Jun 04, 2020 at 01:45:26PM +0200, haaber wrote:
> how do you use qvm-run if qubes won't boot? First step is a always
> proper backup, on some external drive. That is what I wrote in my other
i recommend to read what this thread is about.
the user installed qubes to a new ssd
> On 6/3/20 10:58 PM, Boot problems wrote:
> > How do I restore a mounted vm using dd?
qvm-run -p HELPERVM "sudo cat /dev/mapper/qubes_dom0-vm--VMOLD--private" | sudo
dd conv=sparse of=/dev/mapper/qubes_dom0-vm--VMNEW--private
this assumes you have the old disk opened in HELPERVM,
the old vm
On Sun, May 31, 2020 at 04:59:43PM -0700, Boot problems wrote:
> Using fdisk -l /dev/xvdi shows me 2 partitions only, a 200m EFI System
> and xvdi2 a 931G Linux file system, there are no more partitions even
> if I decrypt, mount and fdisk -l /dev/xvdi2
after the luksOpen, check with lvm tools:
On Sun, May 31, 2020 at 01:57:24PM -0700, Boot problems wrote:
> /dev/xvdi but using that it just says permission denied.
so use "sudo fdisk -l /dev/xvdi"
> the cryptsetup luksOpen /dev/xvdi2 name, then it says access denied, I
so use "sudo cryptsetup luksOpen /dev/xvdi2 name"
On Sun, May 31, 2020 at 12:45:22PM -0700, Boot problems wrote:
> Hello, I wanted to migrate from my old hhd to a new ssd, I installed
> could it be a grub issue? What can I do?
assuming you were NOT reinstalling because you were compromised...
- just boot your new qubes system
- with the
On Sun, May 31, 2020 at 11:55:15AM +0200, haaber wrote:
> Thank you! I removed my debian-9 template long ago (surprised?), but I
> could re-install one for building. Just to evaluate the time-cost: how
> would "downgrade" work?
just install the right rpm for either kernel or debian template.
On Sun, May 31, 2020 at 09:07:14AM +0200, Joo Nasss wrote:
> Qubes 4.0.3 don't Install on revodrive
> There comes an Error that ist failed to make DM RAID
not familiar with revodrive, but for installing to a different kind
of barely-supported storage (internal eMMC via sdhci-pci driver) i
On Sat, May 30, 2020 at 09:46:57AM +0200, Zbigniew Łukasiak wrote:
> > > > disable sys-usb autostart.
> > > maybe "lock out" refers to a USB keyboard ?
> > yes, that is how i read it, and that is what my suggestions for
> > dealing with the update are about.
> Yes - I have an USB keyboard. So
> > disable sys-usb autostart.
> maybe "lock out" refers to a USB keyboard ?
yes, that is how i read it, and that is what my suggestions for
dealing with the update are about.
You received this message because you are subscribed to the Google Groups
On Fri, May 29, 2020 at 11:09:00PM +0200, Magali Bardet wrote:
> Does anyone know what is the problem ? How can I solve it ?
use "qvm-block" instead of "qvm-usb" to attach it to another qube.
(or the block instead of the usb section of the device widget)
You received this message because
On Thu, May 28, 2020 at 09:26:34AM +0200, Zbigniew Łukasiak wrote:
> My sys-usb uses a very old template. I tried some googling - but
> failed to find any advice about update it without locking me out of
> the system.
disable sys-usb autostart. and reboot.
now you can replace the sys-usb
On Wed, May 27, 2020 at 07:30:29AM -0700, Dave wrote:
> The upgrade process for Standalone Fedora-31-work-test worked up until the
> end when it complained about disk space.
> *dnf --releasever= distro-sync --best* --allowerasing
uh, since you do not seem to follow the fedora upgrade guide
On Mon, May 25, 2020 at 02:23:08AM -0700, sschi...@gmail.com wrote:
> On Saturday, 23 May 2020 17:24:42 UTC+2, qubeslover wrote:
> Is there any plan to create a package for Qubes Dom0 repo for the future?
> We are planning to collaborate with Qubes folks on packaging it.
On Mon, May 25, 2020 at 12:08:49AM +0200, Caroline Villinger wrote:
> Because I suspect that you can no longer use them with Qubes OS.
> That's why I'm interested in whether there is such software in Qubes OS.
for these questions, qubes is "just another linux".
if you have a working solution for
On Wed, May 20, 2020 at 02:01:21PM +, 'Matt Drez' via qubes-users wrote:
> > `qvm-run gnome-terminal`
> that did not work, but this one had a different error code:
> `Command failed with code: 1`
check the output by adding a -p:
qvm-run -p gnome-terminal
it might actualy tell you
On Tue, May 19, 2020 at 11:14:45AM +0200, haaber wrote:
> Hello there, I was thinking about the usefulness of a qvm-print command
> that takes an input file, sends it to the "printing-VM" (defined in some
> config file), and launches there a document viewer (defined in the
> config file) in order
On Mon, May 18, 2020 at 02:38:34PM -0700, TheGardner wrote:
> [user@sys-firewall ~]$ df -h /var/lib/qubes/dom0-updates
> /dev/xvda3 9.6G 8.7G 450M 96% /
> sudo mkfs.ext4 /dev/xvdc3
> sudo mount /dev/xvdc3 /var/lib/qubes/dom0-updates
> Do I have to change (back) somethings, after I
On Mon, May 18, 2020 at 03:33:02AM -0700, TheGardner wrote:
> - Setting the space up to 4096 on sys-firewall > same result
the default download location in udaptevm is /var/lib/qubes/dom0-updates
so with a default appvm layout that is inside the rootfs (or its overlay).
you can check if this is
On Sat, May 16, 2020 at 07:25:59PM -0700, sjill...@gmail.com wrote:
> nvme0n1p 953G (hd1)
> nvme0n1p1 1MBIOS boot efi (hd1,1)
this is WAY too small.
make it at least 100M, better 500M or even 1GB.
here a single set of xen+linux+initrd is about 35-40MB, and
in general you
On Sat, May 16, 2020 at 06:22:20AM -0700, sarru1...@gmail.com wrote:
> > you need at least one usable template, and in general for a q4.0.3
> > install that means fedora-30.
> but I'm not able to connect to the internet. It's not showing sys-net,
> nothing. How can I troubleshoot for an
> > stderr: “qubes-prefs:error: “No such domain:\’fedora-30\””
this indicates you do not have a fedora-30 template.
did you deselect templates during install?
you need at least one usable template, and in general for a q4.0.3
install that means fedora-30.
(and the first thing you should do
On Thu, May 14, 2020 at 06:56:56PM +0200, onelovecisco via qubes-users wrote:
> In PHV mode like Fedora-31 or Debian-10.
> Is the Qubes-builder capable of this?
qubes-builder most certainly can not build bsd templates.
but like almost any PC OS, you can install it in hvm mode,
and that should
On Thu, May 14, 2020 at 06:06:43AM -0700, email@example.com wrote:
> Does anyone have an idea what is wrong and how to fix it?
"dom0:mmcblk0" and "usb storage" doesnt match up too well.
on this computer the dom0:mmcblk0 is a pci device entirely unrelated
to anything USB.
check what kind of
On Mon, May 11, 2020 at 01:48:58AM -0700, matteochicarella...@gmail.com wrote:
> Firstly, is it safe to have Windows and Qubes on the same machine? I
> use VeraCrypt for full disc encryption
veracrypt does not support actual full disc encryption.
> Also, I've got a 2TB external HDD, would it
On Sun, May 10, 2020 at 06:00:49PM -0700, Catacombs wrote:
> am trying to find a USB Wireless Dongle which comes pre installed in
> the Kernel. But.
there is only exactly _one_ wifi usb dongle that is documented to
work with qvm-usb (aka linux usbip) _and_ has a driver included
On Sun, May 10, 2020 at 08:21:03PM +0200, jiggermas...@posteo.de wrote:
> [user@dom0 ~]$ sudo vgs
> VG #PV #LV #SN Attr VSize VFree
> qubes_dom0 1 168 0 wz--n- 701.28g 100.00g
this means the VG is already the right size.
for resizing the pool, google "how to resize an lvm
(please dont top post)
On Sun, May 10, 2020 at 07:51:01PM +0200, jiggermas...@posteo.de wrote:
> Yes, that's what I mean, mixed up terminology there. The pool has now
> 584 GiB, before the reinstall it had around 670 GiB - I am wondering
> where that additional 84 GiB ended up (and I need it,
On Sun, May 10, 2020 at 05:12:04PM +0200, jiggermas...@posteo.de wrote:
> The partition size for the LVM correctly shows about 700 GiB, but the
> root storage then only gets 584, and I am not able to set it higher.
the root partition is just the root partition for dom0.
if you want to see how
On Sun, May 03, 2020 at 10:01:40PM +0100, lik...@gmx.de wrote:
> Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO
> I2C Controller #0
that is not a USB controller.
> Any ideas to resolve that?
make sure to attach the right device.
if you are trying to assign a USB
On Thu, May 07, 2020 at 08:30:14AM -0300, Franz wrote:
> I installed into Fedora 31 template a proprietary banking rpm
> application/plugin/extension which is supposed to work with the browsers
> during banking tasks. This is called warsaw_setup_fedora_64.rpm
this sounds like a terrible idea
On Wed, May 06, 2020 at 09:31:50PM -0700, viktor.ransm...@gmail.com wrote:
> >> i recommend to keep your one-generation-outdated mainline-template
> >> around (even if it is EOL) if you can spare the diskspace.
> >> if you manage to wreck your new mainline template some way, it is
> >> easier
On Wed, May 06, 2020 at 06:17:58PM +, 'Matt Drez' via qubes-users wrote:
> My problem is that I don't see their individual IP addresses in the
> capture just a NAT'd address of SPS's eth0. I supposed I have to
> create a bridge somehow but that's way beyond my skills.
you are simply sniffing
On Wed, May 06, 2020 at 12:02:55PM +0200, haaber wrote:
> > https://labs.f-secure.com/advisories/saltstack-authorization-bypass
> Thanks for the source. How do you infer that this "doesn't apply" (and
> maybe "did never apply") to qubes? Recall my question: where does salt
sm1> Qubes uses Salt, and there's something nasty going around:
sm2> to be used "by hand only" we could enforce risk = 0 by the above formula
sm2> and keeping fingers off salt for a while. Thanks!
sm3> There was today an update for all templates related to the
On Wed, May 06, 2020 at 06:21:00AM +, lamboicarus via qubes-users wrote:
> I am wondering if anyone knows how I might install grub for use with
> an encrypted boot partition, or no boot partition at all. I have
> recently decided to use btrfs, and I have grub working fine. The
On Tue, May 05, 2020 at 11:36:27PM +0530, Anil wrote:
> By the way, as I write this mail, the keyboarding is again acting up:
> sometimes eating up space, sometimes emitting two for one key press.
> It was working well the whole day.
did you try asking the internet about this problem?
On Tue, May 05, 2020 at 11:25:53PM +0530, Anil wrote:
> I tried to use a USB keyboard, but of course that won't work in Qubes.
that is not a "of course" qubes thing but your choice / configuration.
you can use a USB keyboard with qubes if you want to, including
for entering luks passphrase.
On Mon, May 04, 2020 at 11:21:18PM +0200, Olaf Klinke wrote:
> Where in the documentation is that stated? The manpage of qvm-device
> does not mention this. The only hint is that all examples of qvm-usb in
> the documentation show sys-usb as backend.
for example in the documentation about usb
On Mon, May 04, 2020 at 12:28:27PM -0700, viktor.ransm...@gmail.com wrote:
> If I'd like to remove any old & **unused** Template VMs (e.g. Debian 9,
> Fedora 29, etc.) all I have to do is to start the Qubes Manager, select the
> template I'd like to remove - and - select 'Delete qube' ...
On Mon, May 04, 2020 at 09:12:59PM +0200, Ulrich Windl wrote:
> Is it possible to set a flag that makes fsck do a full filesystem
> check on the next boot?
> Havent found one for ext3...
use tune2fs to set the current-mountcount (-C) to something bigger
than the max-mountcount (check with -l,
On Sat, May 02, 2020 at 11:11:34PM -0700, Caroline Villinger wrote:
> Would you be willing to give us all the files we need for the translation?
> If you agree, it would be very nice if you could give us an answer.
the qubes-translation mailinglist might be a
On Sat, May 02, 2020 at 01:00:55PM -1000, anon wrote:
> Last metadata expiration check: 1 day, 9:07:55 ago on .
the easiest way to "encourage" it to fetch a fresh repo index
is the --clean parameter.
as in: sudo qubes-dom0-update --clean qubes-template-fedora-31
You received this message
On Sat, May 02, 2020 at 11:01:06PM +0200, Olaf Klinke wrote:
> I presume dom0 did not recognize the drive as a USB device and hence
> refuses to attach as such? `qvm-usb` yields the empty list.
oh right, you just came full circle:
attaching USB devices is not going to work without a usbVM.
> was really unrisky and straightforward scripting, why did the Qubes OS
> installer not offer this choice, let alone just do it?
a mix of historic reasons and expecting users to do their homework.
without a sys-usb, you can not really use usb devices with qubes.
and _trying_ to use them will
On Sat, May 02, 2020 at 03:14:42AM +, 'Zsolt Bicskey' via qubes-users wrote:
> > Set the VLAN correctly?
> yes, as I said if I connect a Windows latptop it works right away
> > Set all parameters necessary to satisfy any port security on the switch?
> Yes, same answer as above
On Sat, May 02, 2020 at 01:23:53AM +0200, Olaf Klinke wrote:
> just lacking the knowledge how different writing to a CD is from
> reading from CD, on the hardware level. Is there more to burning a CD
> than a single block special device?
try attaching it as a USB-device instead of a block device.
On Fri, May 01, 2020 at 04:33:55PM -0500, Sven Semmler wrote:
> So make sure to remove those from your grub/EFI config before rebooting!
yes, that would be what the second qubesctl call does.
there should be no need for manual config editing during this.
> The USB qube will work anyway but if
On Fri, May 01, 2020 at 10:33:08PM +0200, Olaf Klinke wrote:
> > > and my keyboard / mouse uses sys-usb. I need to have this appVM
> > > running to use the peripheral obviously. But, since the appVM
> > > running, I can't update the templateVM?
if you really _need_ sys-usb (== only
On Fri, May 01, 2020 at 06:18:10PM +0200, Dieter wrote:
> I tried accessing data on an old qubes (3.2) drive that doesnt boot
> However after decryption I only see the lvms "qubes_dom0-swap" and
> reading from dom0 is no problem but how can I access the other VMs?
On Fri, May 01, 2020 at 11:19:45AM +0530, Anil wrote:
> system perhaps? Or better, some older version of NUC or other mini PC?
NUCs will not allow you to do anything weird with the firmware,
so no me_cleaner or coreboot or so.
they work reasonably well with qubes.
> I know Purism is selling a
On Wed, Apr 29, 2020 at 03:10:48PM -0300, Franz wrote:
> I tried fsck on dom0, but got the enclosed terror screen.
it would have helped if you had tried to fsck the right filesystem:
and if it is asking for repair a bazillion times, perhaps with
On Wed, Apr 29, 2020 at 08:11:37AM -0300, Franz wrote:
> Did it with Fedora 30, but with exactly the same result
> But checking other VMs I am getting the same error on some of them :((
> So this is a widespread problem.
did you try to google your problem?
because at this point it is starting to
On Tue, Apr 28, 2020 at 03:26:44PM -0300, Franz wrote:
> > a) check what the actual size is:
> > dom0$ sudo lvs -a | grep yourvmname
> > => whats the size of the yourvm-private volume?
> did it, but there is no unit, so number are difficult to interpreter,
> snapshot enclosed
and just to shred that last bit of misinformation the other two
responses skipped ...
On Tue, Apr 28, 2020 at 12:44:38AM +, '[NOTIFICATION]' via qubes-users
> It would be great if you opened up QUBES for worldwide editing and
> audit and development.
On Mon, Apr 27, 2020 at 09:06:41PM -0300, Franz wrote:
> So, it seems that Qubes Manager, Nautilus and df are consistent, telling
> that available space is almost 5GB totally used.
> But Qubes VM settings with Private Storage Max Size of 18524 MB is totally
a) check what the actual size is:
On Mon, Apr 27, 2020 at 11:34:30AM +0800, Sandy Harris wrote:
> Can the OS be booted from the network?
short answer: no.
> Can I avoid the problem by booting Qubes-OS from the network?
"i dont trust the vendor bios"?
how would running an even more complex untrusted bios solve the
On Sun, Apr 26, 2020 at 01:16:42PM -0700, Harold Smith wrote:
> TPM and TXT were listed as required for AEM in the recommended section, so
> i'll disable TXT and TPM, I have vt-x with ept and vt-d and I;ll try again.
you can also just keep them enabled.
you can use the TPM for whatever you
On Sun, Apr 26, 2020 at 09:17:10PM +0200, Olaf Klinke wrote:
> it seems that some iptables rules are set on VM boot that redirect port
> 53 requests, but I can't get iptables inside the AppVM to divulge these
those rules should exist in your external netvm (sys-net), and point to
On Sat, Apr 25, 2020 at 05:09:46PM -0700, Harold Smith wrote:
> Hello, I'm getting ready to Intall Qubes onto a machine, I can't find any
> information about TPM settings, apart from that TPM is required.
where did you get that impression?
qubes doesnt use a TPM, much less require one.
On Sat, Apr 25, 2020 at 06:45:11PM +0200, 'Max Andersen' via qubes-users wrote:
> Hi there,
> After upgrades to latest kernel and several other updates, enabling
> sound, I still need support for t
your message looks incomplete/corrupted.
but the most likely answer to your unasked
On Wed, Apr 22, 2020 at 11:29:30PM +0200, Frédéric Pierret wrote:
whats with the top-posting, eh? :P
> From a brief look, it's due to newer Fedora pulseaudio and our Qubes
> package requires older one. I'll try to fix that soon.
actualy it seems to have been fixed some days ago and is now in
On Mon, Apr 20, 2020 at 01:12:20AM -0700, l319...@gmail.com wrote:
> I have tried what Matthew did and you pointed to but I still have dom0 time
> an hour behing from what it supposed to be. Weird as both dom0 timedatectl
> and sys-net vm how same timezone
a) run "qubes-prefs clockvm" in dom0.
On Fri, Apr 17, 2020 at 02:53:01PM -0700, Catacombs wrote:
> I would have thought someone could suggest a more trustworthy RNG.
there is no real problem with using the intel RNG.
if it is as part of a proper software RNG setup.
(just dont use anything handpatched by debian devs... *coughs*)
On Fri, Apr 17, 2020 at 02:06:19AM -0700, Catacombs wrote:
> It is my understanding that “the “Number Generator” is on the MOBO.
> Could the “Intel Management Engine” be changed to alter the RNG
> to create weakened Encryption?
> Could the IME be altered to load malware to steal
On Wed, Mar 25, 2020 at 04:21:29PM +0100, GD rub wrote:
> Device BootStart End Sectors Size Id Type
> /dev/xvda1 *2048 29360127 29358080 14G 83 Linux
> /dev/xvda2 18946048 20969471 2023424 988M 82 Linux swap / Solaris
urgh! be super careful there.
your xvda2 is
On Wed, Mar 25, 2020 at 03:12:04PM +0100, GD rub wrote:
> You can't do that on the root filesystem. resize2fs is permissible only if
> the partition is unmounted.
actualy, no, resize2fs works just fine on a mounted filesystem.
> > > Device BootStart End Sectors Size Id Type
On Mon, Mar 23, 2020 at 05:48:29AM -0700, peebl...@gmail.com wrote:
> asking me in which VM i want to open the file.. So it seems the command
> line parameter for VM is not taken into account..
it probably is, but you need to authorize it anyways: security.
> How can I fix this?
On Sun, Mar 22, 2020 at 05:07:44AM -0700, max via qubes-users wrote:
> [max@dom0 ~]$ sudo qubes-dom0-update
> --enablerepo=qubes-dom0-current-testing qubes-template-fedora-31
try with --enablerepo=qubes-templates-itl-testing
You received this message because you are subscribed
On Sun, Mar 22, 2020 at 11:57:38AM +0100, haaber wrote:
> > Assuming you didn't make backups before the crash: You need to have a
> > running Qubes system to backup VMs the normal way.
> Does that mean Chris, that in case of a disaster, there is no way to
> backup your data "by hand" (booting a
On Fri, Mar 20, 2020 at 11:07:55PM +, 'jrsrrs33' via qubes-users wrote:
> to understandif my computer is compatible or not and in this case,
> what should I install? qubes 3.2 or qubes 4.0.3?
do not use qubes 3.x ... it has been deprecated for a long time now.
please do use qubes 4.0.3 ...
On Wed, Mar 18, 2020 at 11:56:31AM -0300, Franz wrote:
> When a laptop is always connected to power, e very good behavior to
> strongly prolong battery life is to avoid charging it to 100% and limiting
> it to lower threshold, perhaps 80%.
i am using a (perl) script for doing this on my qubes
On Wed, Mar 11, 2020 at 10:46:12AM -0700, redpoll...@gmail.com wrote:
> I've downloaded some ubuntu templates with the .rpm extension. I have been
> told by someone that I need to put the rpm file into dom0 and then install
> via cli with dnf etc.
this means you are giving the person who
On Sat, Mar 07, 2020 at 03:08:13PM -0800, A wrote:
> Is it possible to get an app like WinAuth for Linux or what do you use
> for 2 step verification ?
You received this message because you are subscribed to the Google Groups
On Thu, Mar 05, 2020 at 01:21:47PM -0500, Chris Laprise wrote:
> You can also qualify the model somewhat and say that an attacker cannot
> successfully infect all of your (hopefully diverse) computers, so that makes
the diversity bit is important.
and if its mainly about validating a download,
On Thu, Mar 05, 2020 at 05:48:36PM +, 'Ian' via qubes-users wrote:
> I've just started using Qubes and I'm trying to ease transition from
> my current virtualbox based setup by just importing my virtualbox VMs
> as HVMs.
> 1. Resolution above 1920x1080 (the host is 2560x1440,
On Thu, Mar 05, 2020 at 03:56:55PM +, Mark Fernandes wrote:
> Well that's an idea. But still what if the software you are being 'fed' is
> all tampered software, so that after replacing the computer, as soon as you
> use software, you are compromised again?
> Purchasing a new computer can also
On Thu, Mar 05, 2020 at 03:30:26PM +, Mark Fernandes wrote:
> So if your computer has been compromised, the methods you suggest may be
if your computer has been compromised to the point where
you dont trust it to verify a signature, you need a new
computer to install qubes on.
could you please try to at least spell the name right?
this is giving my inner monk a headache...
On Thu, Mar 05, 2020 at 02:40:18PM +, Mark Fernandes wrote:
> The only thing relevant to this topic in the guide, appears to be the
> information on verifying signatures (which is of course
On Thu, Mar 05, 2020 at 04:54:45AM -0800, Rafael Reis wrote:
> Could be and MTU issue. I had trouble with Qubes, VPNs, TOR and PPOE
> connection due to it’s unusual MTU size (lower than 1500). Maybe the
> experts could shed some light into how Qubes deals with MTU across VMs
qubes? not at all.
On Tue, Mar 03, 2020 at 12:20:57PM -0800, Eva Star wrote:
> collection ticket:
> > https://github.com/QubesOS/qubes-issues/issues/3778
> Thanks! Yes, exactly this issue. Can I use passthrough mode if I will
> connect external 2.0 usb hub to my current notebook usb port and then
On Tue, Mar 03, 2020 at 09:43:56AM -0800, Eva Star wrote:
> Get this error. Please, how to fix? Cable is fine. It work on non virtual
> environment on other machine.
> [ 64.124877] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
this most likely means your device is not supported by
On Sat, Feb 29, 2020 at 08:02:25AM +0100, A E wrote:
> When I execute "sudo mount /dev/xvdi /mnt" in the terminal of the VM, I get
> this error: “mount: /dev/xvdi/mnt: can’t find in /etc/fstab.
that error doesnt match the command. one of them must be incorrect.
if the error is real, it indicates
On Fri, Feb 28, 2020 at 06:00:04PM -0600, Sven Semmler wrote:
> You want your sys-firewall to be separate from sys-net for the same
> reason: compartmentalization.
as usual "depends on your threat model".
if you are into outbound-firewalling of appvms, not doing so in the
appvm makes a lot of
1 - 100 of 137 matches
Mail list logo