Re: [qubes-users] Install DNSSEC on ProxyVM type (debian) ?

2017-02-13 Thread ThierryIT
Le mardi 14 février 2017 02:57:28 UTC+2, Unman a écrit :
> On Mon, Feb 13, 2017 at 05:10:28AM -0800, ThierryIT wrote:
> > Hi,
> > 
> > Thx a lot for these information.
> > 
> > I  have installed dnssec-trigger on a newly created VM from a debian 
> > template as ProxyVM type. This is working, I  have checked for the DNSSEC 
> > and all are ok.
> > 
> > In the same way, I do have a VM to browse on internet,  and  I want all DNS 
> > request forwarded to this ProxyVM  freshly installed  ... How to do  this ??
> > 
> > Thx
> > 
> > Le lundi 13 février 2017 09:40:42 UTC+2, Andrew David Wong a écrit :
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA512
> > > 
> > > On 2017-02-12 23:18, ThierryIT wrote:
> > > > Hi,
> > > > 
> > > > I think that I have missed something concerning Qubes. When I
> > > > installed, let's say "Unbound" packages, after a reboot of the VM
> > > > it disappear ... Normal ?
> > > > 
> > > > Thx
> > > > 
> > > 
> > > You have to install it in the TemplateVM (or, for more advanced users,
> > > pick a persistent dir and/or use bind-dirs):
> > > 
> > > https://www.qubes-os.org/doc/templates/
> > > 
> > > - -- 
> > > Andrew David Wong (Axon)
> > > Community Manager, Qubes OS
> > > https://www.qubes-os.org
> > > -BEGIN PGP SIGNATURE-
> > > 
> > > iQIcBAEBCgAGBQJYoWLcAAoJENtN07w5UDAwAoQQAM+eiQ77VRPjYIf/0pKepUh0
> > > eMpVANLYuKUC1yOnkyQR4p+eZBY1aRxLenC1y5pZXfk0ZFySKATa+lw2gZR0A6dn
> > > oMzZVtMxqDpVs3SQOImFvGEJCrhmaro1NmyL7+xNTgbEIO7Q35Az+AMLT3nNUa5N
> > > qclPsdCi48MWki4YhCMOaNLxxeFYlJoN1JMdqVg9wWKfPWWL7t15koO0gB2hWAj0
> > > izroJeb9jDOW73PCo13zIs3nBrgmUnP/1VTg7emipVTfeQabHbpads61dNNSCgfv
> > > TEQfXI8+b4TX1ajN5mT90sX5N11OOY0rePRHhhSlRlGMNM+2P6rxjMPvXTrxkF1q
> > > 6TX12i2f2MxKg0uY7wJj2bCqG20Mo9sIsbxybvtFXKphnHZYOGaRmasdw4QciW/m
> > > 1Ojy9dFUdLlqRSsbJRsk91CE6MwhmCqGQAsJsFd1WKdY6+EyH1cSuNpr+PEt01xl
> > > hY91+ljOpI2/wYAQ+cumRV7JAydeCVv59Qs3k5yeFnpeqPMbPe9hKOnTj6eLyDbb
> > > WCCHJzmJJ0NIqzEvdsaiJnfOy9gTSKVdX4YIOoC5b2wjW4+vqJwqPUssSC511zpa
> > > OxEmKTSN7raMuuNLG370oplr5pRnrA/iolg/W/tDM2TbyfGQuEOHZXh91C6vyKKv
> > > mFM7z+UCGxMljbNCEuDN
> > > =laqs
> > > -END PGP SIGNATURE-
> > 
> 
> Please don't top post.
> 
> If the new proxyVM is upstream from the browsing machine then you will
> need to adjust iptables in the nat table to redirect dns requests to the
> dnssec-trigger listener.
> 
> If the new proxy is not upstream, but connected to the same upstream
> proxy then you can set the ip address in /etc/resolv.conf in the
> browsing qube, and allow traffic between the qubes as shown in this
> page:
> www.qubes-os.org/doc/firewall  in the section "Enabling networking
> between two qubes"
> You could set the dns record from /rw/config/rc.local.

For me it will be the first case.

So to do it right, I will need to:

In the Browsing VM (10.137.4.16):

- DNS resolver to the IP of the ProxyVM
- VM settings: NetVM to ProxyVM

In the ProxyVM (10.137.2.13): 

- VM settings: NetVM to sys-firewall
- DNS resolver to 127.0.0.1  (already done)
- New iptables NAT rules to forward all DNS request from the BrowsingVM to the 
local DNS listener

Is it right  ?
Thx


  

-- 
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/d4cdac77-bcd7-4bad-8a96-f15bc3bcf5cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Issues with Standalone VM and screen being

2017-02-13 Thread adonis28850
Hi guys,

I've just created an standalone Linux VM. It install fine, but when I start the 
first time, the screen is out of place, the image below shows it better:


https://i.imgsafe.org/f6ff22e0b3.jpg

Any suggestion? I'm not even able to launch a terminal to try and modify config 
files!

-- 
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/dc0e4ec2-3a7f-4312-8cf5-40d4ac4c84c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - HP-Pavilion Desktop PC - 560-p057ng

2017-02-13 Thread Andre

Hi,

the mainboard supports TPM.
All kind of templates work, networking works, tor-networking works, 
package installers work on every distro.  Windows7 VM installation 
sourced from --cdrom=/dev/cdrom stalls within second Microsoft screen.


Thanks a lot for this great distro, cool work !
Andre

--
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/ce902f65-584a-3368-ca1b-1c3d88a1178d%40juntermanns.net.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-HP-HP_Pavilion_Desktop_560_p0xx-20170213-212325.yml
Description: application/yaml


[qubes-users] Yubikey init failed PCSCD

2017-02-13 Thread Robin Lambertz

Hello,

I'm trying to make my Yubikey Neo (a PGP smartcard) accessible to my GPG 
Qube in a split-gpg + sys-usb setup. When attaching the Yubikey to the 
GPG VM, however, PCSCD doesn't seem to detect my Yubikey (which leads it 
to being unusable with gpg). I tried both an up-to-date archlinux and 
the default fedora-23 templates, and in both cases the yubikey neo 
doesn't show up in `pcsc_scan`.


