Re: AW: Re: AW: [qubes-users] Re: i3 under Qubes 4 RC3

2018-02-22 Thread Florian Brandes

On 22.02.2018 22:39, '[799]' via qubes-users wrote:

Hello Florian

 Original-Nachricht 
An 22. Feb. 2018, 09:07, Florian Brandes schrieb:

 > I use i3 under Q4rc4 without any issues
 > or problems.

Would you mind sharing your i3-config files?



Hi,

not at all. config file taken from /home/dom0user/.config/i3/config

The only line I changed from the default setup is:
# start dmenu (a program launcher)
bindsym $mod+d exec --no-startup-id i3-dmenu-desktop --dmenu="dmenu -i -nb #d2d2d2 
-nf #00 -sb #63a0ff"

where I added the "-i" option.

I also added the /usr/bin/qubes-i3status bash script.

I changed

local qubes=$(qvm-ls 2>/dev/null | grep ' \* ' | wc -l)
to
local qubes=$(qvm-ls 2>/dev/null | grep 'Running ' | wc -l)


and
local disk=`df -h / | tail -n 1 | awk '{print $4}'`
to
local disk=`sudo lvs --noheadings -o lv_size,data_percent /dev/mapper/qubes_dom0-pool00 | 
perl -pe 's/\s*([0-9.]+)([a-zA-Z]*)\s+([0-9.]+).*/sprintf("%.1f%s", ($1 * (100 
-$3) \/ 100.0), $2)/e'`

Both are attached.

Regards,

Florian






--
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/7b75712c-3288-90aa-d939-b76efab12197%40gmx.de.
For more options, visit https://groups.google.com/d/optout.
# This file has been auto-generated by i3-config-wizard(1).
# It will not be overwritten, so edit it as you like.
#
# Should you change your keyboard layout some time, delete
# this file and re-run i3-config-wizard(1).
#

# i3 config file (v4)
#
# Please see http://i3wm.org/docs/userguide.html for a complete reference!

set $mod Mod4

# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
# This font is widely installed, provides lots of unicode glyphs, right-to-left
# text rendering and scalability on retina/hidpi displays (thanks to pango).
font pango:DejaVu Sans Mono 8
# Before i3 v4.8, we used to recommend this one as the default:
# font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
# The font above is very space-efficient, that is, it looks good, sharp and
# clear in small sizes. However, its unicode glyph coverage is limited, the old
# X core fonts rendering does not support right-to-left and this being a bitmap
# font, it doesn’t scale on retina/hidpi displays.

client.background   dom0#121212
client.focused  dom0#522702 #522702 #ff #a6907d
client.focused_inactive dom0#522702 #361a01 #ff #a6907d
client.unfocuseddom0#522702 #361a01 #99 #a6907d
client.urgent   dom0#66 #a6907d #ce #a6907d

client.background   red #121212
client.focused  red #e53b27 #e53b27 #ff #f19b90
client.focused_inactive red #e53b27 #902519 #ff #f19b90
client.unfocusedred #e53b27 #902519 #99 #f19b90
client.urgent   red #e53b27 #f19b90 #ce #f19b90

client.background   orange  #121212
client.focused  orange  #d05f03 #d05f03 #ff #daa67e
client.focused_inactive orange  #d05f03 #7b3702 #ff #daa67e
client.unfocusedorange  #d05f03 #7b3702 #99 #daa67e
client.urgent   orange  #d05f03 #daa67e #ce #daa67e

client.background   yellow  #121212
client.focused  yellow  #999b00 #999b00 #ff #cacb7c
client.focused_inactive yellow  #999b00 #666700 #ff #cacb7c
client.unfocusedyellow  #999b00 #666700 #99 #cacb7c
client.urgent   yellow  #999b00 #cacb7c #ce #cacb7c

client.background   green   #121212
client.focused  green   #04af5b #04af5b #ff #7dd5aa
client.focused_inactive green   #04af5b #02713b #ff #7dd5aa
client.unfocusedgreen   #04af5b #02713b #99 #7dd5aa
client.urgent   green   #04af5b #7dd5aa #ce #7dd5aa

