Unman:
> On Sat, Sep 16, 2017 at 06:43:00PM +, 0xB44EFD8751077F97 wrote:
>> Using Qubes3.2, I'm attempting to create a communication
>> channel between two VMs. One VM without networking. I'd like to mimic
>> ssh -L port:localhost:port.
>>
>> I think a qrexec rpc should work, but I'm not sure
I have an issue trying to use some internal HDD in a new Qubes R3.2
install. The machine was previously Windows, so the HDD were NTFS
formatted, and they contain various work and backup data. Qubes is on
its own SSD.
Initially Qubes could not see the drives from dom0, so I couldn't attach
them to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Sep 21, 2017 at 04:02:42PM -0300, Franz wrote:
> On Thursday, September 21, 2017, Marek Marczykowski-Górecki <
> marma...@invisiblethingslab.com> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Thu, Sep 21, 2017 at
On Thursday, September 21, 2017, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Thu, Sep 21, 2017 at 12:54:45PM -0400, Michael Carbone wrote:
>> On 09/21/2017 12:47 PM, Franz wrote:
>> > None vm starts except dom0
>>
Hi all.
I assume this is relevant not only for considerations related to the
practical limit/benefit of increasing RAM in existing computers, but also
regarding the specifications when buying new computers.
- At the following amounts of RAM; 8GB -> 16GB -> 24GB -> 32GB -> 48GB ->
64GB, how much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, Sep 20, 2017 at 05:46:56AM -0700, John Maher wrote:
> I've been trying to get my Yubikey to attach to my gpg qube by doing the
> following:
>
>[dom0 ~]$ qvm-usb -a gpg `qvm-usb | grep Yubikey | cut -f1`
>
> but I'm presented with:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Sep 21, 2017 at 12:54:45PM -0400, Michael Carbone wrote:
> On 09/21/2017 12:47 PM, Franz wrote:
> > None vm starts except dom0
> >
> > I am writing this email by a cell phone
> >
> > -Changing the kernel with qubes manager GUI does not
Model: Dell Latitude E6430.
I did a complete and full install and it would boot loop right after the grub
loader.
I went into the bios settings for the performance/processor and disabled
speedstep, anything that has to do with boosting the performance of the
processor. I disabled it
I did
On Saturday, September 16, 2017 at 5:16:33 AM UTC-8, rysiek wrote:
> Hi all,
>
> first of all, hello. Been meaning to sign up for this list for some time,
> some
> of you might remember me from the IRC channel (from when I was setting up my
> own Qubes devel builds).
>
> Anywhoo. I decided to
On 09/21/2017 12:47 PM, Franz wrote:
> None vm starts except dom0
>
> I am writing this email by a cell phone
>
> -Changing the kernel with qubes manager GUI does not work
you can use the GUI, just change the VM to a different kernel in VM
Settings > Advanced (and click okay), then change it
Hi all,
I am running Qubes OS 3.2 on a Lenovo Thinkpad E550. I have recently been
having problems with starting / restarting VMs. Whether starting from the GUI
or command line, VMs fail:
"ERROR: Cannot execute qrexec-daemon!"
In case it is relevant, following a recent update I had an error on
None vm starts except dom0
I am writing this email by a cell phone
-Changing the kernel with qubes manager GUI does not work
-the terminal line that worked last time runs without errors but does not
solve the problem:
For VM in 'qvm-ls --raw-list'; do qvm-prefs $VM kernel default; done
When I
On Thursday, 21 September 2017 07:23:01 UTC+1, Alex wrote:
> Replying to this thread to report that somebody DID ACTUALLY find an
> exploitable vulnerability in the latest IME 11+, and they will be
> sharing nothing less that this UNSIGNED CODE EXECUTION vuln at blackhat
> europe 2017.
>
>
Hi Unman,
Yes, I overwrote all entries while installing Ubuntu.
Thanks a lot for your hints, problem is finally resolved after hours of reading
:)
What I done
chroot /mnt/sysimage
cd boot
grub2-mkconfig
grub2-install /dev/sda
reboot
Old grub file was fine so I booted in now successfully.
On Wednesday, 20 September 2017 09:41:58 UTC+1, pels wrote:
> [1.617897] systemd[1]: Failed to mount tmpfs at /run: Permission denied
> [.[0;1;31m!!.[0m] Failed to mount API filesystems, freezing.
> [1.621206] systemd[1]: Freezing execution.
Looks like a tmpfs cannot be mounted at
I'd like to know where the Xen configurations are stored and how to manipulate
them, for example, to add net interfaces or exposing a console.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
Thanks for your answer.
I wrote that I'm trying to connect TO a Template Emergency Dracut shell FROM
Dom0, using 'xl console'.
--
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,
On Wednesday, September 20, 2017 at 2:54:31 PM UTC+2, cooloutac wrote:
> On Wednesday, September 20, 2017 at 4:41:58 AM UTC-4, pels wrote:
> > I'd like to activate SELINUX(enforcing) in VMs (f25 and f25-minimal), but
> > fails:
> >
> > [1.510532] audit: type=1404 audit(1505894636.317:2):
On Wed, Sep 20, 2017 at 04:15:21PM -0700, stas2...@gmail.com wrote:
>
> Guys, Thank you for your replies.
>
> Unman, Ubuntu is not important to me.
> Most important thing is to load Qubes again.
> I have tried grub2-install /dev/sda3 - but I am getting an error saying that
> it's unreliable and
On Wed, Sep 20, 2017 at 08:57:41PM -0400, 'Essax' via qubes-users wrote:
> To remove Whonix templates first remove all the appVMs based on those
> templates. In dom0 type :
>
> qvm-remove sys-whonix
> qvm-remove anon-whonix
>
> Then to remove the Whonix templates. In dom0 type :
>
> qvm-remove
20 matches
Mail list logo