I started pcscd with `sudo LIBCCID_ifdLogLevel=0x000F pcscd --foreground 
--debug --apdu --color | tee log.txt` to get more info. The logs are 
attached, but the interesting bits are here :


```
0206 ccid_usb.c:621:OpenUSBByName() Found Vendor/Product: 1050/0111 
(Yubico Yubikey NEO OTP+CCID)

0012 ccid_usb.c:623:OpenUSBByName() Using USB bus/device: 2/4
0010 ccid_usb.c:680:OpenUSBByName() bNumDataRatesSupported is 0
1997 ccid_usb.c:1244:InterruptRead() before (0)
00103904 ccid_usb.c:1290:InterruptRead() after (0) (2)
0072 -> 00 65 00 00 00 00 00 00 00 00 00
2614 <- 00 81 00 00 00 00 00 00 00 00 00
0050 -> 00 65 00 00 00 00 00 01 00 00 00
00103063 ccid_usb.c:836:ReadUSB() read failed (2/4): -7 LIBUSB_ERROR_TIMEOUT
0224 -> 00 65 00 00 00 00 00 02 00 00 00
05002241 ccid_usb.c:797:WriteUSB() write failed (2/4): -7 
LIBUSB_ERROR_TIMEOUT

0242 ifdhandler.c:188:CreateChannelByNameOrChannel() failed
0159 ccid_usb.c:879:CloseUSB() Closing USB device: 2/4
0151 ccid_usb.c:889:CloseUSB() Last slot closed. Release resources
0240 ccid_usb.c:189:close_libusb_if_needed() libusb_exit
0476 readerfactory.c:1110:RFInitializeReader() Open Port 0x20 
Failed (usb:1050/0111:libudev:1:/dev/bus/usb/002/004)
0161 readerfactory.c:375:RFAddReader() Yubico Yubikey NEO OTP+CCID 
init failed.

```

When attaching the yubikey to the VM, ReadUSB returns immediately with 
the TIMEOUT error (isn't that weird ?), while the WriteUSB times out 
after 5 seconds. I'm wondering if it was possible the Qubes USB proxy 
could cause those timeouts ? Anyone knows what else could cause those 
errors ?


Thank you for your time :)

Robin Lambertz

--
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/o7tt6k%24v4i%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.
 debuglog.c:289:DebugLogSetLevel() debug level=debug
0275 debuglog.c:310:DebugLogSetCategory() Debug options: APDU
0029 pcscdaemon.c:351:main() Force colored logs
0428 configfile.l:282:DBGetReaderListDir() Parsing conf directory: 
/etc/reader.conf.d
0063 configfile.l:319:DBGetReaderListDir() Skipping non regular 
file: ..
0014 configfile.l:319:DBGetReaderListDir() Skipping non regular 
file: .
0013 configfile.l:358:DBGetReaderList() Parsing conf file: 
/etc/reader.conf.d/libccidtwin
0201 pcscdaemon.c:655:main() pcsc-lite 1.8.20 daemon 
ready.
6163 hotplug_libudev.c:294:get_driver() Looking for a driver for 
VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
0661 hotplug_libudev.c:294:get_driver() Looking for a driver for 
VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001
13709193 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB 
Device add
0196 hotplug_libudev.c:294:get_driver() Looking for a driver for 
VID: 0x1050, PID: 0x0111, path: /dev/bus/usb/002/004
0014 hotplug_libudev.c:433:HPAddDevice() Adding USB device: 
Yubico Yubikey NEO OTP+CCID
0060 readerfactory.c:1079:RFInitializeReader() Attempting 
startup of Yubico Yubikey NEO OTP+CCID 00 00 using 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
00049489 readerfactory.c:954:RFBindFunctions() Loading IFD 
Handler 3.0
0115 ifdhandler.c:1953:init_driver() Driver version: 
1.4.25
0818 ifdhandler.c:1970:init_driver() LogLevel: 0x0003
0033 ifdhandler.c:1981:init_driver() DriverOptions: 0x
0164 ifdhandler.c:1994:init_driver() LogLevel from 
LIBCCID_ifdLogLevel: 0x000F
0011 ifdhandler.c:110:CreateChannelByNameOrChannel() Lun: 0, 
device: usb:1050/0111:libudev:0:/dev/bus/usb/002/004
0009 ccid_usb.c:237:OpenUSBByName() Reader index: 0, Device: 
usb:1050/0111:libudev:0:/dev/bus/usb/002/004
0030 ccid_usb.c:269:OpenUSBByName() interface_number: 0
0042 ccid_usb.c:270:OpenUSBByName() usb bus/device: 2/4
0035 ccid_usb.c:287:OpenUSBByName() Using: 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist

Re: [qubes-users] Re: How to setup NetVM based on fedora-24-minimal template to allow updates?

2017-02-13 Thread Dominique St-Pierre Boucher
Got it!!!

The package qubes-template-minimal-stub prevent the install of tinyproxy.

In order to do that, you have to install with the full package name:

sudo dnf install tinyproxy.x86_64

I don't know if you have to do something else but it worked for me!!!

Dominique!