client.background   gray#121212
client.focused  gray#8c959f #8c959f #ff #c3c8cd
client.focused_inactive gray#8c959f #676d75 #ff #c3c8cd
client.unfocusedgray#8c959f #676d75 #99 #c3c8cd
client.urgent   gray#8c959f #c3c8cd #ce #c3c8cd

client.background   blue#121212
client.focused  blue#3384d6 #3384d6 #ff #95bee8
client.focused_inactive blue#3384d6 #1f5082 #ff #95bee8
client.unfocusedblue#3384d6 #1f5082 #99 #95bee8
client.urgent   blue#3384d6 #95bee8 #ce #95bee8

client.background   purple  #121212
client.focused  purple  #8f5cbe #8f5cbe #ff #c6abdd
client.focused_inactive purple  #8f5cbe #5c3e78 #ff #c6abdd
client.unfocusedp

Re: AW: [qubes-users] Re: i3 under Qubes 4 RC3

2018-02-22 Thread Florian Brandes

On 22.02.2018 03:38, '[799]' via qubes-users wrote:

Hello,


 Original-Nachricht 
An 26. Jan. 2018, 10:18, aaq via qubes-users schrieb:

 > My dmenu is broken, for starters. Dmenu only
 > shows dom0 applications, so I cannot start
 > anything that way.
 > When I run qvm-run to start something, I can
 > see that my VM is started (with qvm-ls) and I
 > can hear my CPU responding (as in it starts
 > fanning), but nothing visually happens.
 > Nothing is ever started.

Same problem for me, but I haven't found a solution. Using Qubes 4rc4 but i3 is 
not working like it has under Qubes 3.2.

Anyone else using i3 under Q4rc4?


Hi,

yes I use i3 under Q4rc4 without any issues or problems.
(Only thing I added/changed is case insensitivity for dmenu with -i option and 
changed the qube count command and the free disk space command in i3status)
Besides that, it worked out of the box for me (following the provided 
instructions concerning i3 on qubes).
I use Qubes4rc4 on two maschines, both work without a flaw concerning i3.

Regards,
Florian

--
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/b7d6fad2-87f8-5686-deec-cfd2bfe8ecb3%40gmx.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Enigmail not working with Split GPG

2017-07-18 Thread Florian Brandes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/18/2017 07:40 PM, Chris Laprise wrote:
> I already have Split GPG working with git, but after following the Split
> GPG doc for Thunderbird I'm getting errors (from the Enigmail
> Preferences dialog):
> 
>> GnuPG cannot be executed with the path provided. Enigmail is therefore
>> deactivated...
> 
> and
> 
>> Cannot connect to gpg-agent. Maybe your system uses a specialized tool
>> for passphrase handling (e.g. gnome-keyring, seahorse-agent, KDE wallet
>> manager, ...). Unfortunately Enigmail cannot control the passphrase
>> timeout for the tool you are using. Therefore the respective timeout
>> settings in Enigmail are disregarded.
> 
> 
> I'm using Debian 9 appVMs. Issue #2170 doesn't appear to be the same as
> this problem.
> 

Hi Chris,

I had the same problem. Thunderbird/Enigmail complained about not finding 
GnuPG. What worked for me (after you followed the steps in the Split GPG 
document and set up your *-gpg VM and added your *-gpg VM to 
/rw/config/gpg_split-domain) was simply restarting my email VM and my gpg VM. 

Just make sure, the /usr/bin/qubes-gpg-client-wrapper is set as a client (even 
though Enigmail complains, it should still stay there). I had to restart 
several times though and have no idea why you had to, but it worked. 

If not, you could try updating your template to "testing". (I have tried that 
with Fedora 23, 24 and 25, all with testing repos activated). 

Hope I could help a bit,

