[qubes-users] ssh-agent, gnome-keyring, ed25519 keys

2016-08-03 Thread pixel fairy
out of the box, fedora23 template, ssh-agent works fine with rsa keys, but not 
ed25519. 

could not add identity "/home/user/.ssh/id_ed25519": communication with agent 
failed

running "ssh-agent bash" and then adding both keys works fine. is there a clean 
way to disable this keyring? its not like we need it. 

-- 
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/c63ec4be-0dee-4eb5-ba18-4c3e992ff938%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Windows tools in 3.2 (was: Re: [qubes-users] Re: Battery Life Qubes 3.2 rc2)

2016-08-03 Thread Peter M
On Wednesday, August 3, 2016 at 1:26:37 AM UTC-6, Marek Marczykowski-Górecki 
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Tue, Aug 02, 2016 at 07:08:25PM -0700, Peter M wrote:
> > One point to note for those running Windows 7 HVM is that Qubes Windows 
> > Tools 3.2.0.2 seems to be more stable than 3.0.4.1
> > I had issues with the older windows tools in 3.1 but the problems got worse 
> > in 3.2. The VM would randomly crash. Since updating windows tools it has 
> > not crashed yet.
> 
> Do you means you have successfully upgraded tools in existing Windows
> VM? Or maybe you did fresh install?
> 
> In any case, have you observed any difference in performance of Windows
> VM? Especially, if did fresh install, what was Windows installation
> time?
> 
> - -- 
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?


I successfully upgraded Windows Tools in existing Windows VM. Note that it took 
4 tries for me to successfully complete it without crashing. I cloned the VM as 
backup before doing anything. 

I have not noticed any significant performance increases, only stability 
improvement. For me though this is the most critical. I have not had a crash 
since the upgrade.

-- 
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/dd90dfc2-cae1-4447-aaf9-8ffe4541bff8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: black screen after installation v3.1 on dell XPS 15

2016-08-03 Thread admixior
I have similar issue on XPS.
The graphics should work (for me) if you (have and) run older kernel in option.
But you can press for example "PageUp" key and enter password.
(For  me it works)

Regards

-- 
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/4d2b2a36-eed1-4b2d-815e-95919c6f21a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] black screen after installation v3.1 on dell XPS 15

2016-08-03 Thread j7wtah2m6dj8
Hi,

After successful installation, first boot of Qubes.
Boot screen and after that grub menu text is visible.
Then blinking cursor, and then a black screen.
Something wrong with X?

Or something needs change in BIOS?

thnx!

-- 
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/dfa69a18-36b9-4b5d-98d7-1ae83dfd7e88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: PS2 Mouse with adaptor

2016-08-03 Thread raahelps
On Tuesday, August 2, 2016 at 8:57:52 AM UTC-4, Herbies wrote:
> Hi,
> 
> Qubes advice to use ps2 mouse and keyboard but is impossible to find one
> in local shop.
> 
> I have bought some usb/ps2 adapter to connet usb keyboard and mouse to
> my ps2 port. My keyboard is working well, but I have tried several model
> of mouse unsuccessfully.
> 
> Do you know the reason because my usb mouses fail to function while
> connected to the adapter?
> 
> Any other suggestion?
> 
> Thanks you

imo,  it is not as important to have pci mouse as it is for keyboard.   I just 
use a usb to pci adapter for keyboard.  and Use a usb mouse with the qubes 
mouse proxy from usbvm.  For extra security set lockscreen.

-- 
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/433a171d-a602-4599-8cb7-7662ff157709%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] If Ubuntu's license is keeping us from having a ready-made template...

2016-08-03 Thread raahelps
On Wednesday, August 3, 2016 at 8:00:22 AM UTC-4, Achim Patzner wrote:
> Am 03.08.2016 um 13:08 schrieb Marek Marczykowski-Górecki:
> > On Wed, Aug 03, 2016 at 12:42:25PM +0200, Achim Patzner wrote:
> > > ... what about preparing a Mint template that can be distributed?
> >
> > That's good question. I guess only that no one added support for it in
> > builder-debian plugin (or separate one).
> 
> Hm. Who is that No One I keep hearing so much about lately and what does
> it take to convince him to spend some time on it? 8-)
> 
> 
> Achim

probably not enough people care to use ubuntu.  Why is it that you want an 
ubuntu 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/f86f76c1-4ab6-4b49-81d7-0bf3e63cabe2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Attaching a webcam from sys-usb to other appvm

2016-08-03 Thread 46h6sk+9aybfqrmo0zwg via qubes-users
Yes, I'm using Qubes 3.2RC2






Sent using GuerrillaMail.com
Block or report abuse: 
https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D



-- 
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/68d7dc9914b7d1945c07604877e2a6805767%40guerrillamail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Attaching a webcam from sys-usb to other appvm

2016-08-03 Thread Franz
On Wed, Aug 3, 2016 at 3:35 PM, 46h6sk+9aybfqrmo0zwg via qubes-users <
qubes-users@googlegroups.com> wrote:

> Thank you for the reply. I tried to follow the instructions on the
> documentation (as illustrated for the conference AppVM) however that does
> not work. I get a message stating - ERROR: qubes-usb-proxy not installed in
> the VM - which is not true, I've installed the package and the message is
> still displayed.
>
> What I'm doing wrong?
>
>
>
May you confirm you are using Qubes release 3.2?

>
>
>
> 
> Sent using GuerrillaMail.com
> Block or report abuse:
> https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D
>
>
>
> --
> 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/137f3a431aab9bf9f71ab3d8af88094fea39%40guerrillamail.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/CAPzH-qB%2BFhGREaUPt0XnCf5xovhKNijseTZLhoedVh0pfkP%3DCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Attaching a webcam from sys-usb to other appvm

2016-08-03 Thread 46h6sk+9aybfqrmo0zwg via qubes-users
Thank you for the reply. I tried to follow the instructions on the 
documentation (as illustrated for the conference AppVM) however that does not 
work. I get a message stating - ERROR: qubes-usb-proxy not installed in the VM 
- which is not true, I've installed the package and the message is still 
displayed.

What I'm doing wrong?






Sent using GuerrillaMail.com
Block or report abuse: 
https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D



-- 
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/137f3a431aab9bf9f71ab3d8af88094fea39%40guerrillamail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Configuring OpenDNS in Qubes

2016-08-03 Thread marc
> eth0 is an uplink to sys-net. And /etc/resolv.conf there indeed is
> generated, so manual changes will be lost. There is a way to avoid this
> using /etc/qubes/protected-files.d/, but I think it isn't the way to go.
> Better adjust NetworkManager settings in sys-net, using standard
> connection editor GUI. The DNS servers in any other VM are in the end
> pointing to what you have in sys-net(*) (using DNAT redirections). 
> 
> (*) unless you use Tor/Whonix - in which case those are redirected to
> tor process.

Thanks for your answer.

Does it mean that all VM have to share the same DNS settings (except 
Tor/Whonix)? What I was trying to do is routing only one of them through 
OpenDNS, while keeping the rest with my ISP DNS server (and I would like to 
avoid an HVM just for that).

I see I can create a new "NetVM" but I'm not sure if it is full supported. If I 
create a new one, is the GUI adapted so that I can configure both (sys-net and 
my custom one)? I prefer to ask before trying it and risking leaving something 
in an inconsistent state.

-- 
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/e7b7ccac-708d-4c60-8dc6-1493fcf21d15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Android Emulator

2016-08-03 Thread Torsten Grote
On 08/03/2016 11:37 AM, Alex wrote:
> It says that to me too, but using an ARM image does work (this message
> is just a warning)

Oh thanks! I didn't try using an ARM image. If you ever find out how to
run an x86 image with Qubes, please let me know.

> once disconnected from usbVM and attached to the work AppVM,
> it senses the usb reset and does not attach
> again until the cable is unplugged and connected again.

You might be able to use ADB via TCP. I explained how here:


https://github.com/QubesOS/qubes-issues/issues/2202#issuecomment-235937670

Kind Regards,
Torsten

-- 
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/16c8e579-3ccb-0454-77de-bcdc6efcfbbb%40grobox.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] Re: Is a legacy BIOS preferable to UEFI for a secure system?

2016-08-03 Thread grzegorz . chodzicki
W dniu środa, 3 sierpnia 2016 06:15:38 UTC+2 użytkownik Manuel Amador (Rudd-O) 
napisał:
> On 08/02/2016 06:10 PM, grzegorz.chodzi...@gmail.com wrote:
> >
> > Easier troubleshooting/updating/diagnostics. Modern UEFI installed on e.g 
> > gaming motherboards can update itself over Ethernet connection, reinstall 
> > itself from scratch and sometimes contains a built-in mini-linux. If you do 
> > not need such bonuses then legacy BIOS will do just fine.
> >
> 
> How do you / how can I identify these malevolent mobos?
> 
> 
> -- 
> Rudd-O
> http://rudd-o.com/

Pretty much any motherboard made by MSI, Asus, Asrock or Gigabyte, especially 
the ones marketed for gamers. Workstation/server motherboards should be fine 
though. iPMI is less of an issue on ws/server mobos since it usually runs only 
over its own separate ethernet controller.
Funny story, few weeks ago I helped my friend put together a gaming PC. The 
motherboard didn't even POST correctly until we connected the ethernet cable so 
it could update itself. Utterly terrifying.

-- 
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/82dec981-224d-421f-845c-7985950fee33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Configuring OpenDNS in Qubes

2016-08-03 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Aug 03, 2016 at 06:50:21AM -0700, m...@lamarciana.com wrote:
> > Are you using NetworkManager in that ProxyVM?
> 
> I assigned "network-manager" service through "Qubes VM Manager" to my debian 
> standalone ProxyVM, but I see this disappears once I start and shutdown the 
> machine... I tried again to be sure and I can reproduce the issue. I will 
> inspect it further and open a Qubes issue if needed.
> 
> But, anyway, I changed my ProxyVM to use fedora template (still standalone): 
> Then, "network-manager" survives after reboot, but not the content in 
> "/etc/resolv.conf"... But, in fedora template this file has an interesting 
> hint:
> 
> # Generated by NetworkManager
> 
> I think this confirms my fears that /etc/resolv.conf should not be edited by 
> hand...
> 
> I tried then to edit file 
> /etc/NetworkManager/system-connections/qubes-uplink-eth0 and added OpenDNS 
> IP's in "[ipv4]" section but changes are lost after reboot (I'm not using 
> ethernet cable but wifi, but there is no other file. Furthermore, "ifconfig" 
> only shows loop and eth0, but I suppose there is some kind of delegation to 
> sys-net for that).