On Monday, February 13, 2017 at 9:04:17 PM UTC-5, Dominique St-Pierre Boucher 
wrote:
> What do you mean, forcing install by version number?
> 
> I looked into the difference between the minimal and the full version of the 
> template... Missing the tinyproxy.conf file and missing 2 lines in the 
> iptables:
> -A PR-QBS-SERVICES -d 10.137.1.254/32 -i vif+ -p tcp -m tcp --dport 8082 -j 
> REDIRECT
> -A INPUT -i vif+ -p tcp -m tcp --dport 8082 -j ACCEPT
> 
> Did I missed a step somewhere?
> 
> Thanks Dominique
> On Monday, February 13, 2017 at 6:41:55 PM UTC-5, Unman wrote:
> > On Mon, Feb 13, 2017 at 10:59:14PM +, Unman wrote:
> > > On Mon, Feb 13, 2017 at 12:00:40PM -0800, Dominique St-Pierre Boucher 
> > > wrote:
> > > > Hello,
> > > > 
> > > > I have the exact same issue!!! Tinyproxy does not seems to work 
> > > > correctly and I never worked with TinyProxy before.
> > > > 
> > > > Please Help
> > > > 
> > > > Thanks
> > > > 
> > > > Dominique
> > > > 
> > > > On Monday, February 6, 2017 at 8:22:40 AM UTC-5, CF wrote:
> > > > > Hello,
> > > > > 
> > > > > I am running Qubes 3.2 on a laptop smoothly for some days. Following 
> > > > > https://www.qubes-os.org/doc/templates/fedora-minimal/, I wanted to 
> > > > > replace default NetVM (sys-net) and ProxyVM (sys-forewall) based on 
> > > > > Fedora-24 by new ones based on Fedora-24-minimal.
> > > > > 
> > > > > Default minimal template works perfectly as a ProxyVM. Cloned 
> > > > > template 
> > > > > with network device firmware and recommended packages effectively 
> > > > > provide an internet connection but does not allow updates of 
> > > > > TemplateVMs.
> > > > > 
> > > > > As a workaround, it is possible to update those TemplateVMs using 
> > > > > sys-whonix as NetVM. Another workaround is to use the default netVM 
> > > > > based on fedora-23 while keeping the default fedora-24-minimal as 
> > > > > firewall.
> > > > > 
> > > > > Any idea on how to setup the new NetVM to allow those updates without 
> > > > > those workarounds?
> > > > > 
> > > > > Thanks
> > > > 
> > > 
> > > If I remember the qubes-stub package stops straightforward installation
> > > of many of the netvm packages. I assume you worked around this issue.
> > > 
> > > The obvious places to look are:
> > > "iptables -L -nv" to ensure that you have an INPUT rule allowing traffic
> > > to the tinyproxy.
> > > And "systemctl status qubes-updates-proxy" to see what the status of
> > > tinyproxy is.
> > > 
> > > Look at those outputs and you may be able to see the problem.
> > > 
> > > unman
> > 
> > I've just run through the configuration, forcing installs by using the
> > version number, and it works fine.
> > Don't forget that you have to enable the qubes-update-proxy service:
> > qvm-service  -e  qubes-update-proxy

-- 
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/d4865210-be72-48c8-837c-ab415a2efbb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Windows 7 install doesn't work with 'xen' video setting

2017-02-13 Thread rmflagg
Hi everyone,

   I just finished the install of Windows 7 Ultimate in Qubes 3.2 (R3.2).  The 
only problem is that Windows only works with the custom config that I used for 
the installation with the 'xen' video setting changed to 'cirrus.'

   What could I have done/didn't do?  Anyone else have this problem?

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/e1f6d2ee-7c1f-43a7-803a-684c2c956883%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Ad-blocking ProxyVM?

2017-02-13 Thread Joe Ruether
Ok, I need to simplify this. I need help, I don't know what I am missing. Is 
anyone able to recreate the following netcat test?

I cannot seem to get the DNAT portion of the iptables to work at all. Here is a 
very simple test:

On the proxyvm, I use the following rules to redirect port 5353 to localhost, 
and allow the connection:

iptables -t nat -I PR-QBS 1 -d 10.137.4.1 -p tcp --dport 5353 -j DNAT 
--to-destination 127.0.0.1
iptables -I INPUT 1 -p tcp --dport 5353 -j ACCEPT

Then, on the proxyvm, I run the following command to listen on that port (no 
other service is running on that port):

nc -l -p 5353

Finally, on the AppVM, I run the following command:

nc 10.137.4.1 5353

My expectation is that the two netcats will connect, however they don't. What 
do I need to do to get my AppVM to talk to my ProxyVM? 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/c23efb9f-f344-4523-b24d-ed8d7406723e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How to setup NetVM based on fedora-24-minimal template to allow updates?

2017-02-13 Thread Dominique St-Pierre Boucher
What do you mean, forcing install by version number?

I looked into the difference between the minimal and the full version of the 
template... Missing the tinyproxy.conf file and missing 2 lines in the iptables:
-A PR-QBS-SERVICES -d 10.137.1.254/32 -i vif+ -p tcp -m tcp --dport 8082 -j 
REDIRECT
-A INPUT -i vif+ -p tcp -m tcp --dport 8082 -j ACCEPT

Did I missed a step somewhere?

Thanks Dominique
On Monday, February 13, 2017 at 6:41:55 PM UTC-5, Unman wrote:
> On Mon, Feb 13, 2017 at 10:59:14PM +, Unman wrote:
> > On Mon, Feb 13, 2017 at 12:00:40PM -0800, Dominique St-Pierre Boucher wrote:
> > > Hello,
> > > 
> > > I have the exact same issue!!! Tinyproxy does not seems to work correctly 
> > > and I never worked with TinyProxy before.
> > > 
> > > Please Help
> > > 
> > > Thanks
> > > 
> > > Dominique
> > > 
> > > On Monday, February 6, 2017 at 8:22:40 AM UTC-5, CF wrote:
> > > > Hello,
> > > > 
> > > > I am running Qubes 3.2 on a laptop smoothly for some days. Following 
> > > > https://www.qubes-os.org/doc/templates/fedora-minimal/, I wanted to 
> > > > replace default NetVM (sys-net) and ProxyVM (sys-forewall) based on 
> > > > Fedora-24 by new ones based on Fedora-24-minimal.
> > > > 
> > > > Default minimal template works perfectly as a ProxyVM. Cloned template 
> > > > with network device firmware and recommended packages effectively 
> > > > provide an internet connection but does not allow updates of 
> > > > TemplateVMs.
> > > > 
> > > > As a workaround, it is possible to update those TemplateVMs using 
> > > > sys-whonix as NetVM. Another workaround is to use the default netVM 
> > > > based on fedora-23 while keeping the default fedora-24-minimal as 
> > > > firewall.
> > > > 
> > > > Any idea on how to setup the new NetVM to allow those updates without 
> > > > those workarounds?
> > > > 
> > > > Thanks
> > > 
> > 
> > If I remember the qubes-stub package stops straightforward installation
> > of many of the netvm packages. I assume you worked around this issue.
> > 
> > The obvious places to look are:
> > "iptables -L -nv" to ensure that you have an INPUT rule allowing traffic
> > to the tinyproxy.
> > And "systemctl status qubes-updates-proxy" to see what the status of
> > tinyproxy is.
> > 
> > Look at those outputs and you may be able to see the problem.
> > 
> > unman
> 
> I've just run through the configuration, forcing installs by using the
> version number, and it works fine.
> Don't forget that you have to enable the qubes-update-proxy service:
> qvm-service  -e  qubes-update-proxy