Florian
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQI0BAEBCAAeBQJZbvQ0FxxmbG9yaWFuLmJyYW5kZXNAZ214LmRlAAoJEKf3MHt6
BMRJPTMQAJvhrlUpGFMNIlilyLFnvh9dK9jNPQPbk80cN1X38iVxH+vigP4GFF85
JTO2MToVJjauvX9wlQgGMzlrGh58tALaKo9TLDYgPmNugbg6kH25IxnZf4xAYn81
dYsbs6cgFqgc3BUlr7iDZ4u2s3YdbqjDM5WJxugMaPGoGmuFG3E4X5x3ARjgOrWe
LrxN2eCij+C21tTMIyGAZMbE0YSSNVglRtlDdzU/W0wRG/P9UigAeniZnA+3BU1K
pw42FUeczVsSs21TAHDEk/IaRjcxPJvkT8x4GzLLj6XaQ7ZRFHqMOh3+Cfee8FLZ
PZnWX9u/SJ7clbaZCtaPrQouHk4fhj5dpOTOhMsuCPa6Xnx9xSs52eYR1nJc8g+R
njUOw9vJ3XwgIxPVvxcP4y2J4l3zaB+jObb+HIrMRuY/CDCDGnFsiUncwUvVKDdA
qcDcdy7CtFO6VVvdHfOS6jUQExyYcJHFid2U7vKLeZIjCdD9JpmbJm3ADhwP9D35
mLs7ckYGHkU38H6Os33SBUeQOI2RCyDz5ZZZU+Wd1fCn5kzVm0fodQ9HQ7RMXie6
GspclXUUEesrKzJvoTpMS2qcCkmaC4yK5NsOG0b5K8UxzyLi2gqTpCxmsGJgQVIx
lE09yn6stSM/SfAC2qBt4cMhh7jH66M8WCem/DO/bNitcVfb4scd
=Yqew
-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/aa194a78-2eb0-8246-9235-3255226de594%40gmx.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] "Storage Qube" or otherwise share folders of a drive selectively?

2017-07-11 Thread Florian Brandes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/11/2017 10:08 PM, codegee...@gmail.com wrote:
> Right now, I have a lot of stuff all just "consolidated" on one hard drive.
> /var/storage/{Anime,public_html,Documents,Pictures,.config/{pale\ 
> moon,deluge}} and so on.
> 
> But, obviously, I want to try with Qubes to have some isolation from my 
> webserver, perhaps have my Torrent client not be able to read my browser 
> profile, etc.
> 
> I'm thinking of setting up perhaps something like a "Storage Qube", which 
> will have the storage drive permanently attached, and be in charge of 
> managing permissions and serving the folders to authorized VMs via…NFS? SSHFS?
> 
> The catch is, I want to try to have it at least be reasonably performant 
> (i.e., my browser profile is there currently), and preferably not make it 
> "too" hacky/inelegant, in case the Qubes devs roll their own 
> guided/integrated system for this.
> 
> DOES Qubes have a facility to do this currently?
> 

Hi,

I'm new to qubes, so excuse me if I may sound stupid, but wouldn't it be easier 
to include your storage space in your overall qubes setup (maybe as an LVM), so 
that you would just use your qubes and extend their personal disk space? This 
way you could take advantage of the isolation provided by qubes without the 
hassle of setting up a dedicated storage VM which would also need to check 
permissions.

On the other hand you could probably set up a storage VM and serve the files 
via NFS on a IP basis. Since every qube has a unique IP address you could make 
sure that no other qube except the one you permit has access to a specific 
storage folder. 

Greetings, 

