Re: [qubes-users] Qubes VM compromised? - Follow up

[johnyjukya]

> My guess is that Paypal is giving you a hard time just because of the
> tor exits you use to interact with their website.

Could be.  At first I didn't see how/why, but I guess refusing a legit
password from what they judge as a dodgy IP address is a possibility.

(Although accepting the password change on a Tor exit, and then refusing
that on a non-Tor https: connection was rather weird.  Would they silently
fail a password change?  Oh well, I won't stress over it, but will keep a
close eye on things, for sure.  Ever vigilant...)

> So it seems to me all that you are saying is really related to
> using tor via sys-whonix or manually trough the traditional means.

Yes.  I guess it really isn't necessarily anything to do with Qubes,
unless there is some dom0 compromise somewhere.  That's probably pretty
unlikely, and I've only seen weirdness in Tor-based VM's, so I won't give
up on Qubes.

I've been using Tails for awhile, and never had strangeness like this; but
the new factors aren't necessarily Qubes, but the TorBrowser bundle (not
the Tails-reviewed/tested one) and Whonix.

Worst case, I could (and have successfully) just run Tails inside Qubes,
and it should be no worse (safer, actually) than Tails standalone, for
banking or email.  (I was reading that the IOMMU protection prevents DMA
attacks, which is sweet.)

> The sigaint episode is easily explained through the e-mail you provided.

Certainly.

> But yes, the Paranoia is our shepherd and nothing shall lack.
> Paranoia is what justifies the development of a operational system
> of this nature, it shall never die.

Beautiful.  I think I'll put that on a plaque for my wall.

Respect for paranoia, awesome.  I guess a mailing list for a
security-focused operating system is a bit more sympathetic to my concerns
than the general public.  Feels like home, man.  :)

If I tell family and friends about the sad state of computer/network
security these days, the hacks I've seen, and the Snowden stuff, they
think I'm bonkers.

Now why I didn't receive your response (posted a few hours ago) via email
but only see it on the Google Group's page. . .  I'll just assume SIGAINT
is still dealing with some capacity issues.  :)

(I wonder if their surge in signups is possibly a denial of service. 
They've been targeted with at least one significant exit-node attack in
the past. 
https://lists.torproject.org/pipermail/tor-talk/2015-April/037549.html )

Thanks for your reply.

JJ

-- 
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/871a2a68cefc1b3ebf7af8df53bc5ffb.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes VM compromised? - Follow up

[Desobediente Civil]

My guess is that Paypal is giving you a hard time just because of the
tor exits you use to interact with their website.

So it seems to me all that you are saying is really related to using tor
via sys-whonix or manually trough the traditional means.

The sigaint episode is easily explained through the e-mail you provided.

But yes, the Paranoia is our shepherd and nothing shall lack. Paranoia
is what justifies the development of a operational system of this
nature, it shall never die.

-- 
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/bd3c3f0a-6a20-7f99-e486-3dc9393a5c54%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] timesync on by default in debian-8 template (3.2-testing)

[johnyjukya]

I would say so, yes.

I think exim, cups, and possibly some gvfs-samba thing were also all
enabled on both the Fedora and debian-8 templates.

I personally don't like having those on by default in all the VMs,
listening on ports and poking around the network or Internet, as they
really should only be installed or enabled when you need them.

The samba browser thing was making name resolution requests to some
Internet server which (from some brief googling) appeared to owned by
Microsoft.  Not particularly cool.  :)

(It's possible the Samba thing was dragged in by some other packages I
installed, although I'm fairly sure exim/cups were on in the default
fedora/debian templates.)

I know the firewall should prevent incoming connections to any listening
daemons (exim/cups/samba), but they're free to call out, as the samba
browser was doing.  (And I hadn't done anything referring to a smb address
on the system.)  Even with the firewall, why increase any attack surface
on unused services.

