Re: [qubes-users] Re: Cannot get installer to load, Help and advice welcomed (semi-noob here).

[cangent05]

Thank you, it worked. I strongly suggest Qubes staff add these two points on 
their website. Perhaps, the second one (enable VT-x etc.) is obvious to 
computer engineers, or even the first one (try legacy). However, not all of us 
are computer focused individuals. Once again, thank you for your helps.

On Tuesday, May 1, 2018 at 3:30:14 PM UTC+8, awokd wrote:
> On Mon, April 30, 2018 2:38 pm, c...@gmail.com wrote:
> > Tried Qubes 4.0 installation on two PCs: 1) Asus Aspire S13 laptop, Intel
> > i7-6500 CPU @ 2.50GHz 2.60 GHz, 8 GB RAM, 64-bit 2) Asus D620MT desktop,
> > Intel i7-6700 CPU @ 3.40GHz, 3.40 GHz, 16 GB RAM, 64-bit.
> > For the first one, installation never proceeded further than few seconds
> > (after few lines appeared on the screen, the screen was all black and the
> > CPU was running at high speed without any progress). Tried both USB and
> > CD drive.
> 
> Try legacy mode or if you have a secondary graphics adapter, disabling it.
> 
> > For the second one, after selecting the language on the installation
> > interface, it warned "unsupported hardware...Missing features:
> > HVM/VT-x..."
> 
> Make sure VT-x etc. are enabled in your UEFI config.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b3381d8e-9d8d-4be3-af37-966375d4c221%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes R4.0 advantange over R3.2 ?

[Sergio Matta]

Em domingo, 13 de maio de 2018 04:54:48 UTC-3, niepo...@gmail.com  escreveu:
> As i have internet connection problem on Qubes R4.0 that i' unable to resolve 
> i probably back to qubes R3.2.
> My question is Qubes R.4.0 significantly more secure over R3.2? 
> Is version R3.2 has known not resolved issues/vulnerabilities that at version 
> R4.0 are not present?
> My hardware has HVM but not IOMMU.

There are many advantages using 4. Look for the documentation. And it is a base 
for the new developments. 
I was using V4 without iommu (not suported by my old chipset). I choose change 
my motherboard. But until there, you can use PV vms, set the networking with 
commands ip link, ip addr, ip route in /rw/config/rc.local e activate it with 
sudo chmod +x /rw/config/rc.local. 

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d87090e3-b7f8-4556-9a1c-f0389743f852%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-usb: Device Attach Failed [No Reason Given]

[Jone]

On Sunday, May 13, 2018 at 3:38:03 PM UTC-4, awokd wrote:

> Are you using those quotes in the actual command? Try: qvm-usb attach test
> sys-usb:3-1

The error remains the same. [For anyone looking at this post in the future, the 
quotes did succeed with as expected with an AppVM based on the debian-9 
template.] 

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fb009ead-7263-4fec-9796-29b439e0b7f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-usb: Device Attach Failed [No Reason Given]

[awokd]

On Sun, May 13, 2018 7:02 pm, Jone wrote:
> Hello,
>
> Command used: qvm-usb attach "test" "sys-usb:3-1"
> Error: "Device attach failed:"

Are you using those quotes in the actual command? Try: qvm-usb attach test
sys-usb:3-1


-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/db4e6bf55895d1d83742d0d2fd1e8deb%40elude.in.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Ubuntu Xenial Template Build Issues

[wilsondon07]

For anyone with this issue in the future, removing those lines from the make 
file allowed for a xenial template to be created.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/60c7c85b-df25-4f9d-9135-340006338fd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qvm-usb: Device Attach Failed [No Reason Given]

[Jone]

Hello,

Command used: qvm-usb attach "test" "sys-usb:3-1"
Error: "Device attach failed:" 

[Error was just what was in quotes]

"test" is an app-vm made with a xenial+Desktop template in R4.0.
I added the qubes-r4.list to /etc/apt/sources.list.d and installed 
qubes-usb-proxy.

I was successfully able to attach the same usb device to a debian-9 template 
AppVM, it worked appropriately, and succeeded. 

Does anyone know what this error could be or mean? Additionally, what is the 
way to solve this?

Thank you for your time.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0adc5000-6300-40a1-87af-b3021c6266bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] sys-firewall domain start failed