Florian 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQI0BAEBCAAeBQJZZTp6FxxmbG9yaWFuLmJyYW5kZXNAZ214LmRlAAoJEKf3MHt6
BMRJ8REP/1Q1/3DYemY7X1zHtyhZ2BGTh82HXqfwSEKxJDOm4kLa60pl+JAeJuUm
INegwPw6zLLnCNnT2+aRjIB/keRJmLGs+/cJeLd3Qt0gu8BXBIitAOl4kXPxksNi
tdi5p7xmyy2opiXQakGkHGY/knWV1CowPSNAny6LL5RI+Sn0rYXZW1EvMeAoPSZs
oZrBJB3tafVA5CB7ywe25TkdszeDSFR+ZnEQn3ZbsTHbNm/LnH+BsZ+G0LUZIGLf
R6GG9d5+mQvzUOjCK/ANVdxxSGCflfvkhC2ERLu9LXNRgjh6mnrQMlJFvtiBwun4
CJ/FHIbiG692dDfEpiJ8UuXXNXKIzhsKzhXkuwEjq5+ygvimP2cAGgMLMiTGSFJ/
MUa61mY6/n2SZja5fG/Lxitw7zRKGiblRYFrjYcm1KEt4j4HC6G07icJkN9znqiN
2MKtLCt+5xlUFHvvD7Jz5KZSWqy8EfFj17WAruGBSs+qANPLw3jehTMFGUN39PDe
EYLYhDSLmJPnY0qFZR/KOG7aD3LVMTBuCLMeuxDBXd4c9NHH9hgoBfiB/l6FQObO
jlEuLcENHyHBNsGA6wtirwhPLeoCwzXZl1KUJEjp8YNz/FnKcVS1tUyGnj1reRrG
C5zJCljHaEMEw81yKRU+gNY5kZaBHwAJUsPSisfm+6KjHD7ablUB
=RDvn
-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/a6068c15-7553-4604-c6de-ad3035c16483%40gmx.de.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - HP 15-ay123ng

2017-07-09 Thread Florian Brandes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I tested qubes 3.2 with the HP 15ay123ng laptop. 
Installation was done in UEFI mode from an USB drive.  

I changed the main HDD from the default 1 TB HDD to a 240GB SSD HD. Besides 
that,
it's a standard configuration. 

Everything works as expected. The only thing that needed work was the wireless 
card. 
An update to the current testing repository and a kernel update to 4.9 fixed it 
and everything
works flawlessly. 

Regards,

Florian Brandes 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQI0BAEBCAAeBQJZYf4LFxxmbG9yaWFuLmJyYW5kZXNAZ214LmRlAAoJEKf3MHt6
BMRJLnYP/3qoaoVbQixMcf3ZLupts+ecrqkL6gfNCkjb9Hqp38w/r/qBfYuVRjRF
en6Bs7ql4LryETNfPBh6DbxRS3gIvBiP2e681nlpCNhwnzmBDayXk3P8/UyTd0Iz
DmsROP75KqACDHSOgu8DTQCYyvSsBNupfC7itSjeG4ibN/RbbRTxJux68t9d7KtV
85rP98lmHNiPHGr2ctBpPqCPvgBJT70t5maV+ibf4hdikMQ1BPIrhHWS4LAmc0TU
cT60l5DzM/WMYc/BQjJPNW39QJbkgXo6HxDMWK3Ub208GqTwZywXkf6y4Yp7UoZi
UkTpwnPd58uv7vRpPx5WDcAjnU8TUdKB4oC0HaW9TBgwsShed4903P4PRmYKUajR
99uR6uJ9xpeeFxwY2Wm3Jvcq2uPrDGiQhFv8I9KZ/vPfQwt/GOT1Xy9o9LLF19xJ
K/SeiXQmbyeQXle6GweIFFgUkvek1xX2fhplfxG67k/D2V1Y2uuj7pmnsiWqIBcm
J5Ic47QvWFtDAHwe6O1NyJ792IFkC7tChmZC0p1Xu7UB6SKuAbkndhEwGUHwM2Ic
1LWfUWq6c8QAtkGfvy4APL2KxUX87f4L/uhgUPDunRPQiSMJ416sos1QnTev9Psf
vGaStSDVB/QAtQA+9OeDk+hk3zumCx1cIlCFMqFOU9+WVpf485Ew
=9gf4
-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/c727071d-8c45-6665-7813-050b6b97c9a3%40gmx.de.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-HP-HP_Notebook-20170708-230339.yml
Description: application/yaml


Qubes-HCL-HP-HP_Notebook-20170708-230339.yml.sig
Description: PGP signature