JJ

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-08-22 08:37, johnyju...@sigaint.org wrote:
>> I notice in the debian-8 template that network time synchronization
>> seems
>> to be on by default in systemd.
>>
>> systemd-timesyncd.service  loaded active running   Network Time
>> Synchronization time-sync.target   loaded active active
>> System
>> Time Synchronized
>>
>> It's disabled in fedora-23 by default, and rightly so, as I believe it's
>> unnecessary given the dom0 driven /etc/qubes-rpc/qubes.SetDateTime
>> mechanism, and it's kind of "leaky" sending requests unnecessarily to
>> the
>> Internet.
>>
>> Paranoidly yours,
>>
>> JJ
>>
>
> Would that fall under this issue?
>
> https://github.com/QubesOS/qubes-issues/issues/1928
>
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCgAGBQJXvg6zAAoJENtN07w5UDAwkZgP/2P/jWqOseHVrJ+X0ogVa/U4
> lFTIG5AzBt9oLx7BaBy0arsKHRyHGkWGbW1fVzDnCAzkCDKrpq3eNQX6FesMmn8e
> IIPyg7UqTnC29PZvKeZd/DlRGBM5q9jj6HMEcjTDWuc3jD1fKTe2GiDc7Cj4U6Bf
> /aIKtgvdZAZAh0OBINcAezmeOsm6Lc1k0HEPzhdF4iUQUUNgmU+RTdMarZxSReR6
> KxEQmxki568ccbxH0oUtifX8so8+1hAQCnB8yzhw6U/CjDl0TVWtpuHZ/P+hMARO
> EHu7vJDWCbgSr9hf0w4sfZA5LVXaVySbFfC2s9PwIFchmJnD/kg11o9jX+aa2ZuU
> qERxpTihpa2fqWEZ1fk4bQttgbcIzgAoAAVq6rcDOVuGFo+aVMgu+TmJSCU4ybs5
> +3TDvAQJez2z8dvQYvn6kgjQ5MP0PfMZALZSGAdVaTy2B0dNFsnhmiVnzLNLeJKo
> iI/k4EB8qxKcYfOR4wqS0OW9q+stAX8Dq3JO2uWZTnz5NVUacreW6h48WBM/7KCd
> VOtD+3DG/n1n4LNcBqYsZKWVd7/RqRv6+p4z6sICAanY09m87qpnRkeb8wQ7BTWw
> qOFhRZ/cZgjJnaw/qukt9kmU9BZdiAsENDiroCdHGDYJbEqINfV6dCdxL8UyoA1h
> U+t8DDt9iZrZKWU0tl6/
> =tGyU
> -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/5fe9f924-88e4-1820-ddf3-927095c699ca%40qubes-os.org.
> 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/42fd9ff91877330c37f9edc4f48b258e.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Node.js global modules

[angelo "angico" costa]

Hi, all!

I'm using Qubes 3.1 and I'm new with all this compartimented system idea.

I use Node.js for my work and study, and several of its modules should to be 
installed globally. My question is: Should I install those modules in the VM 
where I'll use them, or should I install them from the template VM?

TIA and regards,

Angico.

-- 
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/d220ce8e-f1b5-4617-995f-08e1986452a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing Signal on Qubes mini-HOWTO

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-15 14:43, IX4 Svs wrote:
> On Mon, Aug 15, 2016 at 10:19 AM, Andrew David Wong  
> wrote:
> 
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>> 
>> On 2016-08-14 15:22, IX4 Svs wrote:
>>> Just spent a few minutes to figure this out so I thought I'd share.
>>> 
>> 
>> Thanks, Alex! Would you mind if we added this to the docs at some point?
>> 
>> 
> Not at all - especially if you improve my clumsy way of creating the custom
> shortcut (steps 7-12) and use the proper Qubes way that Nicklaus linked
> to.
> 
> Cheers,
> 
> Alex
> 

Added:

https://www.qubes-os.org/doc/signal/