eth0 is an uplink to sys-net. And /etc/resolv.conf there indeed is
generated, so manual changes will be lost. There is a way to avoid this
using /etc/qubes/protected-files.d/, but I think it isn't the way to go.
Better adjust NetworkManager settings in sys-net, using standard
connection editor GUI. The DNS servers in any other VM are in the end
pointing to what you have in sys-net(*) (using DNAT redirections). 

(*) unless you use Tor/Whonix - in which case those are redirected to
tor process.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXofgJAAoJENuP0xzK19csN7cH/A1gNpFZfoV1Ta7KolWAVCjF
wJuEpj1reXjD/+fc5aO7jvlJCUDWgMIuGPbqCdE0QFEOjbUS/KdyJIONh2+AGnjf
6CrIflZI4ii0lOHglslVaRpK0WqbfonlPoTb6Swo0FmDJh6yI26tc6xdn0zjRU6Y
B0ZVfUCDVow55Ta8Nm+XLtB1HInS0yx3WKOXff5uVvPJVbDVzsq/SncOmNiQjdU3
SmEwJoHNFel3LpUR0l3CHvSm3Bls4NDiWnmOSTn7X6wSXnqOEGWaeB8psy9VI+8W
jVDLlX9+7Jca5zSexQTYAjwDy9x73SfzsXQQnRkAV/iNO1ZAK+pj3p5qdqZsPYg=
=VOop
-END PGP SIGNATURE-

-- 
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/20160803135624.GO32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Configuring OpenDNS in Qubes

2016-08-03 Thread marc
> Are you using NetworkManager in that ProxyVM?

I assigned "network-manager" service through "Qubes VM Manager" to my debian 
standalone ProxyVM, but I see this disappears once I start and shutdown the 
machine... I tried again to be sure and I can reproduce the issue. I will 
inspect it further and open a Qubes issue if needed.

But, anyway, I changed my ProxyVM to use fedora template (still standalone): 
Then, "network-manager" survives after reboot, but not the content in 
"/etc/resolv.conf"... But, in fedora template this file has an interesting hint:

# Generated by NetworkManager

I think this confirms my fears that /etc/resolv.conf should not be edited by 
hand...

I tried then to edit file 
/etc/NetworkManager/system-connections/qubes-uplink-eth0 and added OpenDNS IP's 
in "[ipv4]" section but changes are lost after reboot (I'm not using ethernet 
cable but wifi, but there is no other file. Furthermore, "ifconfig" only shows 
loop and eth0, but I suppose there is some kind of delegation to sys-net for 
that).

-- 
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/f8c7338b-90a9-484f-8d0f-1153aa04b73e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Making archlinux template: on make autoreconf not found but it is installed

2016-08-03 Thread Facundo Curti
2016-08-03 12:11 GMT+00:00 Facundo Curti :