['para-vak' via qubes-users]

Indeed, yet I rarely input anything without 'sudo' behind it... anyway... 
Disregard! A fresh install has not reproduced the error! It seems that ensuring 
proper formatting of the disk is paramount! GParted + a manual partitioning in 
Qubes setup to be sure.

On May 13, 2018 12:24 PM, awokd  wrote:

> On Sun, May 13, 2018 3:52 pm, 'para-vak' via qubes-users wrote:
> 
> > Initial install with default template settings:
> > 
> > Upon concluding final configuration after 1st reboot, just after all VMs
> > 
> > have been created for the first time, right before first booting into the
> > 
> > system:
> > 
> > ['/usr/bin/qvm-start: 'sys-firewall'] failed: stdout:""
> > 
> > stderr:"start failed: internal error: libxenlight failed to
> > 
> > create new domain 'sys-firewall', see
> > 
> > /var/log/libvert/libxl/libxl-driver.log
> > 
> > ISO file integrity has been verified. Media tests during a multiple
> > 
> > re-install attempts with different media have passed, and yet the error is
> > 
> > reproduced.
> > 
> > Following suggestion in error message, reveals log is nonexistent.
> 
> That is odd, ordinarily it would be sys-net or sys-usb with issues like
> 
> that. I think you might have to be su to see that log file. If you qvm-ls,
> 
> what is running? If sys-net fails to start, that might cause sys-firewall
> 
> to also fail. Also, do a qubes-hcl-report and check the last 5 lines about
> 
> HVM, IOMMU, etc.


-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/EpCLTH1is6Ss2Syx86-rS-4iww7J4j9wfZFFZAZ8nGaWEYKq27QSTnvds6TlAir-7_H5sLHzFwV-MtDjqczrjdHFP7RfxraytpWVJH2BnDY%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] BACKUP PROBLEM

[higginsonjim2]

Thanks for comments. To clarify  - i’m only using qubes4 vm’s and templates. In 
ideal world, i ‘d use clonezilla say to clone everything and copy the 
clonezilla image back if i ever thought there was a problem with active system. 
This does not seem possible with qubes. (This process is simple and works well 
with debian, ubuntu etc)
Instead I’ve copied all my qubes3.2 data offline and was intending to use 
filezilla to bring it all back -once i was confident of stable qubes4 setup.
I think i’m further away from ever with that. Just done the umpteenth install 
of qubes4 and now can’t get my test vm’s to recognise software eg filezilla, 
libreoffice writer that i’ ve added to fedora 26. I done endless resume, 
stop/starts and turn pc off/on - but nothing happening. Was intending to 
generate a fedora-26 template backup again, including a few test vm’s  - then 
transfer to another pc , then do a fresh install on main pc, zap the new 
fedora-26 and vm’s and then try and copy the backup file to main pc and restore.
 Qubes is a great idea - for 12 months or so i’ve done almost all my internet 
stuff on dispvm’s and kept a good discipline wrt untusted/ personal vm’s etc. 
My old pc couldn’t handle qubes4 - so ive invested in new kit so i could start 
with qubes4.

I can’t spend any more time with this so it’s back to debian for me.
I’ll have another look at qubes in a few months when hopefully it’s more stable.

Thanks again for comments.


-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/274633a8-90c4-49ca-9193-9aabede65d68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] sys-usb freezes after suspend

[awokd]

On Sun, May 13, 2018 4:32 pm, maur...@disroot.org wrote:
> Unfortunately that only describes the process for the sys-net.
> According to the issue described in the github the blacklist of the module
> xhci-pci was already
> merged into the stable repo r4.0 under the qubes-core-dom0-4.0.11-1.fc25.
> So I guess that will not work either.

Thanks, missed that!

> Are there any other suggestions?

Not from here, I'm afraid...


-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ad428194f3243973bffac1894816015e%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] sys-usb freezes after suspend

[maurice]

Unfortunately that only describes the process for the sys-net.
According to the issue described in the github the blacklist of the module 
xhci-pci was already
merged into the stable repo r4.0 under the qubes-core-dom0-4.0.11-1.fc25.
So I guess that will not work either.

Are there any other suggestions?

Thank you

May 12, 2018 4:05 PM, "awokd"  wrote:

> On Fri, May 11, 2018 7:12 pm, maur...@disroot.org wrote:
> 
>> Hi folks!
>> 
>> Whenever my laptop resumes after have being suspended, the sys-usb is
>> stalled and all USB devices attached fail to work. They are all
>> disconnected.
>> Whenever that happens the only way to have the sys-usb working again is to
>> kill it.
>> Strangely this only affects the sys-usb and not the sys-net, which is
>> working fine after resume.
>> The issue that describes this problem -
>> https://github.com/QubesOS/qubes-issues/issues/3142
>> (https://github.com/QubesOS/qubes-issues/issues/3142) - is closed but this
>> problem persists.
>> 
>> Does anyone knows how this can be solved?
> 
> Try following the procedure here for your USB controller driver:
> https://www.qubes-os.org/doc/wireless-troubleshooting

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d84a44cb373b89cf44aedec8b819744f%40disroot.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] 4 monitors, 3 output types, 2 graphics chips and not getting to show up on all 4 monitors

[awokd]

On Sat, May 12, 2018 11:44 pm, Stumpy wrote:

> I have now tried installing Qbes v4 onto a usb flash drive. The xfce
> display window was the least buggy compared with most of the distros,
> but it seems Qubes 4 doesn't like my graphics card... or something. The
> two Dells connected to the exernal graphics card are showing that
> multiucolored static no matter what configuation I try (ie rotating,
> mirror [which worked well for many of the distros], primary display
> etc).

What if you try Qubes with only the AMD adapter? It usually works well
with the older ones (pre-Vega). Is it only when you use both adapters at
the same time? I'm wondering if some distros default to a lower colour
depth/refresh rate.

> So I am left with the possibility that its the graphics card but as some
> of the other distros worked I was hoping that was the wrong
> assumption... or maybe I am thinking about it wrong, maybe its xen that
> doesn't like the gfx card? (which is the only thing I can think of that
> *all* the distros did not have).
>
> I am desprate to get a multi display option working, so am willing to
> get another gfx card but as I can't keep doing that I need to be sure
> next time.

Makes sense.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5b90431c2565ab0f552431bf51dc%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] sys-firewall domain start failed

[awokd]

On Sun, May 13, 2018 3:52 pm, 'para-vak' via qubes-users wrote:
> Initial install with default template settings:
>
> Upon concluding final configuration after 1st reboot, just after all VMs
> have been created for the first time, right before first booting into the
> system:
>
> ['/usr/bin/qvm-start: 'sys-firewall'] failed: stdout:""
> stderr:"start failed: internal error: libxenlight failed to
> create new domain 'sys-firewall', see
> /var/log/libvert/libxl/libxl-driver.log
>
> ISO file integrity has been verified. Media tests during a multiple
> re-install attempts with different media have passed, and yet the error is
> reproduced.
>
> Following suggestion in error message, reveals log is nonexistent.

That is odd, ordinarily it would be sys-net or sys-usb with issues like
that. I think you might have to be su to see that log file. If you qvm-ls,
what is running? If sys-net fails to start, that might cause sys-firewall
to also fail. Also, do a qubes-hcl-report and check the last 5 lines about
HVM, IOMMU, etc.



-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bad97d8553fc5d589eecf64a49094dd1%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] What is the best recommended way to setup a bulletproof vpn on Qubes 4 ?

[awokd]

On Sun, May 13, 2018 3:34 pm, jhsdxs...@gmail.com wrote:
> I'm new to Qubes and would like to have the traffic for all my Virtual
> Machines go through a VPN. I am really not sure how to do this. I've tried
> following the official Qubes Documentation page about VPNs but I haven't
> had any luck. I'm on Qubes 4.0. Thanks

You can try tasket's updated documentation at
https://github.com/tasket/qubes-doc/blob/a19ddb67ba3820733986978676bcfd33e4743867/configuration/vpn.md.


-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bcbcd173e9c2fdd22680907282e2a00e%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] BACKUP PROBLEM

[awokd]

On Sun, May 13, 2018 1:58 pm, higginsonj...@gmail.com wrote:
>
> Just posted a comment on earlier BACKUP problem where message appeared
>
> "Backup header retrieval failed (exit code 2)" after qvm-backup restore.
>
>
> Tried a simpler backup this time - just fedora-26 template and a small
> personal VM.
>
> Process seemed to go OK - but following backup - was left with fedora-26
> template and fedora-261 template. (Think others have seen this also)