Thanks!

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXvhtNAAoJENtN07w5UDAwxLgP/19yfsizmDa5aJGXU7I3J+2C
uioZbQzJDoEm3P/m92keEL/36ffLOnl/f8uIibJyIgYtBBuMomZ42nDocKpq+Rv9
JXlxKCO2FY/OjkdmWWAbefzDXHEg9UnuVWZZau31kovegiNeJ0sWr6pttjCxsE4o
aGtC0+W6Rn2s8H/okyPdg0jhev8l/UISMuJzeynTznJqI8dj4/Pelwq5mCmWaol7
kIXghTxJDVYYu14uvVYKJiek8OsaEEM99UnMd6dellWI5l18UZDStiQW6CWWKUlz
MadrbzM654HUxJ3yuNx5hlBFMbhBEa+Z/KjLz1/FHFs7mo6KprPcEkLr3f/Hec2C
GPqZqPFxPyyOIqM7pXn7s9GGpFJWB25NcL90ub5K0RcNvon2VH99D0LJ7IZz4pV0
tDDAD6X4K1JgNHpXgByByiqd4AxKNTKRoPCjKDCOO8YZkaVNRoxXeZMdjgH9/G7N
XTqPiiblV5T4SEeDsxlnrUv10W88+kYM8vumm5lnnvgbcmqKJtMBn63sgg9J4cly
HkqUuyuZXHjhZQYwYpNUyyh5P6nDYo35lyTfiNcXz9trE3BQiqKE0wUCdfqdSLk7
KOYrTe7jYYizFD6DTQLSM7ZPBYdVmjlbMK8Xu7LIAQCI1l7gDc93DYcBUlmoSPcZ
eivEvkXWw46L4MZNAvj3
=djis
-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/56ee058c-5f6a-b1a4-43ae-748db4057ecc%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Requirements for Qubes Tools and seamless integration?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-23 20:11, Drew White wrote:
> Hi developers and users,
> 
> I'm trying to find out what is required for building template in Qubes, but
> I still can't find any documentation on it that accurately tells me what I
> want to know.
> 
> I've asked this a long time ago when I was first thinking about building a
> template and want this information so that I will know if it's even going
> to be possible in the first place.
> 
> Is there anyone out there that can list for me what is required for Qubes
> integration on a Linux System? (Debian based and RedHat based)
> 
> I'm looking to find out the EXACT requirements, not what many think that
> I'm asking.
> 
> Some of the things, but not all of what I'm trying to find out the
> requirements of..
> 
> SystemD requirements, GUI requirements, Qubes Packages requirements, system
> package requirements, kernel requirements.
> 
> Pretty much all the packages that are REQUIRED as a minimum to get it all
> to work.
> 
> Sincerely, Drew.
> 

These probably aren't what you're looking for, but since you didn't say that
you've already read these documents, and since they're relevant to the topic,
I'll share the links here in case they happen to contain some information that
is relevant to you:

https://github.com/QubesOS/qubes-template-configs
https://www.qubes-os.org/doc/building-non-fedora-template/
https://www.qubes-os.org/doc/building-archlinux-template/

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXvhCwAAoJENtN07w5UDAwUfEQAKCG/ZqoicJO5Va/SB/+7NFz
7Bo09feV/lmD08C8L0ZMBPgXPVY6rQ+XqyzNeu9cKkLGBq/IfZqF91tZ2u3shGhP
QADo7ZmdUiFnuXX038ZrfccX53Tlevz7CaMRLGJ99rVEDNHSfYQwo5ld0EK7afio
o2Or6U8wXIhq1aYyB5vYSGuOjBA/FJy5MbOzlJze+g5SFuP3EC5nQugXPzzjyzyT
TO4EatWdFkJFPidpJtcwKf/roEGA8llDD0TBdX5yEpyNhvmwmzN4NVMkLAXec6e2
R7lJQlMqve83elhbr6QXyyebssgzkbZDM+Ys6Jhep0OCNpGQTL4GyaxyHaO+Jz7H
GdFpcFnMC8lyj3WbPSh/fGBRK5iUku5pCy43o2iq/N78EvJbAJ/9U+JscVQL58wI
p6YmyI7SB7S4u1vLeiFiQzLibHrcI+BXkAwZu6Wk6JWCQ3nPn7t9LkQxNXy7GbUz
weA+zw9biVJxYc8kI0EqQN+kIoN/u5ZiB5Q4yCEQAJi5TZKa/rA6bhTykKuxH5YT
QQDOQ/ZMpvorWjStIUsNdBqojYFiLshDco3WA/9/LQlbX03ABMEAuttp+tfZNhUn
znqjqYH1Sz6lURC3sxlcU3sPLb7be7cDxExX8YjZ5YFqzE0nN+DzG8bGe0Dpe5LI
Fiy4mnzIUs3Pp177lLzV
=65sE
-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/73ba5171-c7b9-ea39-cacd-58dca5835d8d%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL ASUS rog g752vl-dh71

['n/a' via qubes-users]

Hi,
So far with one exception Asus ROG g752vl-dh71 seems to be working well with 
Qubes. Thanks for all your efforts!!
Exception, touch-pad (not working), Works in mint I believe xinput states it is 
an Elantec or something simmilar - in Qubes xinput did not detect it.
Best wishes,anon85..

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


Qubes-HCL-ASUSTeK_COMPUTER_INC_-G752VL-20160822-224446.yml
Description: application/yaml

[qubes-users] Re: Building Archlinux Template Error

[Foppe de Haan]

