>> The problem is that I also want to have different sets of bookmarks
>> and settings depending on domain (for example, work, school, banking,
>> etc.). Since I want persistent bookmarks and settings, I assume I need
>> to use an AppVM (one per domain) instead of a DispVM, but then I can't
>> get
> I see.. But currently I am using Qubes 3.2 and 4.0 last time I tried was
> VERY unpolished, I am not sure I am going to look at it before support
> for 3.2 expires...
Same here, and my pc doesn't have vt-d nor slat (second level addres
tranlation); both required for Qubes 4
> It's not like I
> I disagree when you say nooone is going to backdoor your bios. I think its
> very common nowadays.
as far as i know there is computrace that is an anti theft system that
gain persistence over the os by dropping an exe that windows will load
at boot time but this works only over fat32 and
> Last weeks there was a lot of talk about a lot of us missing the
> qubes-manager, or frankly any sort of useful graphical user interface.
>
> As I’m a long time programmer I decided to just give this a go and try to
> get something useful going.
> My approach is one where I talk directly to
ion let me know.
Matteo
--
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
>
> Here are some things these users DONT want to do:
> Start a qube
> Stop a qube
> Start a disposableVM
> Look in the manager to see if there are updates.
at least a bit of the inner working must be known: disp vm is useful and
you have to stop a qube that you don't use to
>> update: I doscovered that Legacy Mode is called CSM on some
>> BIOS(https://github.com/QubesOS/qubes-issues/issues/2838#issuecomment-349234545
>> ), so I found that my system actually supports it. However, when I boot
>> into legacy mode, I only see an empty black screen, forever. Here's my
> "there is absolutely no point in not allowing e.g. Thunderbird to remember
> the password – if it got compromised it would just steal it the next time I
> manually enter it"
Correct!
> So this was written 6 years ago but it's the latest one I think.
>
> Can't we just create disposable
>> I guess the benefit of the AppVM over the HVM is Qubes integration for
>> copy and paste and anything else practical?
If you make an AppVM instead of a template (or standalone) only
C:\Users\* will be preserved across reboot.
This is useful to keep the system clean from virus.
C:\Users
Il 02/02/2018 19.20, Matteo ha scritto:
>
>>> I guess the benefit of the AppVM over the HVM is Qubes integration for
>>> copy and paste and anything else practical?
>
> If you make an AppVM instead of a template (or standalone) only
> C:\Users\* w
> Problem is:
> 1)
> I can't really tell if QWT is or is not installed. From the HVM I
> wasn't able to copy out to another AppVM but Frankly:
>
> I don't really follow the protocol To install the QWT, I have it from
> the --repos in dom0 but then I am supposed to once flag it to install
>
> It looks like fullscreen can't do "attacks" on dom0 and other VM's,
but it can do something like keylogging, just visually from the screen
instead, perhaps something akin to taking frequent light sized
screenshots and then sending the screenshots over the internet.
This is possible both if the
> Does anyone know the 'alt+space+f'(fullscreen) command, or where to find it?
> Or are there none available in /bin /usr/bin or similar?
i think that you have to press that keys on the keyboard, is not a
terminal command (in fact you can't find in /usr/bin)
if you press alt+space bar a menu
>> ...switch to cookie authentication and forget the password, that way when
>> the zero-day
>> happens you only lose your cookie which is probably not as powerful as
>> the actual password(ie I dont think you can change your password with
>> just the cookie) plus the zero day can't "permanently"
> Hey, I've tried all sorts of methods to get qubes to install after
> booting from a usb, but it freezes no matter what option I choose. I
> believe it has something to do with my NVIDIA graphics card but I can't
> disable it from my BIOS. Please help!
seems the same issue that you can find
> Dear Qubes Team
> I have a question regarding Qubes and to be specific the way it connects
> to wifi networks.
I'm not part of the Qubes team, i'm just a user.
I don't know if Qubes uses passive discovery, active or both.
But I know how you can find it: you can use another pc with kali live
(or
> I still think seeing results from your test would be really interesting,
> and I could reference it on the Network Manager mailing list. So you
> have a 'yea' vote from me.
>
i have done a test, but i haven't any concrete result :/
i saw that using "airodump-ng --channel 1 mon0"
-on the top
i'm having this problem too, and i don't know how to disable alua
[ 8.319 ] dracut-pre-trigger[547]: cat /tmp/dd_disk: No such file or directory
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
BLOCKS HERE
[ 14.014 ] sd 7:0:0:0:0: alua:
Hi, I'm new to this so bear with me whilst I get a grasp on things
I have a Dell Inspiron 5570 running Windows 10 Home on a 64-bit OS. It's
2TB HDD is fully encrypted with VeraCrypt
I'm looking to buy a 1TB HDD from Amazon to run Qubes on. Would it be
possible to fully encrypt the hard drive and
19 matches
Mail list logo
