-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-14 09:12, jasonwalshismyn...@gmail.com wrote:
>
>> Did you proceed to upgrade your TemplateVMs according to the
>> instructions after upgrading dom0?
>
> after rebooting as decribe in step #7 from upgrading dom0 (Reboot
> Dom0) :
>
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-14 12:30, superlative wrote:
> On Saturday, December 10, 2016 at 1:44:58 PM UTC-8, superlative
> wrote:
>> I got Tor browser on Whonix vm to work by updating the whonix-ws
>> template vm
>
> I'm considering adding the HCL support files
Hi,
when trying to recreate the dvm after the latest torbrowser update I get:
qvm-create-default-dvm whonix-ws
[...]
DVM savefile created successfully.
cp: error writing '/dev/shm/qubes/current-savefile': No space left on device
And DVM starting fails after that obviously.
Do I have to resiz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 01:40, Joonas Lehtonen wrote:
> Hi,
>
> when trying to recreate the dvm after the latest torbrowser update I get:
>
> qvm-create-default-dvm whonix-ws
>
> [...]
> DVM savefile created successfully.
> cp: error writing '/dev/shm/qube
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 15, 2016 at 03:01:09AM -0800, Andrew David Wong wrote:
> On 2016-12-15 01:40, Joonas Lehtonen wrote:
> > Hi,
> >
> > when trying to recreate the dvm after the latest torbrowser update I get:
> >
> > qvm-create-default-dvm whonix-ws
> >
Hi Tim,
Drew White is correct.
This is an installer bug.
There are two separate Qubes installers, the GUI one and the Text one. The
problem is that the Text one has different options and has a fixed error that
cannot be bypassed. The error is that LUKS encryption, either cannot be
disabled
Okay, stuck again. Downloaded a fresh d8 template, updated it and built kernel
again to have a clean slate to work from. Everything builds, no error beside
the expected ones afterwards. But when i switch to pvgrub2 and boot, it shuts
down seconds after boot attempt. Full log attached.
.[30m.[47
Hi all,
Has anyone managed to work out how to get past the Text based LUKS installer
bug?
Thanks,
Rob.
--
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-u
On 12/15/2016 05:00 AM, Foppe de Haan wrote:
> Okay, stuck again. Downloaded a fresh d8 template, updated it and built
> kernel again to have a clean slate to work from. Everything builds, no error
> beside the expected ones afterwards. But when i switch to pvgrub2 and boot,
> it shuts down seco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 04:00, r...@bluesentinel.net wrote:
> Hi Tim,
>
> Drew White is correct.
>
> This is an installer bug. There are two separate Qubes installers,
> the GUI one and the Text one. The problem is that the Text one
> has different options
On 12/15/2016 06:01 AM, Reg Tiangha wrote:
> On 12/15/2016 05:00 AM, Foppe de Haan wrote:
>> Okay, stuck again. Downloaded a fresh d8 template, updated it and built
>> kernel again to have a clean slate to work from. Everything builds, no error
>> beside the expected ones afterwards. But when i s
Hello @qubenix,
I am interested in your Kali installation process. Did you run into any trouble
during the installation? Did you follow the KaliVM installation instructions:
https://www.qubes-os.org/doc/pentesting/kali/?
regards
j. Eppler
--
You received this message because you are subscri
>> I haven't encountered this before, but it sounds like the Tor Browser
>> update might've pushed you over the default 2 GB size limit. Maybe try
>> increasing the size of your DVM template?
>
> Storing savefile in /dev/shm (tmpfs - stored in RAM only) is an
> optimization to load it faster. Norm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 15, 2016 at 01:24:00PM +, Joonas Lehtonen wrote:
> >> I haven't encountered this before, but it sounds like the Tor Browser
> >> update might've pushed you over the default 2 GB size limit. Maybe try
> >> increasing the size of your D
> Yes, I see the problem. It sounds like your ServiceVMs are based on
> debian-8. Have you tried basing them on the default Fedora template
> instead?
Ok, I have now assign sys-net & sys-firewall to fedora-23 TemplateVM, I still
have the same qmemman error.
Is it normal that when I start my co
Some questions:
1) How to disable "restore windows" at startup? I mean when I shutdown Q
and I have opened dom0 console, then this console show after reboot on
the desktop. How to disable? I'm already tried "Sessions and Startup" -
"Xfce Teminal" - Never. then after reboot it reset to default
>> When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
>
>> I changed that to 1000MB and everything works again.
>
> Why that high?
since its preset value was over 2800 I didn't want to reduce it to much
but I just found out that something changes that value. (I did set it to
1000 i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 05:35, jasonwalshismyn...@gmail.com wrote:
>
>> Yes, I see the problem. It sounds like your ServiceVMs are based
>> on debian-8. Have you tried basing them on the default Fedora
>> template instead?
>
> Ok, I have now assign sys-net &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
>
> >> When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
> >
> >> I changed that to 1000MB and everything works again.
> >
> > Why that high?
>
> since its preset valu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 05:40, Joonas Lehtonen wrote:
>
>>> When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
>>
>>> I changed that to 1000MB and everything works again.
>>
>> Why that high?
>
> since its preset value was over 2800 I didn't wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 05:45, Marek Marczykowski-Górecki wrote:
> On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
>
When I look at whonix-ws-dvm "initial memory" it says:
~2800MB
>>>
I changed that to 1000MB and everything wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 05:41, Eva Star wrote:
> Some questions:
>
> 1) How to disable "restore windows" at startup? I mean when I
> shutdown Q and I have opened dom0 console, then this console show
> after reboot on the desktop. How to disable? I'm already t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 15, 2016 at 05:49:18AM -0800, Andrew David Wong wrote:
> On 2016-12-15 05:45, Marek Marczykowski-Górecki wrote:
> > On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
> >
> When I look at whonix-ws-dvm "initial memory"
Andrew David Wong:
> I don't understand. Isn't the target TemplateVM shut down when
> qvm-create-default-dvm is called? How could it be using any memory
> while it's shut down?
This is not about the initial memory of the used templateVM (in this
case whonix-ws) but about whonix-ws-dvm. (qubes ma
On Wednesday, December 14, 2016 at 3:38:24 AM UTC-8, dumbcyber wrote:
> I am reading and responding to this thread on a Macbook Pro 11,1 running
> Qubes R3.2. Andrew and others are right: yes it works, but you need to work
> hard to make it work. I had the keyboard not working issue and in fact
On Saturday, December 10, 2016 at 10:52:29 PM UTC-8, Jean-Philippe Ouellet
wrote:
> 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 sec
When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
>>>
I changed that to 1000MB and everything works again.
>>>
>>> Why that high?
>
>> since its preset value was over 2800 I didn't want to reduce it to much
>> but I just found out that something changes that value. (I did s
> - From this thread:
>
> https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
>
> 'Please check "sudo systemctl status qubes-qmemman", or better "sudo
> journalctl -u qubes-qmemman" for error messages. Then you can restart
> the service with "sudo systemctl restart qubes-qmemman
Hello,
1. have you thought about offering training, consulting and support for
companies who want to use Qubes OS in their enterprise?
2. have you thought about developing commercial management solution which
makes the deployment, remote administration and monitoring easy?
I do not believe that
On 12/15/2016 04:52 PM, Andrew David Wong wrote:
How did you enable this in the first place? My system doesn't do that.
I do not enable this. It's look like session storage, but it's disabled
here `xfce4-sessions-settings`
2) After reboot selected last virtual desktop. How to always
selec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/15/16 07:57, Eva Star wrote:
> On 12/15/2016 04:52 PM, Andrew David Wong wrote:
>>
>> How did you enable this in the first place? My system doesn't do that.
>>
>
> I do not enable this. It's look like session storage, but it's disabled here
>
On 12/15/2016 07:10 PM, Andrew David Wong wrote:
Hm. Not sure if this'll make a difference, but try shutting down
all VMs, then shutting down from the command-line. For example:
$ qvm-shutdown --wait --all
$ shutdown now
I wrote the bash script and at it to the xfce4 launcher. Then I start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/15/16 08:19, Eva Star wrote:
> On 12/15/2016 07:10 PM, Andrew David Wong wrote:
>
>>
>> Hm. Not sure if this'll make a difference, but try shutting down
>> all VMs, then shutting down from the command-line. For example:
>>
>> $ qvm-shutdown --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/15/16 07:43, je wrote:
> Hello,
>
> 1. have you thought about offering training, consulting and support for
> companies who want to use Qubes OS in their enterprise?
Yes, this is something we've considered. We'd prefer to focus on selling
li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/15/16 07:10, jasonwalshismyn...@gmail.com wrote:
>
>> - From this thread:
>>
>> https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
>>
>> 'Please check "sudo systemctl status qubes-qmemman", or better "sudo
>> journalctl -u qu
On 12/15/2016 07:27 PM, Andrew David Wong wrote:
#!/bin/bash
qvm-shutdown --wait --all \
- --exclude=sys-net \
- --exclude=sys-firewall \
- --exclude=sys-usb \
- --exclude=sys-whonix \
- --exclude=sys-whonix \
- --exclude=sys-other-1 \
- --exclude=sys-other-2 \
qvm-shutdown --wait --all
sleep 3
On Thursday, December 15, 2016 at 2:15:20 PM UTC+1, Reg Tiangha wrote:
> On 12/15/2016 06:01 AM, Reg Tiangha wrote:
> > On 12/15/2016 05:00 AM, Foppe de Haan wrote:
> >> Okay, stuck again. Downloaded a fresh d8 template, updated it and built
> >> kernel again to have a clean slate to work from. Ev
On 12/15/2016 09:43 AM, Foppe de Haan wrote:
> On Thursday, December 15, 2016 at 2:15:20 PM UTC+1, Reg Tiangha wrote:
>> On 12/15/2016 06:01 AM, Reg Tiangha wrote:
>>> On 12/15/2016 05:00 AM, Foppe de Haan wrote:
Okay, stuck again. Downloaded a fresh d8 template, updated it and built
ker
On 12/15/2016 09:48 AM, Reg Tiangha wrote:
> On 12/15/2016 09:43 AM, Foppe de Haan wrote:
>> On Thursday, December 15, 2016 at 2:15:20 PM UTC+1, Reg Tiangha wrote:
>>> On 12/15/2016 06:01 AM, Reg Tiangha wrote:
On 12/15/2016 05:00 AM, Foppe de Haan wrote:
> Okay, stuck again. Downloaded a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/15/16 05:58, Marek Marczykowski-Górecki wrote:
> On Thu, Dec 15, 2016 at 05:49:18AM -0800, Andrew David Wong wrote:
>> On 2016-12-15 05:45, Marek Marczykowski-Górecki wrote:
>>> On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
>
> And what happens when you restart qubes-qmemman?
this :
Job for qubes-qmemman.service failed because the control process exited with
error code. See "systemctl status qubes-qmemman.service" and "journalctl -xe"
for details.
"sudo systemctl status qubes-qmemman.service" returns the same kin
J. Eppler:
> Hello @qubenix,
>
> I am interested in your Kali installation process. Did you run into any
> trouble during the installation? Did you follow the KaliVM installation
> instructions: https://www.qubes-os.org/doc/pentesting/kali/?
>
> regards
> j. Eppler
>
Yes, followed the instru
Andrew David Wong:
> On 2016-12-15 05:40, Joonas Lehtonen wrote:
>
When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
>>>
I changed that to 1000MB and everything works again.
>>>
>>> Why that high?
>
>> since its preset value was over 2800 I didn't want to reduce it to
>> mu
I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
it's template. At first everything was working normal, but I've noticed
now that my MAC is only randomized until I connect to a network. At that
point it switches back to the original MAC. Anyone else experiencing this?
Second i
On 12/15/2016 11:50 AM, qubenix wrote:
> I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
> it's template. At first everything was working normal, but I've noticed
> now that my MAC is only randomized until I connect to a network. At that
> point it switches back to the origina
On Sunday, December 11, 2016 at 4:24:25 AM UTC+1, notindoc...@aol.com wrote:
> On Tuesday, October 28, 2014 at 1:26:49 PM UTC-5,
> bm-2cu9wcijafoqtf6...@bitmessage.ch wrote:
> > Dear qubes-users,
> >
> > I am long time qubes follower and user. I apologize in advance if anyone
> > feels this requ
Hi everyone,
Sorry for not getting on this list sooner, however it looks like testing
of coldkernel on Debian is largely going well! I see the most recent
issue from foppe, and will be attempting to reproduce later this evening.
If you run into issues that require coldhak attention, please do not
On Thursday, December 15, 2016 at 10:11:31 PM UTC+1, Colin Childs wrote:
> Hi everyone,
>
> Sorry for not getting on this list sooner, however it looks like testing
> of coldkernel on Debian is largely going well! I see the most recent
> issue from foppe, and will be attempting to reproduce later
On 2016-12-14 13:42, Andrew David Wong wrote:
We have just published Qubes Canary #10.
this announcement should go to [qubes-announce] as well :-)
Qru
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop r
Halo!
I have run into more problems with thunderbird+enigmail on qubes and wonder if
anyone else has problems.
I have a work appvm as Debian 8 with icedove 45.5.1 and enigmail 1.8.2
I have a vault appvm with my gpg keys as Debian 8 to do split gpg.
I updated templates and dom0 today and reboote
15. Dec 2016 21:53 by cu...@tutanota.com:
> I updated templates and dom0 today and rebooted computer. Now when I try to
> look at encrypted email I am prompted to enter my gpg key password every time
> I look at an encrypted email. Also if I look at an encrypted email, go to a
> different pr
> I do not believe that developing a commercial operating system based
on an
> open source foundation will pay off on a long run.
Is there a specific reason you think it will not? Just curious.
1. Selling a license provides a one time payment. Even if you are able to
sell 100_000
https://www.whonix.org/blog/qubes-whonix-dispvm
Before we had just a [stub][1]. Now [Qubes-Whonix][2] [DisposableVMs][3]
are fully [documented][4] thanks to [contributions][5] by the
[community][6]. ([wiki history][7])
**What are DisposableVMs?**
Under the Qubes TemplateVM model, any changes mad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 15, 2016 at 07:10:12AM -0800, jasonwalshismyn...@gmail.com wrote:
>
> > - From this thread:
> >
> > https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
> >
> > 'Please check "sudo systemctl status qubes-qmemman", or be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 15, 2016 at 10:53:56PM +0100, cubit wrote:
> Halo!
>
> I have run into more problems with thunderbird+enigmail on qubes and wonder
> if anyone else has problems.
>
> I have a work appvm as Debian 8 with icedove 45.5.1 and enigmail 1.8.
On Friday, 16 December 2016 01:09:30 UTC+11, pixel fairy wrote:
> On Wednesday, December 14, 2016 at 3:38:24 AM UTC-8, dumbcyber wrote:
>
> > I am reading and responding to this thread on a Macbook Pro 11,1 running
> > Qubes R3.2. Andrew and others are right: yes it works, but you need to
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi everyone,
As those of you who've read Joanna's paper "Intel x86 Considered
Harmful" are well aware, the Intel ME and other closed-source firmware
pose a threat to trustworthy computing. We can do all the awesome
hypervisor and isolation stuff we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 13:46, Qru wrote:
>
> On 2016-12-14 13:42, Andrew David Wong wrote:
>> We have just published Qubes Canary #10.
>
> this announcement should go to [qubes-announce] as well :-)
>
> Qru
>
No, qubes-announce is strictly for QSBs and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 10:58, Reg Tiangha wrote:
> On 12/15/2016 11:50 AM, qubenix wrote:
>> I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
>> it's template. At first everything was working normal, but I've noticed
>> now that my MAC is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 21:52, Andrew David Wong wrote:
> On 2016-12-15 10:58, Reg Tiangha wrote:
>> On 12/15/2016 11:50 AM, qubenix wrote:
>>> I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
>>> it's template. At first everything was wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-15 13:57, cubit wrote:
> 15. Dec 2016 21:53 by cu...@tutanota.com:
>
>> I updated templates and dom0 today and rebooted computer. Now
>> when I try to look at encrypted email I am prompted to enter my
>> gpg key password every time I l
On 12/15/2016 01:58 PM, Reg Tiangha wrote:
On 12/15/2016 11:50 AM, qubenix wrote:
I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
it's template. At first everything was working normal, but I've noticed
now that my MAC is only randomized until I connect to a network. At that
Good morning everyone,
I'm having trouble getting my BCM4312 working under Qubes. I've poked around
the archives a bit and I know from experience that Broadcom and Linux haven't
always been the best of friends, but maybe there's a solution I'm missing.
The card shows up in lspci without any is
63 matches
Mail list logo