You mean on restore, right? I saw that on mine too, it wanted to create
some 0 byte DispVMs so I didn't include those on the restore. Note too
that you should only be restoring your AppVMs and StandaloneVMs and using
the templates that come with 4.0 instead. See
https://www.qubes-os.org/doc/upgrade-to-r4.0/#restore-from-your-backup:

"We recommend that you restore only your TemplateBasedVMs and
StandaloneVMs from R3.2. Using TemplateVMs and SystemVMs from R3.2 is not
fully supported (see #3514). Instead, we recommend using the TemplateVMs
that were created specifically for R4.0"

> Trying to get rid of fedora-261 template. Normal process won't allow it -
> so tried "REMOVE VM's MANUALLY" approach as per docs.
> First 3 instructions seem OK - but final one achieves nothing since there
> is no content in the "applications-merged" folder.

Looks like this doc is for R3.2 only and I missed it! I submitted an edit.
If you have nothing else on your R4.0 installation, it might be faster to
just reinstall it.

> Hence can't remove FEDORA-261 from QUBES MANAGER.
>
> Note ALSO - the FEDORA-261 template created does not include any
> APPLICATIONS from the FEDORA-26 template I stared with.
>
> SPECIFICALLY - it contains none at all!
>
> This seems similar to problems I encountered before with QUBES 4.
>
> 1) With QUBES3.2 - I used DEBIAN template - but have had to give up on
> that as I can't get any applications to show within DEBIAN template and
> have no means to add any.  eg no TERMINAL
>
> 2) WIth QUBES 3.2 I also used a STANDALONE template for development work.
>
> Again - even if it's based on FEDORA-26 template - I get no APPLICATIONS
> available to me and NO terminal.
>
> Basically I have given up on STANDALONE VM also.
>
>
> I can install QUBES4 quickly and get what appears to be a workable system
> - but am loathe to commit to it as every step I take seems to offer more
> problems.
> QUBES3.2 was simple and straightforward  - and just seemed to work.
> Am basically trying to get everything setup on new computer but after many
> many days of trying (2 or 3 weeks of effort)- I cant achieve a stable
> state
>
> No Debian
> No Standalone
> No BACKUP working consistently
> Duplicated template - can't get rid from menu
> QUBES manager clunky
> Struggling to get rid of DISPOSABLE VM template(based on Fedora-26 when I
> updated main template to fedora-27.
> DispVM - quite slow compared to QUBES3.2
>
> HAS ANYONE PREPARED AND USED BACKUPS SUCCESSFULLY ?
>
> --
> 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 email to qubes-users@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/55328bb9-688e-4186-ab78-8d160c22e27e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e931199dc42b3467df788af401806d5d%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes R4.0 - no internet working in appVM

[awokd]

On Sat, May 12, 2018 7:08 pm, niepowie...@gmail.com wrote:
> netVM has ok ping to google.com
> firewallVM has no pings
> appVM has also no pings
>
> Maybe it's worth to mention: update template VM was done with success
> (which is a bit odd as update actually was done with success as firewallVM
> has no pings).

Are you using the default templates and AppVMs, or ones you've restored?
Try doing a reinstall and testing with the default ones only.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/21851366fbaaf8c01d61f794c015f348%40elude.in.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Why so many outgoing IP?

[awokd]

On Sat, May 12, 2018 11:35 pm, mk2mix via qubes-users wrote:
> sorry for the translations that are not very good.

No problem!

> I meant that I had not seen the possibility of "minimal-fedora", so thank
> you.
> it may be a good track.
> I already tried "systemctl ntp disable"
> it does not seem to prevent.

On a Debian template based sys-net at least, it would be "systemctl
disable systemd-timesyncd". Maybe it would be a good idea to do like that
other poster suggested and work on figuring out where communications are
coming from in just one OS? You mentioned pfsense, but wireshark might be
more useful. You could set it up in Qubes like:

Debian/Fedora HVM -> Proxy VM w/Wireshark (haven't tested) -> sys-firewall

Then you can apply what you learned from that to Qubes.


-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a3d9dc6cb63e5b05db4d7c9e94e05bc1%40elude.in.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] sys-firewall domain start failed

['para-vak' via qubes-users]

Initial install with default template settings:

Upon concluding final configuration after 1st reboot, just after all VMs have 
been created for the first time, right before first booting into the system:

['/usr/bin/qvm-start: 'sys-firewall'] failed: stdout:""
stderr:"start failed: internal error: libxenlight failed to
create new domain 'sys-firewall', see /var/log/libvert/libxl/libxl-driver.log

ISO file integrity has been verified. Media tests during a multiple re-install 
attempts with different media have passed, and yet the error is reproduced.

Following suggestion in error message, reveals log is nonexistent.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/h6lVKjxpGck5JfEt7jxpbQaBX0PxMMLMQspuMQaL0tnjscx4eAU4RZJVYUBPgAO9W7pAUgOmnj1UxcXre_K-nOoFGRg1eFrTnMjS4ZW7ZBA%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] What is the best recommended way to setup a bulletproof vpn on Qubes 4 ?

[jhsdxsddw]

I'm new to Qubes and would like to have the traffic for all my Virtual Machines 
go through a VPN. I am really not sure how to do this. I've tried following the 
official Qubes Documentation page about VPNs but I haven't had any luck. I'm on 
Qubes 4.0. Thanks

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e563c55a-b0be-4ed2-ab7e-7a717aa1c3ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] <>