> El miércoles, 3 de agosto de 2016, 7:49:33 (UTC), donoban  escribió:
> > On 08/03/2016 07:23 AM, Facundo Curti wrote:
> > > El martes, 2 de agosto de 2016, 12:25:38 (UTC), Facundo Curti
> escribió:
> > >> Hi there. Someone can help me?
> > >> I'm trying to make an archlinux template on qubes 3.2. But i'm having
> troubles to compile.
> > >>
> > >> When I do:
> > >> $ make vmm-xen-vm
> > >>
> > >> I get:
> > >> /home/user/qubes-src/vmm-xen/PKGBUILD: line 49: autoreconf: command
> not found
> > >>
> > >> But autoreconf is already installed:
> > >> $ whereis autoreconf
> > >> autoreconf: /usr/bin/autoreconf /usr/share/man/man1/autoreconf.1.gz
> > >>
> > >> Here is the complete output:
> > >>
> > >> [user@development qubes-builder]$ make vmm-xen-vm
> > >> Currently installed dependencies:
> > >> git-2.5.5-1.fc23.x86_64
> > >> rpmdevtools-8.9-1.fc23.noarch
> > >> rpm-build-4.13.0-0.rc1.13.fc23.x86_64
> > >> createrepo-0.10.3-3.fc21.noarch
> > >> debootstrap-1.0.81-1.fc23.noarch
> > >> dpkg-dev-1.17.25-6.fc23.noarch
> > >> python-sh-1.11-1.fc23.noarch
> > >> dialog-1.3-4.20160424.fc23.x86_64
> > >> --> Archlinux dist-prepare-chroot (makefile):
> > >>   --> Checking mounting of dev/proc/sys on build chroot...
> > >>   --> Synchronize resolv.conf, in case it changed since last run...
> > >> -> Building vmm-xen (archlinux) for archlinux vm (logfile:
> build-logs/vmm-xen-vm-archlinux.log)
> > >> --> build failed!
> > >> ==> Retrieving sources...
> > >>   -> Found xen-4.6.1.tar.gz
> > >>   -> Found series-vm.conf
> > >>   -> Found apply-patches
> > >> ==> WARNING: Skipping all source file integrity checks.
> > >> ==> Extracting sources...
> > >>   -> Extracting xen-4.6.1.tar.gz with bsdtar
> > >> bsdtar: Failed to set default locale
> > >> ==> Starting build()...
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/qemu-tls-1.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/qemu-tls-2.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.qubes/xen-shared-loop-losetup.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.qubes/xen-no-downloads.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.qubes/xen-hotplug-external-store.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.qubes/xen-tools-qubes-vm.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.qubes/vm-0001-hotplug-do-not-attempt-to-remove-containing-xenstore.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/libxc-fix-xc_gntshr_munmap-semantic.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/libvchan-Fix-cleanup-when-xc_gntshr_open-failed.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/0101-libvchan-create-xenstore-entries-in-one-transaction.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/0001-configure-Fix-when-no-libsystemd-compat-lib-are-avai.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/0001-libxc-prefer-using-privcmd-character-device.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/0001-tools-hotplug-Add-native-systemd-xendriverdomain.ser.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.security/xsa155-xen-0003-libvchan-Read-prod-cons-only-once.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.libxl/0001-libxl-trigger-attach-events-for-devices-attached-bef.patch
> > >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
> ./patches.misc/0001-systemd-use-standard-dependencies-for-xendriverdomai.patch
> > >> /home/user/qubes-src/vmm-xen/PKGBUILD: line 49: autoreconf: command
> not found
> > >> ==> ERROR: A failure occurred in build().
> > >> Aborting...
> > >>
> /home/user/qubes-builder/qubes-src/builder-archlinux/Makefile.archlinux:120:
> recipe for target 'dist-package' failed
> > >> make[2]: *** [dist-package] Error 2
> > >> Makefile.generic:139: recipe for target 'packages' failed
> > >> make[1]: *** [packages] Error 1
> > >> Makefile:208: recipe for target 'vmm-xen-vm' failed
> > >> make: *** [vmm-xen-vm] Error 1
> > >>
> > >>
> > >> Some ideas? :P
> > >
> > > Someone? :S
> > > I'm still having the problem. I tried making everything from fresh in
> a new VM, but i get the same error :P
> > >
> >
> > I have never tried to build a template but if this could help...
> >
> > If the script can't find the autoreconf binary maybe it has a bad PATH
> > or it's being executed in a chroot/VM where autoreconf doesn't exist...
> >
> > You could try to add some debug lines before the error, try to dump the
> > value of PATH. If PATH is right, try to determine if it's being executed
> > on a chroot or VM and if it has autoreconf installed in.
> >
> > Look at the code of:
> > --> Archlinux dist-prepare-chroot 

Re: [qubes-users] Re: Making archlinux template: on make autoreconf not found but it is installed

2016-08-03 Thread donoban
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 08/03/2016 02:11 PM, Facundo Curti wrote:
> 
> Thank you man! I solved the error making this: sudo chroot
> chroot-archlinux
> 
> then, inside the chroot: pacman -S autoconf
> 
> Now I have another error:
> 
>> perl: warning: Setting locale failed. perl: warning: Please check
>> that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), 
>> LANG = "en_US.UTF-8" are supported and installed on your system. 
>> perl: warning: Falling back to the standard locale ("C").
> 
> But I will try to solve it inside chroot again. If I have troubles
> with this, i will let you know. Thanks men!
> 

Nice to hear. You will get it :)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXoeTZAAoJEBQTENjj7QilJh0P/2e9fGldDrX/bGswxNq8E0pq
QvKBhg1iVTlG/4tOfZVuXoRr8FRkymqJKx6MNJdWQtov1i/dSpLt3J94KfYbO7FB
/CN3UWjwSJC8OBTs7jNdFXArUu0ouSiOq2436NzTPRVd7Wu03defZutP230k2q7E
YTUoohlzNw32w0W3EfotE0ipa3qwZ+OPOpdjXtAa8szKvxkH9CLvEt33tOmXp2jm
T9uxjKboUUBLHduwTAgWrjkqZUiRKdjg8gxUUGh/PYUYSYeF0oO0jsd+DNPa10DF
CKAXqCEnKJ9vgIHawU+yuCr3GKCaQHdH/io2k8JsFhaPQRHydJymxSxjusJQMojK
ScdTL/oYfdwGF2lqk0JDU5Hu/sD+Is1iUx6uYTwQi40QtL18+z6/YIQNxpmTNP/a
xgFavz22PHoWvW5JoSNo5MZ2wWlJp2rz8DErnH7dDNEqMFUbFoY/PRHzg/uQu1Pi
nTu+4LUE77OOxRpIp66djTlmxEGoQmLJkG6mAX6UTfGKqoSGZhY8EMw7pbfdeGrj
Vz99QIVM2/AkW2Zi4nSodn0wVa0Iv4c6r2w0PQeYqnQvNE3tlXQ69Rjn/ryOfRv0
NNVqGdC665rl2p4GiOAJkLCDN5UNO8uKfKYrX/uM0vwq2fHZ2y8LwIRmch4Xpbk3
nt1PnRFUOhtAi3Rw8HmY
=bX/Q
-END PGP SIGNATURE-

