Re: [qubes-users] QUBES Windows Tools won't install
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.
Re: [qubes-users] Qubes for running virtual servers
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.
[qubes-users] Re: Building Archlinux Template Error
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 -D_LARGE
[qubes-users] Re: Building Archlinux Template Error
On Wednesday, August 24, 2016 at 4:14:12 PM UTC+2, Foppe de Haan wrote: > 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_
[qubes-users] Re: Building Archlinux Template Error
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 -D_LARGE
[qubes-users] HCL ASUS rog g752vl-dh71
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
Re: [qubes-users] Qubes VM compromised? - Follow up
> When I returned home, I tried logging in again, but from a different VM. > Failed repeatedly. I figured I must have messed up the password. No luck > trying other possibilities. Update: a signed message from SIGAINT indicating it was a system problem: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello all, Due to excessive signups over the last few days our authentication server cluster suffered a cascading crash. We have restored all encrypted credentials from a backup. Everything should be working normally now. If you are still unable to access your account, please email support. We are sorry for any inconvenience this may have caused everyone and our technicians are looking into a more robust authentication system to handle future growth. Thanks, SIGAINT -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXvMeKAAoJEM1IOzMPil9PVPAP/2UsdzaPJ1ZJstGhwsWHxLrp yyTHTn+r1n3bg0nrYx7HEVoS4xB4DAIMcihyOhXQHzs6leNQ1P9EmL0/S6A2qUFs kHwTtknxWSvgIwDMML4n5vFaaveECQX1f+UDh00nmTBvLGQHAJXP6XSp52ci7b4A 6rl4sfk6NDc3EeAiP/7LA6ImTCK/qdOK0BnrvyGGQdMdOTSBZNs9D+bDTw4nEEK8 F7uJFn2HOhIBKdm9+bNnkAvCAfjI1Yey4BH1U4/83J7abmqGmLTz5xCRPAqzId9G JCC4FqpFjutA1DBxnxKI7/z5nuJSUefsrpieu/QRk1SAdiasd89jQ1OE5KGfkGxe nhM2H+xc5vE1mbmMdu3f1GbxzHSeolyb8UXbd5ydIWpSGVvPIGAjoRFu0HaiP4JT wS8gkSJ1HV0BbAHL1YoJrsSqHt8evsku6sBXWnFI7JlRGJ07IUlyYKuLFC8wGx+4 EeozNLzR1UVR6YaeXL5JojPNZ6pZyNt14dxZ9F/SbHx1Wt3nVisVaNe6PNQlhf8s AYtK9Md6oqd+TnM/PYBdfr30HpGGKeLr+s0dah+Aec+/DwQclCkXqPlDgdVV2tI7 7dG+cU2m7atP6k6YnY6PQ+LfubmSOq60rIpEAObxHneHGu9VIvKX+swc+LI2NS56 d1g1X+tLVqMiNOQiSycP =2kOo -END PGP SIGNATURE- Seems legit. :) Had another bit of oddness today (under Cubes, Firefox in debian-8, no Tor, since commerce sites get grumpy about weird locations): Logged into PayPal for first time in months. It says there has been attempted access from an unexpected device or something, and forces me to change my password. I make sure the lock is showing for HTTPS, and it is, so I proceed. After doing so, I am unable to log in. Tried making a purchase with the new password, and it also failed. I just did another password reset via email, but I'm currently locked out for previously trying too many times. Will have to wait it out, and verify my new password is working and there was no unexpected activity. (The bank account it's hooked to shows no activity.) One possibility: I did a copy/paste from Keepassx in a non-network-connected AppVM. It's possible I was sloppy with the copy/paste or there were characters dropped somehow...? Haven't seen that before, but I suppose it's a possibility. I've also asked PayPal support if the forced-password-reset was a legitimate thing in their records, and there wasn't some spoofing going on. It probably was legit, but in the off chance it wasn't, I might take a break from Cubes for a bit :) 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/9b5cf48f25ea67d2888adf852a725a2c.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] timesync on by default in debian-8 template (3.2-testing)
-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 activeSystem > 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.
Re: [qubes-users] Pixels displayed after the cursor in a given frame are not rendered
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-08-23 10:26, Valentin Lorentz wrote: > Hello, > > > I installed Qubes R3.1 today. > > Most of the times I lock the session (either by explicitely close it, or > when the screensaver starts), I get a graphical bug. This happened with KDE > and Xfce. It also happened just after the installer finished. > > > Every pixel below the cursor (and also those which are both on the same > line as the cursor and at the right of the cursor) are not displayed > (black). Some widgets above the cursor are not displayed either (what would > be below the widget is displayed instead), I think it is because they are > rendered after the pixel the cursor is at. Also, in most frames, the > display is shifted right, and the rightmost columns are looped to the left > of the screen. In some frames, the cursor is not displayed. > > As this bug does not appear on screenshots, I'm sending a photo of my > screen as an attachment. > > My laptop is a Thinkpad x260, which I received today. As I said, the bug > occured just after running the installer, so it is not because of changes I > made afterward. I checked the .iso signature, and the installer checked the > media before starting. > > > Is this a known issue? If yes, what can I do to fix it? > > > Best regards, > > Valentin > I seem to recall someone sending a picture similar to yours to this list some time ago, but I can't seem to find the thread. (Maybe you'll have more luck searching than I did.) I also don't see any other x260's in the HCL, so I'm afraid I can't point you to any relevant threads. My best guess: Maybe it has something to do with your IGP/GPU? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXvg/TAAoJENtN07w5UDAwEOgP/Rfme1PylrXZI6O7ugTUnghJ 3u7Q1ifucWtSF+w+fQGmzJ0BSoEw6fTc+1n/vr9BbAiD2UcGEmqa3/mH94INWhKL ROiYcDFLO1QQdBZ3MM4CsfPxKxqfmsAUC0cPOhivP6HyXvbLA3Ze6vyqCeduO9ng cQ4RDJFo5+aP6h7IJjULa24KcIRFz3loIony9MjXBae5JrBWZPbI8+oShuM3IZ3D B/ZMYvgdy2FY/n5KfSc6naiLJhJRL/HVqOxXEKSYQrvOvCgyJ5uLKOxEjC/ZXN/e 78LeyfRTehnUlJ+mwa+4b6rRZF/Sv0QwvLKcOcaAlubPAVNFZOSOpRDp0Knlu7LR hn3yteEMj6XeMaeyZvyE5V4iPrO5etSLfUUl1rNIf7nUQ3CFXIijNN8vhh+/gKHv ctqXvJPaP05pSdw8MxOiefhljaAbp4ljDr994YkyBBnD1MJDoYeMfxMvTwP671/a n0qDqZSTwMfdT+FwozkTcjXED/ykgCPHQ2+L47m0URae6ta3pjFZmBtMlXYqzV+2 +KV8v2j3Y7pqu8XQMy0yO2vBryezLWwmouCLAz7n3GkO5Udz3j2vFXQ3fRXOVC4e LGCJ9jLoXNnNlI3kJmVf4+7nCBubkhh2Zf46XtbuSMqiJ951w8RDm7I5e/Z1FeLn 7SVnt+xqA7gUBUdrMbY0 =vQ9a -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/2127edb1-87ce-2fae-c272-5179681ca9b5%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Requirements for Qubes Tools and seamless integration?
-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.
Re: [qubes-users] installing Signal on Qubes mini-HOWTO
-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] installing Signal on Qubes mini-HOWTO
On Wednesday, August 24, 2016 at 3:10:34 PM UTC-7, Andrew David Wong wrote: > Added: > > https://www.qubes-os.org/doc/signal/ > > Thanks! just to clarify, this method will soon stop working because chrome apps are being killed, only chromeos (and probably chromiumos) will be able to run it. there isn't yet a viable qubes-os chrome desktop. cr os linux, linked above, is not chrome os, its just the chrome browser on the cinnamon desktop. so, unless its hacked to run chromeos apps, that wont work either. it is possible to build your own, or download an unofficial build of chromeos. whispersystems might make another desktop app that does not depend on chrome. or someone can take the source and make one. -- 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/5ada1426-1bed-4e4e-ac03-3696f48ea5f7%40googlegroups.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)
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
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] Qubes VM compromised? - Follow up
>> When I returned home, I tried logging in again, but from a different VM. >> Failed repeatedly. I figured I must have messed up the password. No >> luck >> trying other possibilities. I'm still a bit suspicious that one of my VM's has been compromised. I still saw password problems after restarting the VM's, too, so if there is a compromise, it is likely in the template. After waiting for the PayPal "too many tries" timeout period, from another OS, I tried to log into PayPal. It still failed. I did another email password change request, and was able to do so successfully, then finally log into my account. (No activity, whew.) However, when setting the new password, I once again generated a random 30 character password. This time, PayPal told me there was a 25 (I think it was) character limit on the password. Earlier today, when inside a Qubes VM, the forced password reset (due to "suspicous activity") accepted a 30 characater password without complaint. Maybe sloppy programming on PayPal's part, but for such a key function, it's highly doubtful. At the time of the forced password reset in the Qubes VM, I remember verifying that the URL was a PayPal URL, and that the SSL lock was present. I'm not sure how to proceed. I'm probably over-reacting, but at the moment I'm a bit too nervous to go back to Qubes. Where the VM's involved were debian-8 and Whonix (also debian based), maybe I'll back away from using those (and TorBrowser, which was involved in each instance), stick to the Fedora templates for now, and give it another shot. (Also, while I realize one of the biggest threats to TorBrowser is people not updating it regularly, I really don't like that it does an update check every launch. Too much phoning home for my tastes.) I prefer Debian over Redhat, and I like Whonix, but I think I'll try reducing the attack surface from 5 players/repos (Fedora/Qubes/Debian/Whonix/TorBrowser) to 2 (Fedora/Qubes) and see how that works out for me. I'll update the list if/when PayPal gets back to me on what they saw from their end. Insecurely yours, 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/f58e9f11597f7c7c6239191c352e4a0d.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes VM compromised? - Follow up
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] Qubes VM compromised? - Follow up
> 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.