[Peter Owen]

--
Good Day,
Hope you are doing great Today.I have a proposed business deal that will 
benefit both parties. This is legitimate and legal and your personality 
will not be compromised.Reply to me only if you are interested for 
details.


Sincerely,

Peter OWEN

--
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9413c4cef72f9f8be68e907f99e4c89a%40exline.kz.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] BACKUP PROBLEM

[higginsonjim2]

Just posted a comment on earlier BACKUP problem where message appeared

"Backup header retrieval failed (exit code 2)" after qvm-backup restore.


Tried a simpler backup this time - just fedora-26 template and a small personal 
VM.

Process seemed to go OK - but following backup - was left with fedora-26 
template and fedora-261 template. (Think others have seen this also)

Trying to get rid of fedora-261 template. Normal process won't allow it - so 
tried "REMOVE VM's MANUALLY" approach as per docs.
First 3 instructions seem OK - but final one achieves nothing since there is no 
content in the "applications-merged" folder.

Hence can't remove FEDORA-261 from QUBES MANAGER.

Note ALSO - the FEDORA-261 template created does not include any APPLICATIONS 
from the FEDORA-26 template I stared with.

SPECIFICALLY - it contains none at all!

This seems similar to problems I encountered before with QUBES 4.

1) With QUBES3.2 - I used DEBIAN template - but have had to give up on that as 
I can't get any applications to show within DEBIAN template and have no means 
to add any.  eg no TERMINAL

2) WIth QUBES 3.2 I also used a STANDALONE template for development work.

Again - even if it's based on FEDORA-26 template - I get no APPLICATIONS 
available to me and NO terminal.

Basically I have given up on STANDALONE VM also.


I can install QUBES4 quickly and get what appears to be a workable system - but 
am loathe to commit to it as every step I take seems to offer more problems.
QUBES3.2 was simple and straightforward  - and just seemed to work.
Am basically trying to get everything setup on new computer but after many many 
days of trying (2 or 3 weeks of effort)- I cant achieve a stable state 