-- 
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/471297e2-2c90-b7f3-f48d-1c7ccbb77a65%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Making archlinux template: on make autoreconf not found but it is installed

2016-08-03 Thread Facundo Curti
El miércoles, 3 de agosto de 2016, 7:49:33 (UTC), donoban  escribió:
> On 08/03/2016 07:23 AM, Facundo Curti wrote:
> > El martes, 2 de agosto de 2016, 12:25:38 (UTC), Facundo Curti  escribió:
> >> Hi there. Someone can help me?
> >> I'm trying to make an archlinux template on qubes 3.2. But i'm having 
> >> troubles to compile.
> >>
> >> When I do:
> >> $ make vmm-xen-vm
> >>
> >> I get:
> >> /home/user/qubes-src/vmm-xen/PKGBUILD: line 49: autoreconf: command not 
> >> found
> >>
> >> But autoreconf is already installed:
> >> $ whereis autoreconf
> >> autoreconf: /usr/bin/autoreconf /usr/share/man/man1/autoreconf.1.gz
> >>
> >> Here is the complete output:
> >>
> >> [user@development qubes-builder]$ make vmm-xen-vm
> >> Currently installed dependencies:
> >> git-2.5.5-1.fc23.x86_64
> >> rpmdevtools-8.9-1.fc23.noarch
> >> rpm-build-4.13.0-0.rc1.13.fc23.x86_64
> >> createrepo-0.10.3-3.fc21.noarch
> >> debootstrap-1.0.81-1.fc23.noarch
> >> dpkg-dev-1.17.25-6.fc23.noarch
> >> python-sh-1.11-1.fc23.noarch
> >> dialog-1.3-4.20160424.fc23.x86_64
> >> --> Archlinux dist-prepare-chroot (makefile):
> >>   --> Checking mounting of dev/proc/sys on build chroot...
> >>   --> Synchronize resolv.conf, in case it changed since last run...
> >> -> Building vmm-xen (archlinux) for archlinux vm (logfile: 
> >> build-logs/vmm-xen-vm-archlinux.log)
> >> --> build failed!
> >> ==> Retrieving sources...
> >>   -> Found xen-4.6.1.tar.gz
> >>   -> Found series-vm.conf
> >>   -> Found apply-patches
> >> ==> WARNING: Skipping all source file integrity checks.
> >> ==> Extracting sources...
> >>   -> Extracting xen-4.6.1.tar.gz with bsdtar
> >> bsdtar: Failed to set default locale
> >> ==> Starting build()...
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/qemu-tls-1.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/qemu-tls-2.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.qubes/xen-shared-loop-losetup.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.qubes/xen-no-downloads.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.qubes/xen-hotplug-external-store.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.qubes/xen-tools-qubes-vm.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.qubes/vm-0001-hotplug-do-not-attempt-to-remove-containing-xenstore.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/libxc-fix-xc_gntshr_munmap-semantic.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/libvchan-Fix-cleanup-when-xc_gntshr_open-failed.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/0101-libvchan-create-xenstore-entries-in-one-transaction.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/0001-configure-Fix-when-no-libsystemd-compat-lib-are-avai.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/0001-libxc-prefer-using-privcmd-character-device.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/0001-tools-hotplug-Add-native-systemd-xendriverdomain.ser.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.security/xsa155-xen-0003-libvchan-Read-prod-cons-only-once.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.libxl/0001-libxl-trigger-attach-events-for-devices-attached-bef.patch
> >> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
> >> ./patches.misc/0001-systemd-use-standard-dependencies-for-xendriverdomai.patch
> >> /home/user/qubes-src/vmm-xen/PKGBUILD: line 49: autoreconf: command not 
> >> found
> >> ==> ERROR: A failure occurred in build().
> >> Aborting...
> >> /home/user/qubes-builder/qubes-src/builder-archlinux/Makefile.archlinux:120:
> >>  recipe for target 'dist-package' failed
> >> make[2]: *** [dist-package] Error 2
> >> Makefile.generic:139: recipe for target 'packages' failed
> >> make[1]: *** [packages] Error 1
> >> Makefile:208: recipe for target 'vmm-xen-vm' failed
> >> make: *** [vmm-xen-vm] Error 1
> >>
> >>
> >> Some ideas? :P
> > 
> > Someone? :S
> > I'm still having the problem. I tried making everything from fresh in a new 
> > VM, but i get the same error :P
> > 
> 
> I have never tried to build a template but if this could help...
> 
> If the script can't find the autoreconf binary maybe it has a bad PATH
> or it's being executed in a chroot/VM where autoreconf doesn't exist...
> 
> You could try to add some debug lines before the error, try to dump the
> value of PATH. If PATH is right, try to determine if it's being executed
> on a chroot or VM and if it has autoreconf installed in.
> 
> Look at the code of:
> --> Archlinux dist-prepare-chroot (makefile):
> 
> It seems that it uses a chroot where doing the build. Try to find it.