-- 
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/05139270-7128-4ab5-9752-a54fa3bc7f80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] trying to remove old template but getting error

2017-02-13 Thread Unman
On Mon, Feb 13, 2017 at 04:53:24PM -0800, Gaiko wrote:
> I installed the fedora24 template using
> 
> sudo qubes-dom0-update qubes-template-fedora-24
> 
> Then changed all put then went to global settings, changed the default 
> template, then went into the vm manager and changed the default template for 
> each of the VMs (its a fresh install so there was jsut vault, personal, 
> untrusted, and work) but not the sys-net, sys-firewall, as it had it in my 
> head that was a done deal via global settings.
> 
> Anyway, then ran
> 
> qvm-create-default-dvm --default-template
> 
> then
> 
> sudo dnf remove qubes-template-fedora-23
> 
> but with the last command I got an error:
> no match for argument: qubes-template-fedora-23
> Error:no packages marked for removal.
> 
> I then looked for other posts and found this 
> (https://groups.google.com/forum/#!searchin/qubes-users/no$20match$20for$20argument$3A$20qubes-template-fedora-23$20Error$3Ano$20packages$20marked$20for$20removal.%7Csort:relevance/qubes-users/v7Svq_KS5us/Xej8hMQICAAJ)
>  but there he had mod'd the qubes.xml file and in that file on my comp I 
> noticed there was not an entry for fedora-24 so I was hesitant to go any 
> further.
> 
> So, fedora-23 template files are still in  /var/lib/vm-templates/fedora-23
> and fedora-23 is still showing up in the VM Manager (indicating it needs 
> updates no less). Fedora 24 is also showing up in the VM Manager, and 
> everything *seems* ok with it except it wasn't in the qubes.xml file which i 
> wasn't sure about... 
> 
> Thoughts?
> 

Try 'sudo dnf list installed |grep template'
to check the status with dnf.

Also try qvm-remove qubes-template-fedora-23

-- 
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/20170214010641.GD27086%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Install DNSSEC on ProxyVM type (debian) ?

2017-02-13 Thread Unman
On Mon, Feb 13, 2017 at 05:10:28AM -0800, ThierryIT wrote:
> Hi,
> 
> Thx a lot for these information.
> 
> I  have installed dnssec-trigger on a newly created VM from a debian template 
> as ProxyVM type. This is working, I  have checked for the DNSSEC and all are 
> ok.
> 
> In the same way, I do have a VM to browse on internet,  and  I want all DNS 
> request forwarded to this ProxyVM  freshly installed  ... How to do  this ??
> 
> Thx
> 
> Le lundi 13 février 2017 09:40:42 UTC+2, Andrew David Wong a écrit :
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > On 2017-02-12 23:18, ThierryIT wrote:
> > > Hi,
> > > 
> > > I think that I have missed something concerning Qubes. When I
> > > installed, let's say "Unbound" packages, after a reboot of the VM
> > > it disappear ... Normal ?
> > > 
> > > Thx
> > > 
> > 
> > You have to install it in the TemplateVM (or, for more advanced users,
> > pick a persistent dir and/or use bind-dirs):
> > 
> > https://www.qubes-os.org/doc/templates/
> > 
> > - -- 
> > Andrew David Wong (Axon)
> > Community Manager, Qubes OS
> > https://www.qubes-os.org
> > -BEGIN PGP SIGNATURE-
> > 
> > iQIcBAEBCgAGBQJYoWLcAAoJENtN07w5UDAwAoQQAM+eiQ77VRPjYIf/0pKepUh0
> > eMpVANLYuKUC1yOnkyQR4p+eZBY1aRxLenC1y5pZXfk0ZFySKATa+lw2gZR0A6dn
> > oMzZVtMxqDpVs3SQOImFvGEJCrhmaro1NmyL7+xNTgbEIO7Q35Az+AMLT3nNUa5N
> > qclPsdCi48MWki4YhCMOaNLxxeFYlJoN1JMdqVg9wWKfPWWL7t15koO0gB2hWAj0
> > izroJeb9jDOW73PCo13zIs3nBrgmUnP/1VTg7emipVTfeQabHbpads61dNNSCgfv
> > TEQfXI8+b4TX1ajN5mT90sX5N11OOY0rePRHhhSlRlGMNM+2P6rxjMPvXTrxkF1q
> > 6TX12i2f2MxKg0uY7wJj2bCqG20Mo9sIsbxybvtFXKphnHZYOGaRmasdw4QciW/m
> > 1Ojy9dFUdLlqRSsbJRsk91CE6MwhmCqGQAsJsFd1WKdY6+EyH1cSuNpr+PEt01xl
> > hY91+ljOpI2/wYAQ+cumRV7JAydeCVv59Qs3k5yeFnpeqPMbPe9hKOnTj6eLyDbb
> > WCCHJzmJJ0NIqzEvdsaiJnfOy9gTSKVdX4YIOoC5b2wjW4+vqJwqPUssSC511zpa
> > OxEmKTSN7raMuuNLG370oplr5pRnrA/iolg/W/tDM2TbyfGQuEOHZXh91C6vyKKv
> > mFM7z+UCGxMljbNCEuDN
> > =laqs
> > -END PGP SIGNATURE-
> 

Please don't top post.

If the new proxyVM is upstream from the browsing machine then you will
need to adjust iptables in the nat table to redirect dns requests to the
dnssec-trigger listener.

If the new proxy is not upstream, but connected to the same upstream
proxy then you can set the ip address in /etc/resolv.conf in the
browsing qube, and allow traffic between the qubes as shown in this
page:
www.qubes-os.org/doc/firewall  in the section "Enabling networking
between two qubes"
You could set the dns record from /rw/config/rc.local.




-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20170214005727.GB27086%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] trying to remove old template but getting error