On Thursday, August 18, 2016 at 6:40:42 PM UTC+2, Jovan Miloskovski wrote:
> Hi,
> I'm really learning all of this template building stuff right now but I've 
> stumbled upon an error in the Archlinux qubes template building process I 
> can't find a solution for.
> Here is the segment of the error in my terminal output:
> 
> -> Building vmm-xen (archlinux) for archlinux vm (logfile: 
> build-logs/vmm-xen-vm-archlinux.log)
> --> build failed!
> gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe 
> -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing 
> -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   
> -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .libxl_create.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   
> -Werror -Wno-format-zero-length -Wmissing-declarations 
> -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
>   -Wshadow -include 
> /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h  
> -c -o libxl_create.o libxl_create.c 
> gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe 
> -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing 
> -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   
> -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .libxl_dm.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -Werror 
> -Wno-format-zero-length -Wmissing-declarations 
> -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
>   -Wshadow -include 
> /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h  
> -c -o libxl_dm.o libxl_dm.c 
> gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe 
> -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing 
> -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdir-install-libxl.d 

[qubes-users] Re: Building Archlinux Template Error

[richard . gold]

On Thursday, August 18, 2016 at 5:40:42 PM UTC+1, Jovan Miloskovski wrote:
> Hi,
> I'm really learning all of this template building stuff right now but I've 
> stumbled upon an error in the Archlinux qubes template building process I 
> can't find a solution for.
> Here is the segment of the error in my terminal output:
> 
> -> Building vmm-xen (archlinux) for archlinux vm (logfile: 
> build-logs/vmm-xen-vm-archlinux.log)
> --> build failed!
> gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe 
> -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing 
> -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   
> -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .libxl_create.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   
> -Werror -Wno-format-zero-length -Wmissing-declarations 
> -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
>   -Wshadow -include 
> /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h  
> -c -o libxl_create.o libxl_create.c 
> gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe 
> -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing 
> -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdir-install-libxl.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   
> -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .libxl_dm.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -Werror 
> -Wno-format-zero-length -Wmissing-declarations 
> -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/libxc/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
> -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/xenstore/include
>  -I/home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/include 
>   -Wshadow -include 
> /home/user/qubes-src/vmm-xen/src/xen-4.6.1/tools/libxl/../../tools/config.h  
> -c -o libxl_dm.o libxl_dm.c 
> gcc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe 
> -fstack-protector-strong -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing 
> -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE   -O2 
> -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -D__XEN_TOOLS__ 
> -MMD -MF .subdir-install-libxl.d 

Re: [qubes-users] Qubes for running virtual servers

[darren . op]

On Tuesday, 23 August 2016 17:13:13 UTC+1, johny...@sigaint.org  wrote:
> > How does Qubes perform as the host OS in a virtualised server environment?
> >
> > I'm thinking of a configuration where the host OS is Qubes with VM's
> > running for things like a virtualised email server, IDS server, perhaps a
> > Tor relay etc. I've used Qubes as a desktop host, I'm just curious about
> > whether it's a practical host for virtualised serviers?
> 
> I would think it would perform wonderfully as a virtualized server.  Most
> commercial places that rent you virtual servers use Xen, and Qubes is
> based upon Xen, so . . .
> 
> And the separation of server to prevent cross-contamination is a great
> feature.
> 
> I used a Xen-based virtual server at Rackspace for years, and it performed
> wonderfully.
> 
> Now, if you have a server that's going to be handling a high level of
> traffic, you're going to want some correspondingly powerful hardware and
> memory behind it.
> 
> But the success of running servers under Xen is a proven thing.
> 
> JJ


Thanks, that's what I had hoped. Traffic levels will be low since this is a 
small office environment and so just a few virtual servers handling small 
amounts of traffic.

-- 
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/bc92e088-f1ae-40c5-8936-71299b02d726%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] QUBES Windows Tools won't install

[Foppe de Haan]

On Monday, August 22, 2016 at 11:01:40 PM UTC+2, neilh...@gmail.com wrote:
> I remember when I first installed Windows Tools, I accidentally 
> double-clicked it and it was installing 2 versions of it at the same time.
> 
> This may have been what screwed up network access.
> 
> It may not be a glitch with Windows Tools at all.
> 
> Can Windows Tools be removed and re-installed in Windows "Add/Remove 
> Programs" or something like that..?
> 
> If not, I'll re-install my entire win7 again, and maybe this time it will 
> work.
> 
> What Windows Tools may need... is a system to prevent the user accidentally 
> installing it multiple times at the same time.
> 
> I had 2 installations of the exact same thing going at the same time. 
> 
> That's all I can remember doing wrong. This may not even be the reason at 
> all. It's just my theory.

not sure if it can be removed. Could you please check whether the windows 
(virtual) network adapter has gateway information set (check against the info 
on the QVManager settings page)? You may have to enter it manually.

-- 
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/17631c07-0255-472a-93d9-c951792ad9b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.