No Debian
No Standalone
No BACKUP working consistently
Duplicated template - can't get rid from menu
QUBES manager clunky
Struggling to get rid of DISPOSABLE VM template(based on Fedora-26 when I 
updated main template to fedora-27.
DispVM - quite slow compared to QUBES3.2

HAS ANYONE PREPARED AND USED BACKUPS SUCCESSFULLY ? 

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/55328bb9-688e-4186-ab78-8d160c22e27e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Installation freezes on SSD

[alexw8913]

I used the default templates qubes assigned.  I have tryed about 10 different 
times.

 I took cooloutac's advice except for I kept the default sys-net vm checkbox 
and unchecked the sys-usb template and its working now.  Thanks for the help.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7b188ae3-e019-4db6-864f-7c8336c8a231%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Backup header retrieval failed (exit code 2) after qvm-backup restore

[higginsonjim2]

Am getting same problem - did you resolve this?


Also when attempting to enter the backup image folder (within the backup 
process) the system won't just take the image folder created - when I click OK 
it opens up the sub files and wants me to enter something there. Clearly I can 
delete the file bit within the "location of backup" field - but then I get the 
exit code message. 

Is this part of the problem 

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/44812c83-fe0f-4cca-892f-fe8c2c62ed08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Insert/Inject keyboard hits to a Qube from Dom0

[cr33dc0d3r]

Am Samstag, 12. Mai 2018 00:00:42 UTC+2 schrieb [ 799 ]:
> Hello Jonny,
> 
> 
> 
>   schrieb am Fr., 11. Mai 2018, 15:18:
> Am Freitag, 11. Mai 2018 13:52:23 UTC+2 schrieb cr33d...@gmail.com:
> 
> > Hey Everyone!, 
> 
> > 
> 
> > currently working on several automation processes using bash scripts 
> > executed in dom0 to do certain actions. 
> 
> > 
> 
> > To execute an specific command, normally we are using s.th. like:
> 
> > 
> 
> > qvm-run  [VMname] 
> 
> > 
> 
> > E.g.: qvm-run personal "cp /home/user/Desktop/test.txt 
> > /home/user/Documents/test.txt
> 
> > 
> 
> > Now my situation:
> 
> > 
> 
> > When connecting to an ftp-server via: ftp , i had to enter an 
> > username and password. 
> 
> > 
> 
> > How to execute this using qvm-run? I suggest to write a little script like:
> 
> > 
> 
> > #!/bin/bash
> 
> > 
> 
> > qvm-run personal "ftp " | qvm-run personal "user /n" |qvm-run 
> > personal "pw \n" 
> 
> > 
> 
> > Unfortunately this one does not work since last two aren't commands. 
> > However, is it possible to insert such keyboard entries in an VM's console 
> > to get this work?
> 
> > 
> 
> > Thanks,
> 
> > Jonny
> 
> 
> 
> Hey All, an alternative is to write an executable bash script in the qube 
> that to the ftp stuff, bind it to PATH and execute it with qvm-run. 
> 
> 
> 
> But, if there is an alternative, not to use a script located on that vm and 
> do all remotely, i would be pleased to hear your ideas :) 
> 
> 
> 
> if possible I would try to look for a way to replace ftp by something that is 
> more secure like sftp/scp.
> Then you can drop the login/password part and use certificates to 
> authenticate.
> If you really want to use login/password I would use split-gpg so that you 
> can keep the password on an offline "vault-vm" and the password will be 
> decrypted and used in the AppVM.
> 
> 
> Question if you keep using ftp
> Would it be ok, if you enter login and password in dom0 ?
> Are you always connecting to the same ftp server from the AppVM?
> And are you always executing the same ftp command ?
> Or do you need a more flexible approach like:
> 
> 
> don0script 
> 
> 
> If you are more specific what you want to accomplish I can write you a draft.
> 
> 
> Regards
> 
> 
> [799]

Hey [799],

what i try to accomplish is a process executed on dom0 that downloads an data 
package from the server onto AppVM1 - then forward it over to another AppVM - 
then execute (read) it. Currently i have scripted the transfer between dom1 and 
2 and the download from the server with a script inside dom1. However, i want 
to try to initiate & control the download from dom0 that the script does not 
have to be placed in the AppVM.

- it would be ok to enter login data from dom0 (that login information would be 
stored on dom0)
- in that case i will always connect to the same ftp server
- i will always execute the same ftp command differ by data-name:
  - like: ftp get /path/to/fileX.txt
- would not need to be that flexible - here what i have got for dom1:
#--#
#!/bin/bash

HOST='x.x.x.x'
USER='AppVM1'
PASSWD=''

FILE=$1
ftp -n -v $HOST 

[qubes-users] Qubes R4.0 advantange over R3.2 ?

[niepowiem48]

As i have internet connection problem on Qubes R4.0 that i' unable to resolve i 
probably back to qubes R3.2.
My question is Qubes R.4.0 significantly more secure over R3.2? 
Is version R3.2 has known not resolved issues/vulnerabilities that at version 
R4.0 are not present?
My hardware has HVM but not IOMMU.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1547a60f-d76a-4ebf-b817-66c001bee411%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.