2017-02-13 Thread Gaiko
I installed the fedora24 template using

sudo qubes-dom0-update qubes-template-fedora-24

Then changed all put then went to global settings, changed the default 
template, then went into the vm manager and changed the default template for 
each of the VMs (its a fresh install so there was jsut vault, personal, 
untrusted, and work) but not the sys-net, sys-firewall, as it had it in my head 
that was a done deal via global settings.

Anyway, then ran

qvm-create-default-dvm --default-template

then

sudo dnf remove qubes-template-fedora-23

but with the last command I got an error:
no match for argument: qubes-template-fedora-23
Error:no packages marked for removal.

I then looked for other posts and found this 
(https://groups.google.com/forum/#!searchin/qubes-users/no$20match$20for$20argument$3A$20qubes-template-fedora-23$20Error$3Ano$20packages$20marked$20for$20removal.%7Csort:relevance/qubes-users/v7Svq_KS5us/Xej8hMQICAAJ)
 but there he had mod'd the qubes.xml file and in that file on my comp I 
noticed there was not an entry for fedora-24 so I was hesitant to go any 
further.

So, fedora-23 template files are still in  /var/lib/vm-templates/fedora-23
and fedora-23 is still showing up in the VM Manager (indicating it needs 
updates no less). Fedora 24 is also showing up in the VM Manager, and 
everything *seems* ok with it except it wasn't in the qubes.xml file which i 
wasn't sure about... 

Thoughts?

-- 
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/19d13fbe-0435-4d44-841f-94cd352128bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Wallpaper-changer like variety?

2017-02-13 Thread Gaiko Kyofusho
On Monday, February 13, 2017 at 11:00:46 AM UTC-5, Niels Kobschätzki wrote:
> Hi,
> 
> when I am not using Qubes I like using a wallpaper-changer like variety
> (http://peterlevi.com/variety/).
> What would be the best way to use something like that in Qubes? 
> When I think about it, the best way would be to copy interesting
> wallpapers into the dom0 and then run a shell-script with a
> cronjob/systemd-timer to change it automatically.
> 
> Any other ideas? Or do you see problems with that approach?
> 
> 
> Niels

You probably don't need to bother with cronjobs etc. If you have pix (that you 
trust) you can put them in dom0 then use "Desktop" (System tools > Desktop) in 
XFCE and it has an option to "change background" and gives interval options 
(min/hours/chon/etc) and supports multiple monitors as well (so you could have 
2 diff wallpapers on two different monitors at the same time).

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/985a5c0b-966c-4d29-a4de-4da45d17be38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How to setup NetVM based on fedora-24-minimal template to allow updates?

2017-02-13 Thread Unman
On Mon, Feb 13, 2017 at 10:59:14PM +, Unman wrote:
> On Mon, Feb 13, 2017 at 12:00:40PM -0800, Dominique St-Pierre Boucher wrote:
> > Hello,
> > 
> > I have the exact same issue!!! Tinyproxy does not seems to work correctly 
> > and I never worked with TinyProxy before.
> > 
> > Please Help
> > 
> > Thanks
> > 
> > Dominique
> > 
> > On Monday, February 6, 2017 at 8:22:40 AM UTC-5, CF wrote:
> > > Hello,
> > > 
> > > I am running Qubes 3.2 on a laptop smoothly for some days. Following 
> > > https://www.qubes-os.org/doc/templates/fedora-minimal/, I wanted to 
> > > replace default NetVM (sys-net) and ProxyVM (sys-forewall) based on 
> > > Fedora-24 by new ones based on Fedora-24-minimal.
> > > 
> > > Default minimal template works perfectly as a ProxyVM. Cloned template 
> > > with network device firmware and recommended packages effectively 
> > > provide an internet connection but does not allow updates of TemplateVMs.
> > > 
> > > As a workaround, it is possible to update those TemplateVMs using 
> > > sys-whonix as NetVM. Another workaround is to use the default netVM 
> > > based on fedora-23 while keeping the default fedora-24-minimal as 
> > > firewall.
> > > 
> > > Any idea on how to setup the new NetVM to allow those updates without 
> > > those workarounds?
> > > 
> > > Thanks
> > 
> 
> If I remember the qubes-stub package stops straightforward installation
> of many of the netvm packages. I assume you worked around this issue.
> 
> The obvious places to look are:
> "iptables -L -nv" to ensure that you have an INPUT rule allowing traffic
> to the tinyproxy.
> And "systemctl status qubes-updates-proxy" to see what the status of
> tinyproxy is.
> 
> Look at those outputs and you may be able to see the problem.
> 
> unman

I've just run through the configuration, forcing installs by using the
version number, and it works fine.
Don't forget that you have to enable the qubes-update-proxy service:
qvm-service  -e  qubes-update-proxy

-- 
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/20170213234153.GB26318%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: How to setup NetVM based on fedora-24-minimal template to allow updates?

2017-02-13 Thread Unman
On Mon, Feb 13, 2017 at 12:00:40PM -0800, Dominique St-Pierre Boucher wrote:
> Hello,
> 
> I have the exact same issue!!! Tinyproxy does not seems to work correctly and 
> I never worked with TinyProxy before.
> 
> Please Help
> 
> Thanks
> 
> Dominique
> 
> On Monday, February 6, 2017 at 8:22:40 AM UTC-5, CF wrote:
> > Hello,
> > 
> > I am running Qubes 3.2 on a laptop smoothly for some days. Following 
> > https://www.qubes-os.org/doc/templates/fedora-minimal/, I wanted to 
> > replace default NetVM (sys-net) and ProxyVM (sys-forewall) based on 
> > Fedora-24 by new ones based on Fedora-24-minimal.
> > 
> > Default minimal template works perfectly as a ProxyVM. Cloned template 
> > with network device firmware and recommended packages effectively 
> > provide an internet connection but does not allow updates of TemplateVMs.
> > 
> > As a workaround, it is possible to update those TemplateVMs using 
> > sys-whonix as NetVM. Another workaround is to use the default netVM 
> > based on fedora-23 while keeping the default fedora-24-minimal as firewall.
> > 
> > Any idea on how to setup the new NetVM to allow those updates without 
> > those workarounds?
> > 
> > Thanks
> 

If I remember the qubes-stub package stops straightforward installation
of many of the netvm packages. I assume you worked around this issue.

The obvious places to look are:
"iptables -L -nv" to ensure that you have an INPUT rule allowing traffic
to the tinyproxy.
And "systemctl status qubes-updates-proxy" to see what the status of
tinyproxy is.

Look at those outputs and you may be able to see the problem.

unman

-- 
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/20170213225914.GA26318%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: How to setup NetVM based on fedora-24-minimal template to allow updates?

2017-02-13 Thread Dominique St-Pierre Boucher
Hello,

I have the exact same issue!!! Tinyproxy does not seems to work correctly and I 
never worked with TinyProxy before.

Please Help

Thanks

Dominique

On Monday, February 6, 2017 at 8:22:40 AM UTC-5, CF wrote:
> Hello,
> 
> I am running Qubes 3.2 on a laptop smoothly for some days. Following 
> https://www.qubes-os.org/doc/templates/fedora-minimal/, I wanted to 
> replace default NetVM (sys-net) and ProxyVM (sys-forewall) based on 
> Fedora-24 by new ones based on Fedora-24-minimal.
> 
> Default minimal template works perfectly as a ProxyVM. Cloned template 
> with network device firmware and recommended packages effectively 
> provide an internet connection but does not allow updates of TemplateVMs.
> 
> As a workaround, it is possible to update those TemplateVMs using 
> sys-whonix as NetVM. Another workaround is to use the default netVM 
> based on fedora-23 while keeping the default fedora-24-minimal as firewall.
> 
> Any idea on how to setup the new NetVM to allow those updates without 
> those workarounds?
> 
> 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/6d576bb3-a1ad-423d-b340-80ea9036b849%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Installation Media Self-Check Confusion

2017-02-13 Thread bf1894986
On Monday, February 13, 2017 at 1:07:44 PM UTC-6, raah...@gmail.com wrote:
> On Sunday, February 12, 2017 at 7:33:43 PM UTC-5, bf18...@gmail.com wrote:
> > Hello,
> > 
> > I have been trying to install R3.2 and even though I have tried burning 
> > both usbs and dvds and using different burning programs (including just dd 
> > for the usb) it always results in it saying that the .iso is unsupported 
> > and the install media is fragmented (20 count with a md5 sum(I can include 
> > that if it helps)). The weird part though is that it says it before the 
> > media check starts and if I let it finish the check it say's that it passed 
> > and will continue to the graphical interface. I also verified it before 
> > burning and the files were (reasonably) trust-able. Does anyone have any 
> > advice on if it can be trusted in general or have had this happen before?
> > 
> > Thanks in-advance for even glancing
> 
> what happens when it goes to the graphicsal interface?
> 
> have you tried it on diff ports, diff pc?
> 
> what mobo? how exactly are you verifying it?

When it goes to the interface everything seems exactly the same as it used to 
for anaconda (I have used qubes before in some of its earlier forms and release 
candidates). It even runs a standard install but I'm not sure why it would 
continue when it usually refuses if anything faults.

I've tried two pc's, one using windows and one using deb. 

I've verified with gpg4win and reg gpg with sha251 checks. Mobo is intel 
celeron.

-- 
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/750faeb7-2617-489c-834a-3705b6432a6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Installation Media Self-Check Confusion

2017-02-13 Thread raahelps
On Sunday, February 12, 2017 at 7:33:43 PM UTC-5, bf18...@gmail.com wrote:
> Hello,
> 
> I have been trying to install R3.2 and even though I have tried burning both 
> usbs and dvds and using different burning programs (including just dd for the 
> usb) it always results in it saying that the .iso is unsupported and the 
> install media is fragmented (20 count with a md5 sum(I can include that if it 
> helps)). The weird part though is that it says it before the media check 
> starts and if I let it finish the check it say's that it passed and will 
> continue to the graphical interface. I also verified it before burning and 
> the files were (reasonably) trust-able. Does anyone have any advice on if it 
> can be trusted in general or have had this happen before?
> 
> Thanks in-advance for even glancing

what happens when it goes to the graphicsal interface?

have you tried it on diff ports, diff pc?

what mobo? how exactly are you verifying 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/fcb8ea95-9568-4174-a83e-899c693ecb87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Wallpaper-changer like variety?

2017-02-13 Thread Niels Kobschätzki

Hi,

when I am not using Qubes I like using a wallpaper-changer like variety
(http://peterlevi.com/variety/).
What would be the best way to use something like that in Qubes? 
When I think about it, the best way would be to copy interesting

wallpapers into the dom0 and then run a shell-script with a
cronjob/systemd-timer to change it automatically.

Any other ideas? Or do you see problems with that approach?


Niels

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


Re: [qubes-users] windows7 hangs on installation

2017-02-13 Thread Ted Brenner
Thanks! That did it. I wonder if this should be added to the guide? Or is
this uncommon enough that we should just let folks find it on github if
they happen to run into it?

On Sat, Feb 11, 2017 at 9:38 PM, '01v3g4n10' via qubes-users <
qubes-users@googlegroups.com> wrote:

> On Sunday, February 12, 2017 at 2:33:53 AM UTC, griz...@gmail.com wrote:
> > On Friday, October 28, 2016 at 1:36:56 PM UTC-5, scheu...@googlemail.com
> wrote:
> > > Thanks for your answer.
> > > I wait about 6 hours but nothing happens.
> > > Of course you´re right. I just installed the QWT to dom0.
> >
> > Did you figure this out? I'm seeing this same problem now.
>
> These instructions worked for me.
> https://github.com/QubesOS/qubes-issues/issues/2488
>
> --
> 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/85b957aa-bf42-4283-a450-47dd151a6c09%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sent from my Desktop

-- 
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/CANKZutyHLRnCUw3%2BeizyjM0d5CgK1T0KKjk%2BpCebv_dh01pgNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Define an environment variable to be accessible by qvm-sync-appmenus

2017-02-13 Thread marc
Hi,

I'm working in a small pull request to Qubes which modifies 
`/etc/qubes-rpc/qubes.GetAppmenus` to, optionally, read something from an 
environment variable. 

The issue is that, while manually testing it, I find no way to set an 
environment variable from my VM making it accessible when `qvm-sync-appmenus` 
is run. No matter in which shell initialization file I set it, it isn't read.

Where should I set that environment variable to make sure that scripts like 
`qvm-sync-appmenus` will load it?

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/2f627353-e318-4432-b4d9-a93f91e86d86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-13 Thread marc
> I'm probably wrong but I think what's happening is this:
> Look up the process list and you'll see the invocation:
> su -l user -c /usr/bin/xinit...

Right

> That's su starting a shell as a login shell: as you have zsh as default
> shell, .zprofile is read to set env variables, including path.
> 
> And I think you should have seen the output from qvm-run ps aux
> included something like "sh -c ps aux".

Right

> That call to sh is coming from qrexec-fork-server, I think.
> 
> I hope that makes it a little clearer.

Not too much, but I guess I lack some background in qubes internals :)

> It would be interesting to see what happened if you were to relink sh
> to zsh in the template. I'm looking at a number of issues arising using
> some non default user shells(tcsh, fish)

Doing so:

$ qvm-run -a -p qube "echo $0"
# => sh

$ qvm-run -a -p qube "ps aux"
# Inclues
# => /bin/bash /usr/bin/qubes-session
# => su -l user -c /usr/bin/xinit
# => ps aux (without `sh -c` before)

$ qvm-run -a -p qube 'echo $SHELL'
# => /bin/zsh

-- 
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/e281e3ca-d595-40ae-a5c7-e471346179dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Install DNSSEC on ProxyVM type (debian) ?

2017-02-13 Thread ThierryIT
Hi,

Thx a lot for these information.

I  have installed dnssec-trigger on a newly created VM from a debian template 
as ProxyVM type. This is working, I  have checked for the DNSSEC and all are ok.

In the same way, I do have a VM to browse on internet,  and  I want all DNS 
request forwarded to this ProxyVM  freshly installed  ... How to do  this ??

Thx

Le lundi 13 février 2017 09:40:42 UTC+2, Andrew David Wong a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-02-12 23:18, ThierryIT wrote:
> > Hi,
> > 
> > I think that I have missed something concerning Qubes. When I
> > installed, let's say "Unbound" packages, after a reboot of the VM
> > it disappear ... Normal ?
> > 
> > Thx
> > 
> 
> You have to install it in the TemplateVM (or, for more advanced users,
> pick a persistent dir and/or use bind-dirs):
> 
> https://www.qubes-os.org/doc/templates/
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYoWLcAAoJENtN07w5UDAwAoQQAM+eiQ77VRPjYIf/0pKepUh0
> eMpVANLYuKUC1yOnkyQR4p+eZBY1aRxLenC1y5pZXfk0ZFySKATa+lw2gZR0A6dn
> oMzZVtMxqDpVs3SQOImFvGEJCrhmaro1NmyL7+xNTgbEIO7Q35Az+AMLT3nNUa5N
> qclPsdCi48MWki4YhCMOaNLxxeFYlJoN1JMdqVg9wWKfPWWL7t15koO0gB2hWAj0
> izroJeb9jDOW73PCo13zIs3nBrgmUnP/1VTg7emipVTfeQabHbpads61dNNSCgfv
> TEQfXI8+b4TX1ajN5mT90sX5N11OOY0rePRHhhSlRlGMNM+2P6rxjMPvXTrxkF1q
> 6TX12i2f2MxKg0uY7wJj2bCqG20Mo9sIsbxybvtFXKphnHZYOGaRmasdw4QciW/m
> 1Ojy9dFUdLlqRSsbJRsk91CE6MwhmCqGQAsJsFd1WKdY6+EyH1cSuNpr+PEt01xl
> hY91+ljOpI2/wYAQ+cumRV7JAydeCVv59Qs3k5yeFnpeqPMbPe9hKOnTj6eLyDbb
> WCCHJzmJJ0NIqzEvdsaiJnfOy9gTSKVdX4YIOoC5b2wjW4+vqJwqPUssSC511zpa
> OxEmKTSN7raMuuNLG370oplr5pRnrA/iolg/W/tDM2TbyfGQuEOHZXh91C6vyKKv
> mFM7z+UCGxMljbNCEuDN
> =laqs
> -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/1f60d7a6-e536-49ce-9c87-85b9913b6834%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] DisplayPort problems

