Le samedi 23 décembre 2017 23:57:25 UTC+1, awokd a écrit :
> On Sat, December 23, 2017 10:14 pm, "Marek Marczykowski-Górecki" wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> >
> > On Sat, Dec 23, 2017 at 07:09:22AM -, awokd wrote:
> >
>
> > Just
On Fri, Dec 22, 2017 at 4:18 PM, Holger Levsen wrote:
> On Fri, Dec 22, 2017 at 02:34:41AM -0800, Reynir Björnsson wrote:
>> It may be a coincidence, but when it happened to me I got sys-net running by
>> shutting down sys-whonix first. I've since disabled sys-whonix and
On Sun, December 24, 2017 9:04 am, Kushal Das wrote:
> Hi,
>
>
> My sys-firwall is stuck at the boot time (with no limit) 4.0rc3
> (updated). Is there anyway to boot
> into dom0 without starting any other vm? Then I can remove and create the
> sys-firewall vm again (or if there is any easy way to
> "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
Hi,
My sys-firwall is stuck at the boot time (with no limit) 4.0rc3
(updated). Is there anyway to boot
into dom0 without starting any other vm? Then I can remove and create
the sys-firewall vm again (or if there is any easy way to recreate the
vm). My primary Qubes laptop is not usable state
On Sun, December 24, 2017 9:47 am, Frédéric Pierret (fepitre) wrote:
> Hi, I have also some free time (holidays!), as I have already prepared
> updated ISO for myself, I will give you some help on it.
Thanks! I'll ping you off list.
--
You received this message because you are subscribed to
On Saturday, 23 December 2017 11:23:39 UTC+2, Reynir Björnsson wrote:
> Hi,
>
> On Friday, 22 December 2017 22:59:24 UTC+1, Roy Bernat wrote:
> > On Friday, 22 December 2017 23:51:29 UTC+2, donoban wrote:
> > > >Hi All
> > > >
> > > >i tried to install mirage-firewall followed by the Readme .
On 12/24/2017 04:04 AM, Kushal Das wrote:
Hi,
My sys-firwall is stuck at the boot time (with no limit) 4.0rc3
(updated). Is there anyway to boot
into dom0 without starting any other vm? Then I can remove and create
the sys-firewall vm again (or if there is any easy way to recreate the
vm). My
On Sunday, 24 December 2017 02:09:54 CET Marek Marczykowski-Górecki wrote:
> > sudo lvcreate -L 390.5g -n data Slow
>
> You need yo create those as thin pools, not standard volumes. For
> example this way:
> lvcreate -L 37g --thinpool systems qubes_dom0
Thanks, that fixed it :-)
It took some
Okay so I read all of that lol, and I understood it all but what if there was
an e-mail client that used the browser method? You get logged in to all your
emails without retrieving anything then switch to cookie authentication and
forget the password, that way when the zero-day happens you only
On 2017-12-23 11:11, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2017-12-22 21:30, yreb...@riseup.net wrote:
>> On 2017-12-22 09:50, awokd wrote:
>>> On Fri, December 22, 2017 10:29 am, 'Tom Zander' via qubes-users
>>> wrote:
On Friday, 22 December
On 12/24/2017 06:56 AM, Roy Bernat wrote:
Hi All ,
using qubes 4rc3 ( 16GB i7 7500 ) . the appvm is based on fedora26. i saw
something weird, i put min memory 800, max mem 8000 , 4 cpu . and for some
reason the memory is stuck on 3742 always.
This cause everything to be very very slow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-12-24 19:08, yreb...@riseup.net wrote:
> On 2017-12-23 11:11, Andrew David Wong wrote:
>> On 2017-12-22 21:30, yreb...@riseup.net wrote:
>>> On 2017-12-22 09:50, awokd wrote:
On Fri, December 22, 2017 10:29 am, 'Tom Zander' via
Hi All ,
using qubes 4rc3 ( 16GB i7 7500 ) . the appvm is based on fedora26. i saw
something weird, i put min memory 800, max mem 8000 , 4 cpu . and for some
reason the memory is stuck on 3742 always.
This cause everything to be very very slow when i add more apps .
Any ideas ?
R
I have used Qubes 3.2 in the past with Windows HVM without any problems.
I setup my Windows Standalone but having issues getting the system to boot with
the iso. It is not even getting to the boot screen.
When I start with the iso I get the error msg:
Got empty response from qubesd. See
On Sun, Dec 24, 2017 at 3:14 PM, awokd wrote:
>
> It's not very elegant but this should work:
>
> Boot from your Qubes install media
> Troubleshooting
> Rescue a Qubes system
> 1
> Enter
> chroot /mnt/sysimage
> nano /var/lib/qubes/qubes.xml
> look for the line with
On 12/24/2017 12:57 PM, Roy Bernat wrote:
>
> Hi
>
> Not seems to work for me .
>
> Ideas ?
>
> R
>
Could you paste your 'qvm-prefs mirage-firewall' output?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group
Actually, having a malicious hardware attached at boot time is something hard
to defend. Even if Xen does not attach the hardware to dom0, there is some
pre-Xen phase of boot – BIOS/UEFI. Qubes cannot affect this phase of boot. If
you have attached a malicious device that for example pretends
On Sunday, 24 December 2017 16:24:37 UTC+2, donoban wrote:
> On 12/24/2017 12:57 PM, Roy Bernat wrote:
> >
> > Hi
> >
> > Not seems to work for me .
> >
> > Ideas ?
> >
> > R
> >
>
> Could you paste your 'qvm-prefs mirage-firewall' output?
autostart D False
backup_timestamp
19 matches
Mail list logo