Thank you man!
I solved the error making this:
sudo chroot 

Re: [qubes-users] If Ubuntu's license is keeping us from having a ready-made template...

2016-08-03 Thread Achim Patzner
Am 03.08.2016 um 13:08 schrieb Marek Marczykowski-Górecki:
> On Wed, Aug 03, 2016 at 12:42:25PM +0200, Achim Patzner wrote:
> > ... what about preparing a Mint template that can be distributed?
>
> That's good question. I guess only that no one added support for it in
> builder-debian plugin (or separate one).

Hm. Who is that No One I keep hearing so much about lately and what does
it take to convince him to spend some time on it? 8-)


Achim

-- 
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/433b8e56-d677-7d46-430b-f110b7925ebd%40noses.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] If Ubuntu's license is keeping us from having a ready-made template...

2016-08-03 Thread Achim Patzner
... what about preparing a Mint template that can be distributed?



Achim

-- 
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/9ac396bf-19ea-fb7a-8ce8-8f2f803ecd6d%40noses.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: x201t not compatible

2016-08-03 Thread pixel fairy
On Tuesday, August 2, 2016 at 11:44:43 AM UTC-7, Bill Wether wrote:
> Try disabling VT-d in the BIOS. It's a common Lenovo problem. 
> 
> Cheers
> 
> BillW

ok, i totally missed https://www.qubes-os.org/doc/thinkpad_x201/

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/aacc1181-0e9a-47e6-9469-528cb76c9ce3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] 3.2 RC - which VM settings?

2016-08-03 Thread JPL
On Wednesday, August 3, 2016 at 10:56:37 AM UTC+1, Alex wrote:
> On 08/03/2016 11:39 AM, JPL wrote:
> > [...]
> > Can someone tell me what difference the following settings will
> > make:
> > 
> > - Initial memory min / max. I'm going for 500/3000 fo0r all as I have
> > 8GB memory. Reasonable?
> Don't overprovision for system-related VMs. A netVM will rarely need
> more than 1GB, same for firewallVM.
> 
> You appVMs may vary: in my work vm, where I use 2 IDEs (Android Studio
> and MonoDevelop) + android emulator + firefox + thunderbird, I capped at
> 10GB and it works ok. My workstation has 32GB ram.
> 
> > - VCPUs - defaults to 2 but I can pick a maximum of 8. Which should I
> > choose (processor is Intel i7)?
> Don't overprovision vCPUs: the hypervisor will have to find *that many*
> cores free at the same time to run your VM, and that's why VMWare
> recommends 1vCPU for every VM on their ESX/ESXi infrastructure that you
> can upgrade to 2 if needed.
> 
> I am against giving more than 2 vCPUs per VM in Qubes, and I recommend
> careful experiments when tweaking this value (increment by 1 and test
> with your actual workload, if there are performance gains or losses).
> 
> > - Tickbox for include in memory balancing. What difference does this
> > make? Should I tick it for all VMs?
> You cannot have memory balancing enabled for VMs with devices attached;
> apart from that, there's no actual reason to allocate fixed amounts of
> RAM for you VMs. Say, you dedicated 10GB out of 16 to one important VM,
> but now you're just upgrading your templates with all the appVMs turned
> off, and you'd like the templates to benefit of all available memory
> without having to manually correct allocations. Or you just closed your
> personal Firefox instance to gain a little room for a big compilation in
> the work AppVM.
> 
> TL;DR: I think the defaults provided in Qubes are reasonably ok, and
> while they may be changed if needed, changes should be tested carefully
> - knobs are inter-dependent, and giving "more" of any one may actually
> reduce performance overall, or for specific tasks.
> 
> -- 
> Alex

Thanks for the detailed answer Alex. Makes sense now. Cheers

-- 
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/550d9430-3084-4e10-b7c7-7abda108d8b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Question about Whonix / Tor Browser / exploits

2016-08-03 Thread neilhardley
So you're saying that you can run an entire Xen exploit without installing 
anything to the hard drive at all... Just purely run it in the RAM itself.

Wow.

And what do you think about Selfrando..?

Is this going to fix browser exploits once and for all, or will it just fall to 
hackers..?

https://blog.torproject.org/blog/selfrando-q-and-georg-koppen

"Selfrando randomizes Tor browser code to ensure that an attacker doesn't know 
where the code is on your computer. This makes it much harder for someone to 
construct a reliable attack--and harder for them to use a flaw in your Tor 
Browser to de-anonymize you."

http://news.softpedia.com/news/tor-browser-integrates-tool-to-fend-off-deanonymization-exploits-505418.shtml

"While ASLR takes code and shifts the memory location in which it runs, 
Selfrando works by taking each code function separately and randomizing the 
memory address at which it runs.

If the attacker cannot predict the memory position at which pieces of code 
execute, then they cannot trigger memory corruption bugs that usually allow 
them to run rogue code inside the Tor Browser"