2017-02-13 Thread Others call me jean
Hi community

Yesterday I installed Qubes OS and it works fine. Thank you guys!

But I could not solve one problem yet. Here my configuration:

- Lenovo T460s, NVMe SSD, i7-6600U
- Qubes OS 3.2
- 4.8.12-12.pvops.qubes.x86_64
- ThinkPad Ultra Dock (Docking Station)
- 2x Dell U2415b with DP to Docking Station

Before I installed Qubes, I used Arch Linux with GNOME. The Displays
normally works, even when I dock/undock from my docking station.

Now, the Qubes OS freeze/crash, when I plug in the display direct or
dock/undock from the docking station with DisplayPort. This is really
annoying!

With HDMI this problem does not exist. But unfortunately I have only 1
HDMI connection on my docking station (I don't know why, because with
daisy chaining you could use multiple display with only 1 DP port!).

Do you know a possible solution for DisplayPort support?

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/o7s893%24k7h%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Cant start the AppVM - uninstalled python-numpy.

2017-02-13 Thread Keld Norman
I got the appvm on-line - found the .deb packages here 
http://ftp.qubes-os.org/repo/deb/r3.1/vm/pool/main/q/ and ran wget  to 
downloaded them - then dpkg -i .deb and now it is all good agin :) 

Thanks for the response 

-- 
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/3f437eba-65ea-4bc2-97f0-a81b29d7ba81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Cant start the AppVM - uninstalled python-numpy.

2017-02-13 Thread john.david.r.smith

On 13/02/17 01:31, Keld Norman wrote:

Hi community :)

I ran this on a standalone debian 8 appvm
apt-get purge python-numpy

Yes, I now know that is not the most cleaver command to run..

It resulted in the following packages got removed:
python-numpy python-qwt4-qt4 qubes-core-agent gimp gpsd-clients 
live-usb-install python-glade2 python-matplotlib qubes-gui-agent w3af 
python-kivy python-gtk2 python-scipy python-pygame

So now I can not boot that AppVM normally..

I can connect to it using: sudo xl console Lab  from dom0's console
and get a prompt (login as root) but I am missing the /rw directory and 
everything seems readonly (I wanted to reinstall the uninstalled packages)

When i try to run apt-get install (all the packages listed above) it just fails with 
"Unable to write to /var/cache/apt" because /var is not there and /rw is also 
not there.. :/

i am not an expert in this, but did you try to `sudo mkdir -p "/var/cache/apt"`?
maybe this allows you to re-install the packages.

--
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/41f62804-a020-4120-88f2-66cb03e89986%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] SOLVED: How to disable xfce login?