-- 
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/d402e4ba-03b6-45b8-a0e8-381198bedbfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] 3.2 RC - which VM settings?

2016-08-03 Thread JPL
A clean install of 3.2 failed at the configuration stage so I am creating and 
configuring the sys-net, sys-firewall sys-whonix and all appVMs manually.

Can someone tell me what difference the following settings will make:

- Initial memory min / max. I'm going for 500/3000 fo0r all as I have 8GB 
memory. Reasonable?

- VCPUs - defaults to 2 but I can pick a maximum of 8. Which should I choose 
(processor is Intel i7)?

- Tickbox for include in memory balancing. What difference does this make? 
Should I tick it for all VMs?

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/9372c838-cbb8-404c-a1e1-09fd84000908%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Upgrading from Qubes 3.1 to 3.2 fail

2016-08-03 Thread donoban
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


On 08/03/2016 09:35 AM, donoban wrote:
> The only think that I did on both install was installing Xfce
> after the default KDE install
> 

Ah and I removed the fedora templates -_-
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXoaXhAAoJEBQTENjj7QiltWIP/0KtMn38RUQDdNnkqT9nyVDX
oRcty9OwAbskp/AHAxAuFyGbL5aKibqzn7Z9NL99QC55/wKne90XPVU7WjYcXuIy
2JRxIZvn+dA0X2clpEpxiyL0CyXXxh3u0NGBUgWcufOjVHZ9mF+9XDE/70Bac4A+
ItkLod2aRHVVMAI2x9/K7Fk1GFzLN7KL3FwUp+aGtz2oBVTETN40DNzEk9PvtVCA
YNeQxvXoCdkOiXOhgsymGXCxJEI3RRt7x7HVPaqy/3TKpTaQrTN6IJN4uOYsM8K3
Gokgi3lUEJHEiNq0rsIqSHee7E4VXPTO54LtPMPFSZWaHc45yeViNyPIBGoMQtzs
2mnFO4IEaktBkjuMFJCZ54DjgueiuJPtcQDALCzFhGV32oDMyL/pyGpqTTP2usa9
xGpN7Owtk9F/yLDcWXwHBfCAqUcz/DhTY2qP0dAD7CBHq/liff4rJZHgWXnqwBf9
Lq78KE4Er5/ogQ8bGsn+G9dzT9gZziuvkX9mgI12Z9sl407fQiRQhS3SRim+Pp8K
o+O5sMGgBgU7fo8+2wKGZ1BWeUckt5XIbnOvUSK6UaX7l8QiZ6Qhqp1Jh5OqWcOp
kWhlzAXo0uWuAskTJ1W1JsA8AsbsqEVTcfsWci7+4w5GMErypS8Ny716EJg2aumt
005OaS8W2YMwDQkVqjSK
=eSwx
-END PGP SIGNATURE-

-- 
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/a7fc8a0d-ac60-2d97-d5ad-df04ead2237a%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Making archlinux template: on make autoreconf not found but it is installed

2016-08-03 Thread donoban
On 08/03/2016 07:23 AM, Facundo Curti wrote:
> El martes, 2 de agosto de 2016, 12:25:38 (UTC), Facundo Curti  escribió:
>> Hi there. Someone can help me?
>> I'm trying to make an archlinux template on qubes 3.2. But i'm having 
>> troubles to compile.
>>
>> When I do:
>> $ make vmm-xen-vm
>>
>> I get:
>> /home/user/qubes-src/vmm-xen/PKGBUILD: line 49: autoreconf: command not found
>>
>> But autoreconf is already installed:
>> $ whereis autoreconf
>> autoreconf: /usr/bin/autoreconf /usr/share/man/man1/autoreconf.1.gz
>>
>> Here is the complete output:
>>
>> [user@development qubes-builder]$ make vmm-xen-vm
>> Currently installed dependencies:
>> git-2.5.5-1.fc23.x86_64
>> rpmdevtools-8.9-1.fc23.noarch
>> rpm-build-4.13.0-0.rc1.13.fc23.x86_64
>> createrepo-0.10.3-3.fc21.noarch
>> debootstrap-1.0.81-1.fc23.noarch
>> dpkg-dev-1.17.25-6.fc23.noarch
>> python-sh-1.11-1.fc23.noarch
>> dialog-1.3-4.20160424.fc23.x86_64
>> --> Archlinux dist-prepare-chroot (makefile):
>>   --> Checking mounting of dev/proc/sys on build chroot...
>>   --> Synchronize resolv.conf, in case it changed since last run...
>> -> Building vmm-xen (archlinux) for archlinux vm (logfile: 
>> build-logs/vmm-xen-vm-archlinux.log)
>> --> build failed!
>> ==> Retrieving sources...
>>   -> Found xen-4.6.1.tar.gz
>>   -> Found series-vm.conf
>>   -> Found apply-patches
>> ==> WARNING: Skipping all source file integrity checks.
>> ==> Extracting sources...
>>   -> Extracting xen-4.6.1.tar.gz with bsdtar
>> bsdtar: Failed to set default locale
>> ==> Starting build()...
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/qemu-tls-1.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/qemu-tls-2.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.qubes/xen-shared-loop-losetup.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.qubes/xen-no-downloads.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.qubes/xen-hotplug-external-store.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.qubes/xen-tools-qubes-vm.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.qubes/vm-0001-hotplug-do-not-attempt-to-remove-containing-xenstore.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/libxc-fix-xc_gntshr_munmap-semantic.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/libvchan-Fix-cleanup-when-xc_gntshr_open-failed.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/0101-libvchan-create-xenstore-entries-in-one-transaction.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/0001-configure-Fix-when-no-libsystemd-compat-lib-are-avai.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/0001-libxc-prefer-using-privcmd-character-device.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/0001-tools-hotplug-Add-native-systemd-xendriverdomain.ser.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.security/xsa155-xen-0003-libvchan-Read-prod-cons-only-once.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.libxl/0001-libxl-trigger-attach-events-for-devices-attached-bef.patch
>> + patch -s -F0 -E -p1 --no-backup-if-mismatch -i 
>> ./patches.misc/0001-systemd-use-standard-dependencies-for-xendriverdomai.patch
>> /home/user/qubes-src/vmm-xen/PKGBUILD: line 49: autoreconf: command not found
>> ==> ERROR: A failure occurred in build().
>> Aborting...
>> /home/user/qubes-builder/qubes-src/builder-archlinux/Makefile.archlinux:120: 
>> recipe for target 'dist-package' failed
>> make[2]: *** [dist-package] Error 2
>> Makefile.generic:139: recipe for target 'packages' failed
>> make[1]: *** [packages] Error 1
>> Makefile:208: recipe for target 'vmm-xen-vm' failed
>> make: *** [vmm-xen-vm] Error 1
>>
>>
>> Some ideas? :P
> 
> Someone? :S
> I'm still having the problem. I tried making everything from fresh in a new 
> VM, but i get the same error :P
> 

I have never tried to build a template but if this could help...

If the script can't find the autoreconf binary maybe it has a bad PATH
or it's being executed in a chroot/VM where autoreconf doesn't exist...

You could try to add some debug lines before the error, try to dump the
value of PATH. If PATH is right, try to determine if it's being executed
on a chroot or VM and if it has autoreconf installed in.

Look at the code of:
--> Archlinux dist-prepare-chroot (makefile):

It seems that it uses a chroot where doing the build. Try to find it.

-- 
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 

Re: [qubes-users] MicroSD assigned to dom0 and not to sys-usb

2016-08-03 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Aug 03, 2016 at 02:56:09AM +, Jeremy Rand wrote:
> Marek Marczykowski-Górecki:
> > On Mon, Aug 01, 2016 at 07:35:26PM +, 468ezc+5r0fnwy87qeag via 
> > qubes-users wrote:
> >> Hi,
> > 
> >> My MicroSD while attached is assigned to dom0 and not sys-usb as is 
> >> supposed. Notwithstanding, USB devices are still assigned to sys-usb.
> > 
> >> Is this the intended behavior? Doesn't this increases, in the same manner 
> >> as usb devices does, the surface attack in dom0?
> > 
> > Your (micro)SD card reader is probably not a USB device, but PCI device.
> > Yes, it's better to assign it to some VM - sys-usb is ok. You can do
> > this in VM settings - "Devices" tab.
> 
> Seems to me that assigning the SD controller to a different VM than
> sys-usb would eliminate some attack vectors, since if they're assigned
> to the same VM, IOMMU won't prevent software accessing the SD card from
> attacking software accessing the USB devices (and vice versa).  A
> doomsday scenario that comes to mind is when the USB controller is being
> used to connect to the Internet via a phone tether, and the SD card is
> storing some high-value data.  (My doomsday imagination is limited;
> perhaps there are better doomsday scenarios.)
> 
> Is my intuition on this corect?

Generally yes, but I think it's rather little value. If you have
higi-value data, you should encrypt it anyway. Outside of device-facing
VM of course. Generally the VM where you (or someone else) can plug
potentially malicious device, should not be trusted.

> Of course, using a separate VM means increased RAM usage, which may or
> may not be worth it.
> 
> Cheers,
> -Jeremy Rand
> 



- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXoZtxAAoJENuP0xzK19csKVkIAI1CNc7J08vF9WVg2ji/6eQ8
vcAqm+FUwQuvf09dyV+PgbfSoX2GIKsu/v41qXNuq/WgZ9qUmzsIDd+N7Kxm6SVQ
pj3dB8jPdLZoVH6YZTa/MRxZLLtglMNoNSrVKVPaBKql2vo3jQRzIva6JwBBYQLk
fRPZdVyS5movd66xpEAMsB7C67mMv0RpupfXqQ9UZbBQzGugX/+pRgZaxzFa02ol
t0nXj8Hb0COFLLxfN4XIwUFZBXuaK6cQ1lQrafYbyL6YFuC4s7A3d3Fs5er9tM1A
St526GFmtV/oWCJj+PREY+qJ6SS9dVzVmkTaFUgUqkLA63FkdIVakeqSWi1qZg8=
=FLg2
-END PGP SIGNATURE-

-- 
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/20160803072120.GJ32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.