2017-02-13 Thread peter . palensky
On Saturday, February 11, 2017 at 7:37:22 PM UTC+1, 01v3g4n10 wrote:
> On Saturday, February 11, 2017 at 3:23:38 PM UTC, peter.p...@gmail.com wrote:
> > I enabled "login at boot" during installation (3.2).
> > How can i disable it again?
> > 
> > Thanks,
> > Peter.
> 
> Make sure that any instances of autologin in /etc/lightdm/lightdm.conf are 
> commmented out with a "#".

Thanks for the pointer. What helped was to UNCOMMENT the following lines:

pam-service=lightdm
pam-autologin-service=lightdm-autologin
autologin-user=
autologin-user-timeout=0

Thank you!
Peter.

-- 
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/70f78f54-0b13-48b7-977d-68adf8ab0770%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Install Qubes on external SSD? Photo edition tools?

2017-02-13 Thread '0xDEADBEEF00' via qubes-users
Hi,

I use digiKam, Darktable and Gimp in my photo workflow on qubes without any 
problem. They are all available both in the fedora-23 and debian-8 templates.

Have a nice day,

0xdeadbeef00



Sent with [ProtonMail](https://protonmail.com) Secure Email.


 Original Message 
Subject: [qubes-users] Install Qubes on external SSD? Photo edition tools?
Local Time: February 12, 2017 6:09 PM
UTC Time: February 12, 2017 5:09 PM
From: ingrid.mary.vie...@gmail.com
To: qubes-users 

Hi,
I'm currently using Windows and considering changing OS.
I would like to try Qubes, but first on an external device, while keeping 
Windows on my hard drive.
1. Can I install Qubes on an external SSD or should I try Live USB instead?
2. Are there advanced photo edition tools for Qubes? For example, Darktable?
Thanks a lot!!!

--
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/8cf3994b-ffdb-4b3b-8dcb-f55189707d16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/nSTCfU0loA5It_rA07waHRcUNCaYlsJTxTGbNCJf9VX3Aeqa-tcwi6vDL-FI8tiJSf8dSJ8kni9z2DT9tMG3NOQQPN4aBGx90guYzWMDxTc%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Install Qubes on external SSD? Photo edition tools?

2017-02-13 Thread 'Peter T Garner' via qubes-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



On Sun, 12 Feb 2017 09:09:57 -0800 (PST)
ingrid.mary.vie...@gmail.com wrote:

> Hi,
> I'm currently using Windows and considering changing OS.
> I would like to try Qubes, but first on an external device, while
> keeping Windows on my hard drive. 1. Can I install Qubes on an
> external SSD or should I try Live USB instead? 2. Are there advanced
> photo edition tools for Qubes? For example, Darktable? Thanks a lot!!!
> 


I had *major* problems trying to install R3.2 on an external SSD, but I
suspect that some of this was down to my old PC hardware (an HP
XW8400). The main problem was that the SSD was not recognised as a
destination device. 

I eventually bought a 64Gb Sandisk Ultra USB3 stick and it installed
immediately without problems. That was even more surprising as I only
have USB2 ports on the PC. I now have a happy Qubes installation that
I can carry around. Hope that helps.
 


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEZi0TqYJNvNPoJPrGf56/hIEKxXAFAlihaH4ACgkQf56/hIEK
xXDzNgwAtQAl7WNE9mmwFTBeJ2wQAceIG5ppDHmw8NsLyuJzeb0AWfJvJdYpGUJP
zsp2n8a4xK8Wop6ntiNaoAZiNRtBff0ovcmCH+C9OKoI/OVWa41LXgalQcm1bqVJ
WTsWOdRKXxBiiG/YZkFTCmKV9OSTMSx2wx1xUw25icZJrv2AQyc7wZ/asxRea+od
6OFwYjqSebM9D25CEOYisYaDwYSlm6Dy8f1qh86I6zh5wGzueQo7kqCGfYA/+bEE
uGNLbG+Mq8xLNf1v1xWbd0uLFtQCh/P2n1it6zJeZ++9fGheuw7jedw8jMl4FbAo
dvWmcHp8WwhHOAd0PQy5PexAc2hbbVTgZptsepyjHauvNYT0vU1bqodUGb+gM53r
Ay2FIMR9J8l/5HltZNMtThTLwx25x6axWANwMOHUiIiBSObeklQodVWVyrgOK5Mc
Q7QVQktlq9fnU4Dj9Zmgg1hg68dK5vOppaWMj4a+sSudjaPSGPUF7pIbMynEIfpX
SGWT0sce
=ggfU
-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/20170213080412.33e234f0.peter%40petergarner.net.
For more options, visit https://groups.google.com/d/optout.