[qubes-users] Re: Suspend and high load issues on AppVM shutdown

2020-08-20 Thread 'Антон Чехов' via qubes-users
On Wednesday, August 19, 2020 at 12:04:49 PM UTC+2 John...@eclipso.email 
wrote:

> Hello, 
>
> i'm new to qubes and i like the security aspect it provides. During 
> testing i noticed 2 problems i couldn't solve. 
>
> 1. The resume from suspend function doesn't work for me. The Computer 
> powers on again, but the screen stays black. Keyboard and mouse don't work 
> either. Using other linux distributions force me to use 
> acpi_sleep=old_ordering to make suspend work. Trying to boot qubes with 
> that kernel option @multiboot and @module in grub doesn't help. 
>
> 2. Having AppVMs with several hundred GB, e.g. 500GB in vault leaves the 
> system crippled and often completly unresponsive for 1-2 minutes. Some 
> kworkerd process in dom0 eats up 100% of a single core. This happens every 
> time, even when i boot up the AppVM in question and shut it down 
> immediately again. The more GB the AppVM uses the longer the shutdown 
> takes. Seeing the HDD Led flashing nonstop during the shutdown made me 
> curious about the snapshot feature. Unfortunately, setting the qvm-volume 
> revert snapshot config from 1 to 0 didnt help. Neither with existing AppVMs 
> nor with newly created AppVMs. 
>

 Hi,
if you have the time and maybe a spare SSD/HDD available you could try the 
pre-release version of Qubes 4.1. It solved several issues for me but of 
course it isn't bug free and I don't know if it is regarded as safe to use 
securely already. 

1. I had the same problem with each previous version until testing Qubes 
4.1 solved this problem. I haven't shut down the laptop for a few days now 
but always resumed from suspend and it "just works". You could also try the 
latest kernel in 4.0 when updating dom0 but I don't know if a kernel option 
or the latest kernel solved the problem in Qubes 4.1. My problem was, that 
with the latest kernel my ethernet didn't work anymore in 4.0.
https://www.qubes-os.org/doc/software-update-dom0/

2. If you should decide to try out the latest 4.1 iso you could also try 
out btrfs during partitioning. There is an automated install with btrfs as 
well. Again, I don't know if everything is working as it should (looking at 
journalctl gives a few error messages but I get these in 4.0 as well) and I 
don't have these huge AppVM (why would you need 500GB in a vault app?) but 
I did notice an improvement when shutting down VM apps. It is rather fast. 
There is some minor bug in the Qube Manager: I sometimes have to close & 
reopen because the app has closed already but the Manager thinks it's still 
open. It usually takes less than 20 seconds and I think the warning comes 
when it takes more than 20 seconds. 

The thing is, this might not have to do anything with brfs or ext4 or 
whatever but maybe with the lack of LVM. (?) I only know a few things about 
the differences between these file systems so I might be completely wrong. 
Maybe others could share their experiences.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b3770bbf-81f2-42ac-9984-ec3c101f362bn%40googlegroups.com.


[qubes-users] Re: Google requiring login to access qubes-users

2020-08-16 Thread 'Антон Чехов' via qubes-users
On Saturday, August 15, 2020 at 9:39:30 PM UTC+2 tetra...@danwin1210.me 
wrote:

> WHen I try to access the Google Groups qubes-users site, sometimes 
> (circa 50%) I'm presented with a Google login prompt and can't access 
> the qubes-users group unless I have a Google account. 
>
> Since Qubes is privacy-focused it seems like maybe the Qubes mailing 
> lists should migrate to a less Orwellian mailing list provider. 
>

I noticed that as well. I've been surfing the internet almost exclusively 
via VPN for a very long time and the past few weeks have become a pain. 
Google services and other big companies like Amazon apparently increased 
measures against the use of VPN. I had used dedicated (public) servers for 
different sites for years without problems and suddenly Amazon and other 
big companies stopped accepting my usual payment methods like bank 
transfer. Instead I should use gift cards (!!!). 

Most servers of the big VPN providers like Proton, Air and other companies 
are blacklisted and therefore captcha have become a common occurrence. 

Maybe this will become our new home for the future:
https://qubes-os.discourse.group/

Or, like unman suggested, use google groups like a mailing list without 
ever logging in.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/eee239a4-cacf-470a-ab6d-bc38029e82ecn%40googlegroups.com.


Re: [qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections

2020-08-12 Thread 'Антон Чехов' via qubes-users
On Sunday, August 9, 2020 at 10:07:25 PM UTC+2 awokd wrote:

> 'Антон Чехов' via qubes-users: 
>
> > I have a handful ob Yubikeys (v.2 to v.4) and I really want to make use 
> of 
> > them with Qubes as well. So the next thing will be U2Fproxy and 
> > YubikeyLogin. 
> > There is some weird (?) behavior when attaching a Yubikey and the 
> > Personalization Tool in sys-usb is open. The key is recognized but I get 
> a 
> > never-ending loop of warnings: "Denied: qubes.InputKeyboard 
> > Denied qubes.InputKeyboard from sys-usb to dom0" 
> > 
> > I think that this is the right behavior but as long as I switch to the 
> > Personalization Tool these warnings never stop. Elsewhere I get this 
> > warning just the one time when I plug the key in. 
>
> From 
> https://www.qubes-os.org/doc/usb-qubes/#enable-a-usb-keyboard-for-login 
> under Manual setup, I wonder if you can edit 
> /etc/qubes-rpc/policy/qubes.InputKeyboard to something like sys-usb 
> sys-usb ask,default_target=sys-usb. Should be more documentation on that 
> file somewhere out there. 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>


Sorry for the late response. I tried that but the warning remained. 
Thinking a while about it I am of the opinion that it wasn't bad seeing 
this message. It only shows up once when plugging in a Yubikey (or I guess 
any device that is recognized as a keyboard) together with the message that 
a Yubikey is available. 
I don't need the Personalization Tool very often. On the contrary, once the 
slots are configured they usually stay that way for a long time.

My conclusion for now is, that I can live with this message. Or is this not 
the expected  behavior? What do you think about it?
It may be connected with some policy file for the Yubikey but I don't know 
and didn't have the time to seriously investigate these policy files & 
documentation. 

I am thinking about setting up 'sys-usb' as a disposable VM along the lines 
of the following documentation.
https://www.qubes-os.org/doc/disposablevm-customization/
Have you or others tried that out and is this documentation up to date?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a495d0a9-9845-48f0-946c-f40b3f538762n%40googlegroups.com.


Re: [qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections

2020-08-09 Thread 'Антон Чехов' via qubes-users
Just a little update: Both YubikeyLogin and U2Fproxy are working fine. I 
tried the latter with a Fedora32 AppVM and my Google Account. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8cbbaa0b-fcbb-4074-9176-cf00da77c982o%40googlegroups.com.


Re: [qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections

2020-08-09 Thread 'Антон Чехов' via qubes-users
On Friday, August 7, 2020 at 8:20:07 PM UTC+2, awokd wrote:
>
> 'Антон Чехов' via qubes-users: 
> > Hi, 
> > 
> > I just wanted to ask if there is hope getting sys-usb to work on the 
> G505s 
> > in the future? I tried sys-usb in Qubes 4.0 and 4.1 with and without 
> > kernelopts irqpoll but unfortunately it doesn't work for me. 
> > 
> > Off-topic: 
> > Suspend doesn't work in 4.0 but it works in 4.1. 
> > 
> Sys-usb works on mine with that irqpoll option, but it's pretty slow. 
> Might be picky about USB devices. Suspect it's actually something to do 
> with how Coreboot set up interrupt tables, not Qubes, but could be way 
> off. 
>
> -- 
> - don't top post 
> Mailing list etiquette: 
> - trim quoted reply to only relevant portions 
> - when possible, copy and paste text instead of screenshots 
>

 Hi,

thanks for your answer. It does work indeed! :-)

I tried again because we have the same laptop and I thought if it works for 
you it has to work for me as well. At first I tried again without the 
kernelopts: I did install sys-usb and then I did reboot without trying it 
out. After rebooting a random hard disk was recognized and I was happy. 
Unfortunately, after another reboot I got error messages again and it only 
worked now and then. It rather didn't.

I once again tried the kernelopts and I saw my mistake during the first 
time I tried. I left a minus before nopats. I hadn't noticed that before 
but after looking at other kernelopts in different VM in the Qubes Settings 
I noticed that the '-' did look out of place and so I was running the 
command again ( qvm-prefs sys-usb kernelopts 'nopat iommu=soft swiotlb=8192 
irqpoll') and after a reboot it now works. 

I have a handful ob Yubikeys (v.2 to v.4) and I really want to make use of 
them with Qubes as well. So the next thing will be U2Fproxy and 
YubikeyLogin. 
There is some weird (?) behavior when attaching a Yubikey and the 
Personalization Tool in sys-usb is open. The key is recognized but I get a 
never-ending loop of warnings: "Denied: qubes.InputKeyboard
Denied qubes.InputKeyboard from sys-usb to dom0"

I think that this is the right behavior but as long as I switch to the 
Personalization Tool these warnings never stop. Elsewhere I get this 
warning just the one time when I plug the key in.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/be7c972a-28db-4204-8102-5f6ec804dba9o%40googlegroups.com.


[qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections

2020-08-03 Thread 'Антон Чехов' via qubes-users
Hi,

I just wanted to ask if there is hope getting sys-usb to work on the G505s 
in the future? I tried sys-usb in Qubes 4.0 and 4.1 with and without 
kernelopts irqpoll but unfortunately it doesn't work for me. 

Off-topic:
Suspend doesn't work in 4.0 but it works in 4.1.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b17704fa-c98d-49fb-b3ac-ee84287429c7o%40googlegroups.com.


[qubes-users] Re: How to install kali and archlinux templates on latest rc2

2019-11-03 Thread 'Антон Чехов' via qubes-users
Hi,
try building the template again from scratch. I have had problems building 
the archlinux template in the past as well but I tried my luck again today 
and now it worked from start to finish (building on fedora-30). I did not 
change any lines in the configuration apart from leaving the line "‘*DISTS_VM 
?=" *in the qubes-os-master.conf empty but I guess that wasn't even 
necessary.

Whoever fixed the scripts for building archlinux: a big thanks from me!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/394a29f0-037d-4d47-8dc4-531cb3588baf%40googlegroups.com.


Re: [qubes-users] Qubes/class, Was: slightly off-topic: self-resetting OS idea

2019-09-03 Thread 'Антон Чехов' via qubes-users


On Wednesday, August 28, 2019 at 11:07:57 PM UTC+2, qtpie wrote:
>
> panina: 
> > 
> > 
> > On 8/26/19 6:27 PM, 799 wrote: 
> >> Hello 
> >> 
> >> David Hobach   tri...@hackingthe.net >> 
> >> schrieb am Mo., 26. Aug. 2019, 11:22: 
> >> 
> >> On 8/26/19 10:24 AM, panina wrote: 
> >> > Hi! 
> >> > 
> >> > This is not strictly Qubes-OS related, rather inspired by Qubes. 
> >> > 
> >> > I've been struggling with some parts of Qubes usage. Most of the 
> time, 
> >> > it is overkill for me, and putting some strain on my computer. 
> The 
> >> > bugginess is also quite annoying, whenever I just need to do some 
> >> > everyday work. 
> >> > I've been thinking I'd like some form of dual-boot solution, or 
> >> possibly 
> >> > a Live USB that could be used. 
> >> > Most of the time I work with ssh and webapps, so the only 
> persistent 
> >> > data I need to work will fit on a smartcard. 
> >> > 
> >> > My thought is to have an installation that mounts most of the 
> root 
> >> > partition as readonly, and uses ramdisks wherever the system 
> wants to 
> >> > write (e.g /var/log). I'm also thinking it should be possible to 
> get a 
> >> > fingerprint or somesuch of the root partition, and use my TPM2 to 
> >> check 
> >> > this. 
> >> > 
> >> > The system should also have a possibility to update itself, that 
> I can 
> >> > choose to do in environments that I feel is safe. 
> >> > 
> >> > I am wondering if anyone knows of an OS that works like this? Or 
> if 
> >> > anyone knows of tools that might accomplish parts of this? 
> >> 
> >> Ehm... You're describing Qubes OS with disposable VMs there? The 
> >> fingerprinting is essentially AEM? 
> >> 
> >> If you need to keep your data on an external disk (SDCard), you can 
> use 
> >> either a manual approach with qvm-copy, permanently attach the disk 
> >> to a 
> >> single disposable VM with a fixed name or use an automated solution 
> >> such 
> >> as [1]. You might also want to look into qvm-pool. 
> >> 
> >> [1] https://github.com/3hhh/qcrypt 
> >> 
> >> 
> >> I don't know why people are complaining about the "bugginess" and that 
> >> it needs more performance. 
> >> 
> >> If you buy the right hardware you'll not run into lots of bugs and get 
> >> enough performance to run qubes. You can buy a Lenovo T530/430, W530, 
> >> X230 for not much money, add a SSD some RAM and you'll not run into 
> >> performance problems (normal use). 
> > 
> > This is a view that I see quite a lot. It is a whole different 
> > discussion. Hence the re-subjecting. 
> > 
> > Firstly, this view completely lacks class analysis. Not everyone can 
> > afford to buy the newest shiny. A lot of us have to use whatever we can 
> > get our hands on. 
> > Whenever a secure OS is mentioned, Qubes is the go-to. Everyone comes 
> > here. The approach that you have to buy new, specific hardware to have a 
> > functioning OS means anyone poor, or in a country with a poor dollar 
> > exchange rate, is left behind. 
> Panina, I hate to say this since class awareness is sorely lacking in 
> tech, but in this case I dont agree with you. You dont need to buy the 
> latest and/or shiny. If you look up any of the models mentioned 
> previously on ebay (Lenovo T530/430, W530, X230) and upgrade those with 
> an SSD you can have a fine Qubes laptop for $300 that will last you many 
> years. I am personally using qubes for a few years on a laptop from 2014 
> just like this. Maybe this could be mentioned more clearly in the docs, 
> many people seem to think that they need a new i7 with 16GB+ of ram. 
> That is absolutely not the case. 
>
> $300 is very different from $1500 but still definitely not free. If I 
> take 'latest and shiny' a little less literal and by 'whatever we can 
> get our hand on' you mean a laptop you can get for less than $200 or 
> even for free, then I retract my point. However this is not really qubes 
> can do something about. Hardware related projects have minimum hardware 
> requirements, that hardware often (not always) costs money, and money is 
> a class issue which it shouldnt be. 
>
> Maybe somebody on the mailinglist works at a big company with lots of 
> qubes-compatible laptops that get written of soon and these could be 
> distributed trough the Qubes project? Or maybe somebody knows a 
> foundation coordinating this kind of project or helping people out with 
> hardware some other way? 
>
>
Just a little addition to the devices already mentioned:
I've been using a T420 (16GB RAM) with Qubes4 for as long as it has been 
available and it is working very well. There are a few things (suspend & 
resume, backlight is never really off) that aren't working right now but 
nothing too serious. It cost me 150€ and this laptop is widely available 
(of course, there are always exceptions).

For the fun of it, I purchased a G505S as well 

Re: [qubes-users] Software installed in template does not work in appVM

2019-09-01 Thread 'Антон Чехов' via qubes-users


On Sunday, September 1, 2019 at 3:46:00 PM UTC+2, Антон Чехов wrote:
>
>
>
> On Sunday, September 1, 2019 at 3:32:24 PM UTC+2, awokd wrote:
>>
>> 'Антон Чехов' via qubes-users: 
>> > Hi, 
>> > 
>> > I have a small problem that I don't know how to tackle. 
>> > I've installed a language software/dictionary in a clone of the Fedora 
>> 30 
>> > Template. The parent folder in the template is /home/user/. I can start 
>> the 
>> > program by going to the folder and using a shell script ( 
>> ./script-name). 
>> > When I shut down the template and opened a Fedora-appVM based on the 
>> > template-clone there was a menu entry available with the name of the 
>> > program. Unfortunately it didn't start. Furthermore I couldn't find any 
>> > traces of the program but to be honest I never had to look up how the 
>> > software is connected to a templateVM. 
>> > 
>> > Any help would be appreciated. 
>> > 
>> TL;DR version- Since that dictionary installs in /home/user, install it 
>> in the AppVM instead. 
>>
>> Long version- 
>> https://www.qubes-os.org/doc/templates/#inheritance-and-persistence. 
>>
>
>
> Thanks for your answer but doesn't that mean I should install the program 
> somewhere else than /home in a templateVM? Moving it is not possible, is it?
> Has anyone installed a licensed software in a template, activated it, and 
> then successfully started it in an App? Is this possible?
>
> The dictionary can be used with any document or browser. When I move the 
> cursor over a word, the translation will be shown in the program. It would 
> be a nice addition but of course one installation in an AppVM would also be 
> enough.
>


Okay, I tried myself and moved the folder from /home to /etc and the 
program did open via terminal in every Fedora based appVM but the 
activation showed an error message. Also there were problems with fonts and 
the dictionary wasn't displayed correctly.

I then did install the program in the appVM like recommended and now 
everything is working fine, including the shortcut in the appVM menu. 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bc845504-d4eb-4f24-be3a-215ec4f8208b%40googlegroups.com.


Re: [qubes-users] Software installed in template does not work in appVM

2019-09-01 Thread 'Антон Чехов' via qubes-users


On Sunday, September 1, 2019 at 3:32:24 PM UTC+2, awokd wrote:
>
> 'Антон Чехов' via qubes-users: 
> > Hi, 
> > 
> > I have a small problem that I don't know how to tackle. 
> > I've installed a language software/dictionary in a clone of the Fedora 
> 30 
> > Template. The parent folder in the template is /home/user/. I can start 
> the 
> > program by going to the folder and using a shell script ( 
> ./script-name). 
> > When I shut down the template and opened a Fedora-appVM based on the 
> > template-clone there was a menu entry available with the name of the 
> > program. Unfortunately it didn't start. Furthermore I couldn't find any 
> > traces of the program but to be honest I never had to look up how the 
> > software is connected to a templateVM. 
> > 
> > Any help would be appreciated. 
> > 
> TL;DR version- Since that dictionary installs in /home/user, install it 
> in the AppVM instead. 
>
> Long version- 
> https://www.qubes-os.org/doc/templates/#inheritance-and-persistence. 
>


Thanks for your answer but doesn't that mean I should install the program 
somewhere else than /home in a templateVM? Moving it is not possible, is it?
Has anyone installed a licensed software in a template, activated it, and 
then successfully started it in an App? Is this possible?

The dictionary can be used with any document or browser. When I move the 
cursor over a word, the translation will be shown in the program. It would 
be a nice addition but of course one installation in an AppVM would also be 
enough.

  

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c290c6a1-c264-4fc5-af47-28d8e9ba7114%40googlegroups.com.


[qubes-users] Software installed in template does not work in appVM

2019-09-01 Thread 'Антон Чехов' via qubes-users
Hi,

I have a small problem that I don't know how to tackle.
I've installed a language software/dictionary in a clone of the Fedora 30 
Template. The parent folder in the template is /home/user/. I can start the 
program by going to the folder and using a shell script ( ./script-name).
When I shut down the template and opened a Fedora-appVM based on the 
template-clone there was a menu entry available with the name of the 
program. Unfortunately it didn't start. Furthermore I couldn't find any 
traces of the program but to be honest I never had to look up how the 
software is connected to a templateVM.

Any help would be appreciated.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/91625c1d-5920-428a-8958-de08f02c800e%40googlegroups.com.


[qubes-users] Re: WARNING: don't update qubes, will break your install

2019-05-26 Thread 'Антон Чехов' via qubes-users
On Saturday, May 25, 2019 at 10:55:44 PM UTC+2, dro...@gmail.com wrote:
> I just finished a fresh install of Qubes, then updated dom0, fedora template, 
> debian template, whonix gw and ws templates, as per instructions on
> 
> https://www.qubes-os.org/doc/installation-guide/
> 
> Shutdown, boot.
> 
> Qubes won't let me login.  Same problem as in my other post.

I've been updating my system regularly since moving from Qubes3.2 to Qubes4 and 
never had any issues so far (default kernel is 4.19.45-1 at the moment) even 
with testing repos enabled. 

I did have to check some VM for using the latest kernel (and change manually) 
even when I had chosen the latest one in the global settings already. But that 
might have been a mistake on my part - I can't really say anymore.

So, when updating dom0 via terminal you can see if the older kernels are being 
erased or if they are still in use somewhere. 
I've read that maybe you could run out of space but that never happened to me 
and I keep looking that all my VM are using the latest kernel.

-- 
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/d3c43284-1fd9-4d03-8680-5908ea272f60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: lenovo t400 will qubes work with lenovo's bios?

2019-03-25 Thread 'Антон Чехов' via qubes-users
On Monday, March 25, 2019 at 5:19:56 PM UTC+1, jcr...@gmail.com wrote:
> On Tuesday, January 2, 2018 at 6:25:52 PM UTC+1, ronwi...@safe-mail.net wrote:
> > https://www.qubes-os.org/hcl/
> > 
> > Can you install qubes on a lenovo t400, which runs the lenovo bios? Thanks.
> 
> Did you try this?
> Seems T400 do not have Intel vt-d as far as I can tell.

Well, I did and I can tell you that it didn't work. You already described the 
reason for this. I also did try with libreboot (which is based on coreboot) and 
it didn't work either.

Also the famous Lenovo G505S does *not* work with stock bios, I think it is 
missing microcodes for Qubes 4.0. I tried different versions of the stock bios. 
The latest is v3.0, if I recall correctly.

Like James Goodwin mentioned earlier in this thread about a year ago, the T420 
works (almost) perfectly out of the box.
The only problem I am having is suspend. There is a strange behavior when 
waking up, it's some cycle where all the lights are blinking every few seconds.

Apart from this I think the T420 is a very good choice for a small budget. 
Also, it is very silent, which for me is an important factor.

-- 
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/ff11dbe6-76c1-4a7c-8db3-2254bccb3ec6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: TOR browser updates.

2018-11-19 Thread 'Антон Чехов' via qubes-users
On Tuesday, November 20, 2018 at 3:39:24 AM UTC+1, William Fisher wrote:
> How do I update the TOR browsers at the Template VM level? I've updated TOR 
> at the APP level but it doesn't stay updated.

I updated my template-vm (whonix-gw-14, whonix-ws-14 and sys-whonix) this week 
via console (sudo apt-get update && sudo apt-get dist-upgrade) and the latest 
TOR browser was downloaded. 

I started a disposable whonix-vm and checked (help -> about tor browser) the 
version and it was 8.0.3 which should be the latest.
Starting anon-whonix-vm was not updated (8.0) but tor-browser did download the 
latest version upon opening it (help -> about tor browser) and it stays updated.

-- 
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/fff3de14-ce48-4f6e-9f40-07cf7bf3f427%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: New to Qubes having issues logging into my vpn service despite following the Qubes instructions

2018-09-18 Thread 'Антон Чехов' via qubes-users
On Tuesday, September 18, 2018 at 12:02:51 PM UTC+2, Wolf moon wrote:
> On Tuesday, 18 September 2018 10:46:44 UTC+1, Антон Чехов  wrote:
> > On Tuesday, September 18, 2018 at 10:37:06 AM UTC+2, Wolf moon wrote:
> > > On Saturday, 15 September 2018 04:21:53 UTC+1, Wolf moon  wrote:
> > > > Hi guys New to Qubes ( which is an amazing feat of cyber security 
> > > > engineering ) all working fine and learning my way around it. 
> > > > 
> > > > My only issue is logging into my vpn service. 
> > > > 
> > > > I have followed the Qubes instructions ( which the images are different 
> > > > to Qubes 4.0 and after searching the net on this matter someone said 
> > > > that this is a shot of the previous Qubes so not helpful there ) I also 
> > > > contacted my vpn service on the matter. They read up on the Qubes 
> > > > instructions and emailed me back a step by step guide but still no joy. 
> > > > 
> > > > My vpn service works well on my Raspberry Pi 3 in the command line ( 
> > > > which I found simple instructions for elsewhere on the internet ) and 
> > > > works fine on my windows 10 system as its got an app interface you 
> > > > download.
> > > > 
> > > > Its just Qubes I am having issues with. I am by no means a hardcore 
> > > > techy, I am learning and not afraid or unfamiliar using the command 
> > > > line in linux. 
> > > > 
> > > > I have contacted the Qubes team after trying my best effort to resolve 
> > > > this on my own as I know they are a small team of 5 or so last time I 
> > > > checked.
> > > > 
> > > > Any help and advice would be greatly appreciated.
> > > > 
> > > > Best,
> > > > 
> > > > Wolf Moon
> > > 
> > > Okay guys so I am signed up to Nordvpn. ( To note: I always update 
> > > everything in Qube manager )
> > > 
> > > I started off by google searching how to set up a vpn on qubes. I dont 
> > > have every forum page be it google groups or reddit page saved I read 
> > > unfortunately. 
> > > 
> > > But they generally instructed me to do go through the steps to set up a 
> > > vpn as Qubes instructs on their page 
> > > https://www.qubes-os.org/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-networkmanager
> > > 
> > > Specifically Set up a ProxyVM as a VPN gateway using iptables and CLI 
> > > scripts
> > > 
> > > What I was referencing referring to the diagram/photo being outdated or 
> > > of the old version of Qubes prior to 4.0 was the Dom0 create a new Vm. It 
> > > just comes up looking different which is what one of the OPs mentioned on 
> > > one of the how to guides I found. 
> > > 
> > > Moving forward.
> > > 
> > > Certain commands didn't work like sudo which after googling one forum 
> > > posted in Qubes you dont use sudo much, dnf ( what ever that is ) is used 
> > > instead which is what I used.
> > > 
> > > I created a Qube named it Nordvpn > Template > Fedora-26 > Networking > 
> > > sys-net 
> > > Appvm
> > > 
> > > From there the rest of the instructions didn't work on Qubes for me.
> > > 
> > > Apart from downloading the nord config files successfully which are in my 
> > > nordvpn documents folder with all the server addresses as txt files eg 
> > > uk648.nordvpn.comtcp443.ovpn
> > > 
> > > Also was instructed to download nano reader and a few other things.
> > > 
> > > My cd ls in my nordvpn terminal is as follows 
> > > 
> > > DesktopMusic  Templates   nano.save
> > > Documents  Pictures   Videos  openvpn-client.ovpn.txt
> > > Downloads  Public  auth-user-pass  pass.txt
> > > 
> > > ( To note and jumping ahead: following tasket's Reddit page on Qubes vpn 
> > > set up instructions I added vpn-handler-openvpn to services in the appvm 
> > > I named Nordvpn )
> > > 
> > > So from there comes Nordvpns reply ( they were very helpful before 
> > > helping me successfully setting up my vpn link on my Raspberry Pi )
> > > 
> > > I received this email: 
> > > 
> > > Hello, Adam,
> > > 
> > > I have checked your OS documentation and it would be great if you could 
> > > test out the following setup:
> > > Disable any auto-starting service tha

[qubes-users] Re: New to Qubes having issues logging into my vpn service despite following the Qubes instructions

2018-09-18 Thread 'Антон Чехов' via qubes-users
On Tuesday, September 18, 2018 at 10:37:06 AM UTC+2, Wolf moon wrote:
> On Saturday, 15 September 2018 04:21:53 UTC+1, Wolf moon  wrote:
> > Hi guys New to Qubes ( which is an amazing feat of cyber security 
> > engineering ) all working fine and learning my way around it. 
> > 
> > My only issue is logging into my vpn service. 
> > 
> > I have followed the Qubes instructions ( which the images are different to 
> > Qubes 4.0 and after searching the net on this matter someone said that this 
> > is a shot of the previous Qubes so not helpful there ) I also contacted my 
> > vpn service on the matter. They read up on the Qubes instructions and 
> > emailed me back a step by step guide but still no joy. 
> > 
> > My vpn service works well on my Raspberry Pi 3 in the command line ( which 
> > I found simple instructions for elsewhere on the internet ) and works fine 
> > on my windows 10 system as its got an app interface you download.
> > 
> > Its just Qubes I am having issues with. I am by no means a hardcore techy, 
> > I am learning and not afraid or unfamiliar using the command line in linux. 
> > 
> > I have contacted the Qubes team after trying my best effort to resolve this 
> > on my own as I know they are a small team of 5 or so last time I checked.
> > 
> > Any help and advice would be greatly appreciated.
> > 
> > Best,
> > 
> > Wolf Moon
> 
> Okay guys so I am signed up to Nordvpn. ( To note: I always update everything 
> in Qube manager )
> 
> I started off by google searching how to set up a vpn on qubes. I dont have 
> every forum page be it google groups or reddit page saved I read 
> unfortunately. 
> 
> But they generally instructed me to do go through the steps to set up a vpn 
> as Qubes instructs on their page 
> https://www.qubes-os.org/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-networkmanager
> 
> Specifically Set up a ProxyVM as a VPN gateway using iptables and CLI scripts
> 
> What I was referencing referring to the diagram/photo being outdated or of 
> the old version of Qubes prior to 4.0 was the Dom0 create a new Vm. It just 
> comes up looking different which is what one of the OPs mentioned on one of 
> the how to guides I found. 
> 
> Moving forward.
> 
> Certain commands didn't work like sudo which after googling one forum posted 
> in Qubes you dont use sudo much, dnf ( what ever that is ) is used instead 
> which is what I used.
> 
> I created a Qube named it Nordvpn > Template > Fedora-26 > Networking > 
> sys-net 
> Appvm
> 
> From there the rest of the instructions didn't work on Qubes for me.
> 
> Apart from downloading the nord config files successfully which are in my 
> nordvpn documents folder with all the server addresses as txt files eg 
> uk648.nordvpn.comtcp443.ovpn
> 
> Also was instructed to download nano reader and a few other things.
> 
> My cd ls in my nordvpn terminal is as follows 
> 
> DesktopMusic  Templates   nano.save
> Documents  Pictures   Videos  openvpn-client.ovpn.txt
> Downloads  Public  auth-user-pass  pass.txt
> 
> ( To note and jumping ahead: following tasket's Reddit page on Qubes vpn set 
> up instructions I added vpn-handler-openvpn to services in the appvm I named 
> Nordvpn )
> 
> So from there comes Nordvpns reply ( they were very helpful before helping me 
> successfully setting up my vpn link on my Raspberry Pi )
> 
> I received this email: 
> 
> Hello, Adam,
> 
> I have checked your OS documentation and it would be great if you could test 
> out the following setup:
> Disable any auto-starting service that comes with the software package. For 
> example for OpenVPN.
> sudo systemctl disable openvpn.service
> You may also wish to install nano or another simple text editor for entering 
> the scripts below. Now run the following command to create VPN directory:
> sudo mkdir /rw/config/vpn
> Enter the directory using the following command:
> cd 
> /rw/config/vpn
> 
> Then our website - https://nordvpn.com/servers/#recommended , on the server 
> picker you will see recommended server number. Then open 
> https://nordvpn.com/ovpn/ website and download recommended server file. You 
> can download directly to device and transfer to your VM or use command to 
> download from the hyperlink:
> sudo wget 
> https://downloads.nordcdn.com/configs/files/ovpn_legacy/servers/us1310.nordvpn.com.udp1194.ovpn
> (Change the last line of server name to download the correct file). Then 
> rename downloaded file to client.ovpn
> The VPN client may not be able to prompt you for credentials when connecting 
> to the server. Create a file in the /rw/config/vpn folder with your 
> credentials and using a directive. For example for OpenVPN, edit:
> auth-user-pass
> to:
> auth-user-pass pass.txt
> 
> Save file /rw/config/vpn/client.ovpn. Make sure a /rw/config/vpn/pass.txt 
> file actually exists.
> sudo nano /rw/config/vpn/pass.txt
> Add:
> username
> password
> Replace username and password with your actual username and 

[qubes-users] Re: Archlinux template for Qubes R4 build is working

2018-09-18 Thread 'Антон Чехов' via qubes-users
On Wednesday, May 30, 2018 at 5:37:17 PM UTC+2, qubes...@secmail.pro wrote:
> Archlinux template seems to be fully working and building completely but
> requires minor changes:
> 
> run ./setup
> release 4.0 stable
> select archlinux
> 
> edit the file
> qubes-src/builder-archlinux/scripts/04_install_qubes.sh
> 
> find the line:
> echo "  --> Registering Qubes custom repository..."
> cut out what is in 4 lines after this one echo and paste this instead:
> su -c 'echo "[qubes] " >> $INSTALLDIR/etc/pacman.conf'
> su -c 'echo " #QubesTMP" >> $INSTALLDIR/etc/pacman.conf'
> su -c 'echo "SigLevel = Optional TrustAll " >> $INSTALLDIR/etc/pacman.conf'
> su -c 'echo " #QubesTMP" >> $INSTALLDIR/etc/pacman.conf'
> su -c 'echo "Server = file:///tmp/qubes-packages-mirror-repo/pkgs " >>
> $INSTALLDIR/etc/pacman.conf'
> su -c 'echo " #QubesTMP" >> $INSTALLDIR/etc/pacman.conf'
> 
> The build script has some problem with #comments.
> Not sure why this fix works but different fixes were not, was about to
> give up but then it worked.
> 
> Another couple of edits (taken from 2 day old fix on github)
> /qubes-src/gui-agent-linux/archlinux/PKGBUILD
> In line 11
> 
> makedepends=(pkg-config make gcc patch git automake autoconf libtool
> pulseaudio xorg-server-devel xorg-util-macros xf86dgaproto libxcomposite
> qubes-vm-gui-common qubes-libvchan-xen qubes-db-vm libxt pixman)
> 
> pixman is added just to be sure but im unsure how it helps, as said on
> github too.
> 
> within the same file edit line 62:
> 'xorg-server>=1.19.0' 'xorg-server<1.21.0'
> 
> changed from "1.20.0" to "1.21.0"
> 
> and that would be it. Builds.
> 
> The qubes repository with archlinux binaries has its pgp signature expired
> for over 2 months so Qubes- stuff does not upgrade from within template.
> [qubes-r4.0]
> Server = http://olivier.medoc.free.fr/archlinux/current
> thats why it does not matter (much) if it is left disabled by default.
> 
> the only leftover would be to edit /etc/pacman.conf and remove last 3
> lines which were used during template build.
> 
> Thank you all

Hello,

I am having some difficulties building the Arch Linux template for Qubes 4.0.

I have been following the steps along the lines of this guide:
https://github.com/QubesOS/qubes-issues/issues/3185

Everything is looking fine until “make template”.

The logfile is showing this error message:

--> Updating pacman sources...
warning: config file /etc/pacman.conf, line 104: directive '[qubes] # QubesTMP'$
error: config file /etc/pacman.conf, line 105: invalid value for 'SigLevel' : '$
error: config file /etc/pacman.conf, line 105: invalid value for 'SigLevel' : '$
make[1]: *** [Makefile:64: rootimg-build] Error 1

I changed the SigLevel in the pacman.conf to “Optional TrustAll” and started 
the whole process again but nothing changed. 

I tried cutting out the lines and pasting these but there were more error 
messages instead suggesting that there is something wrong in these lines. Has 
anybody an idea what went wrong and what I could do?

A little help would be very welcome. I’ve been using Arch for quite some time 
and it would be great to have it as a template.

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/3d386ac1-3e29-4cee-a179-9518e5ce49ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Calling qubes expets VPN sign in headache! Nordvpn wont work

2018-09-18 Thread 'Антон Чехов' via qubes-users
On Tuesday, September 18, 2018 at 8:48:16 AM UTC+2, Wolf moon wrote:
> Guys despite going through guides like 
> https://github.com/tasket/Qubes-vpn-support etc there are parts that qubes 
> gets stuck on like in the mentioned guide I get to step 2 and it does not 
> recognise command 1n which sticks me at that stage. 
> 
> I have all the config files downloaded from nord. 
> 
> Can you show me either a simpler way to sign on to my vpn account or point me 
> in the right direction of a guide that actually works.
> 
> I had no issues signing into my vpn service via the command line on my 
> raspberry pi and on my windows 10 machine it was even easier as it could 
> download an app. 
> 
> Best,
> 
> Wolf moon

If you don't know exactly what you are doing it is best to copy & paste the 
commands. In Qubes this is done a little differently, so be sure to read this 
first:
https://www.qubes-os.org/doc/copy-paste/

The command is LN in lower case ln, not 1n. 
https://en.wikipedia.org/wiki/Ln_(Unix) 

It should work but if it doesn't you could still try the "old" command line 
approach, explained here:
https://www.qubes-os.org/doc/vpn/
The instructions you should try start under the headline "Set up a ProxyVM as a 
VPN gateway using iptables and CLI scripts"

Good luck!

-- 
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/86a3b28a-a5a7-4ab2-b861-20dec8b1b922%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-20 Thread 'Антон Чехов' via qubes-users
On Friday, April 20, 2018 at 1:38:36 AM UTC+2, cooloutac wrote:
> On Thursday, April 19, 2018 at 6:38:57 AM UTC-4, Антон Чехов wrote:
> > On Thursday, April 19, 2018 at 12:27:25 PM UTC+2, cooloutac wrote:
> > > On Thursday, April 19, 2018 at 6:19:45 AM UTC-4, Антон Чехов wrote:
> > > > On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner 
> > > > wrote:
> > > > > On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner 
> > > > > wrote:
> > > > > > Hi all,
> > > > > > 
> > > > > > After a recent reboot, the devices and VM tray icons no longer are 
> > > > > > appearing on boot in Xfce. I have no idea what might have caused 
> > > > > > this. There were no dom0 updates in the meantime. If I try to 
> > > > > > manually run them, e.g., python3 -mqui.tray.devices, I get the 
> > > > > > following:
> > > > > > 
> > > > > > ERROR:dbus.proxies.Introspect error on 
> > > > > > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > > > > > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 
> > > > > > Message recipient disconnected from message bus without replying
> > > > > > 
> > > > > > Followed by a backtrace, the relevant part appears to be:
> > > > > > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 
> > > > > > 22, in 
> > > > > >DOMAINS = qui.models.qubes.DomainManager()
> > > > > > 
> > > > > > Any advice would be appreciated, since with no icons, I'm also not 
> > > > > > appearing to get notifications for devices and VM actions.
> > > > > > 
> > > > > > Best,
> > > > > > Daniel
> > > > > 
> > > > > Interesting discovery: this problem arose as a result of setting 
> > > > > qrexec_timeout on an arbitrary VM to a value larger than an INT32. So 
> > > > > the moral of the story: Don't try to set qrexec_timeout too high!
> > > > > 
> > > > > Daniel
> > > > 
> > > > Hello,
> > > > 
> > > > I am experiencing the same problem with the final version of 4.0 but I 
> > > > did not change a setting of qrexec_timeout. The device tray icon 
> > > > disappeared suddenly.
> > > > 
> > > > I am getting tons of "GTK error" when trying to run manually via 
> > > > "python3 -mqui.tray.devices"?
> > > > 
> > > > So far I haven't been able to get the devices tray appear again but I 
> > > > can attach devices via command line.
> > > > 
> > > > Anyone having the same problem?
> > > 
> > > no,  weird.  have you tried to use qubes-manager at all?
> > 
> > Do you mean the VM manager? If so, yes! It does work with a lot of bugs 
> > like a lot of people reported already. I don't see all apps in the VM 
> > manager and the lights indicating a working app do only appear or disappear 
> > when clicking an app. Sometimes I forget an app is still running.
> > VPN apps I created don't appear in the VM manager at all, so I do need to 
> > use CLI.
> > 
> > Having a working devices tray icon would be nice, though.
> 
> ya hope they fix that issue soon.  What I do is keep hitting the green 
> refresh icon on top to refresh the manager to see the current vm states.  For 
> some reason it doesn't refresh on its own.   Weird that custom appvms you 
> create don't appear in the manager.
> 
> Have you made alot of customizations in dom0?

None at all!
I tried using Qubes 4 before the final release but had problems during install. 
The final version worked flawlessly. I did not want to import any VMs from 3.2 
because I had problems before and I wanted to do a clean install with 
everything built in Qubes 4. 
So far I can't complain. The problems I am having are all of minor importance. 
I had some problems with localization and keyboard, and problems with icons and 
the VM manager. All in all the system is working fine but I prefer working with 
3.2 in the meantime. The icons and the look is really great. I hope that Qubes 
4 will get there eventually.

I am using a Lenovo T420 with 16GB and stock BIOS. I am planning on using 
coreboot sometime in the future.

-- 
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/d1ce1cc1-cf5f-4e8a-a5e2-f60b13f7eb21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: ProtonMail bridge

2018-04-20 Thread 'Антон Чехов' via qubes-users
On Friday, April 20, 2018 at 4:24:50 PM UTC+2, Антон Чехов wrote:
> On Friday, April 20, 2018 at 7:50:37 AM UTC+2, ThierryIT wrote:
> > Le vendredi 20 avril 2018 00:25:43 UTC+3, chipp...@gmail.com a écrit :
> > > AHTON,
> > >   Thank you for sharing what worked for you.  My bridge was installed 
> > > into the personal VM (Fedora-26).
> > >  I understand what you are suggesting, and hope to try it out this 
> > > weekend when I slow down again.
> > > 
> > > Regards ~
> > 
> > Hi,
> > How did you get the Linux version of the Bridge ... Seems not to be yet 
> > available ... Beta tester ?
> 
> Did you write to "bri...@protonmail.ch"?
> I wrote to them at the end of february and I got an answer 5 days later. I 
> didn't have much correspondence but I always got an answer. If you're a paid 
> customer I'd try again.

I meant "paying customer". Paid would be nice! Haha

-- 
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/571f3b03-aacb-4c55-bbd2-bd9127a9e704%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: ProtonMail bridge

2018-04-20 Thread 'Антон Чехов' via qubes-users
On Friday, April 20, 2018 at 7:50:37 AM UTC+2, ThierryIT wrote:
> Le vendredi 20 avril 2018 00:25:43 UTC+3, chipp...@gmail.com a écrit :
> > AHTON,
> >   Thank you for sharing what worked for you.  My bridge was installed 
> > into the personal VM (Fedora-26).
> >  I understand what you are suggesting, and hope to try it out this 
> > weekend when I slow down again.
> > 
> > Regards ~
> 
> Hi,
> How did you get the Linux version of the Bridge ... Seems not to be yet 
> available ... Beta tester ?

Did you write to "bri...@protonmail.ch"?
I wrote to them at the end of february and I got an answer 5 days later. I 
didn't have much correspondence but I always got an answer. If you're a paid 
customer I'd try again.

-- 
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/7acbc571-1092-4859-b9c4-d91b38c781e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-19 Thread 'Антон Чехов' via qubes-users
On Thursday, April 19, 2018 at 12:27:25 PM UTC+2, cooloutac wrote:
> On Thursday, April 19, 2018 at 6:19:45 AM UTC-4, Антон Чехов wrote:
> > On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner wrote:
> > > On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner wrote:
> > > > Hi all,
> > > > 
> > > > After a recent reboot, the devices and VM tray icons no longer are 
> > > > appearing on boot in Xfce. I have no idea what might have caused this. 
> > > > There were no dom0 updates in the meantime. If I try to manually run 
> > > > them, e.g., python3 -mqui.tray.devices, I get the following:
> > > > 
> > > > ERROR:dbus.proxies.Introspect error on 
> > > > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > > > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 
> > > > Message recipient disconnected from message bus without replying
> > > > 
> > > > Followed by a backtrace, the relevant part appears to be:
> > > > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 22, 
> > > > in 
> > > >DOMAINS = qui.models.qubes.DomainManager()
> > > > 
> > > > Any advice would be appreciated, since with no icons, I'm also not 
> > > > appearing to get notifications for devices and VM actions.
> > > > 
> > > > Best,
> > > > Daniel
> > > 
> > > Interesting discovery: this problem arose as a result of setting 
> > > qrexec_timeout on an arbitrary VM to a value larger than an INT32. So the 
> > > moral of the story: Don't try to set qrexec_timeout too high!
> > > 
> > > Daniel
> > 
> > Hello,
> > 
> > I am experiencing the same problem with the final version of 4.0 but I did 
> > not change a setting of qrexec_timeout. The device tray icon disappeared 
> > suddenly.
> > 
> > I am getting tons of "GTK error" when trying to run manually via "python3 
> > -mqui.tray.devices"?
> > 
> > So far I haven't been able to get the devices tray appear again but I can 
> > attach devices via command line.
> > 
> > Anyone having the same problem?
> 
> no,  weird.  have you tried to use qubes-manager at all?

Do you mean the VM manager? If so, yes! It does work with a lot of bugs like a 
lot of people reported already. I don't see all apps in the VM manager and the 
lights indicating a working app do only appear or disappear when clicking an 
app. Sometimes I forget an app is still running.
VPN apps I created don't appear in the VM manager at all, so I do need to use 
CLI.

Having a working devices tray icon would be nice, though.

-- 
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/fa424de1-e570-44c8-b6e7-101ab0b37781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-19 Thread 'Антон Чехов' via qubes-users
On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner wrote:
> On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner wrote:
> > Hi all,
> > 
> > After a recent reboot, the devices and VM tray icons no longer are 
> > appearing on boot in Xfce. I have no idea what might have caused this. 
> > There were no dom0 updates in the meantime. If I try to manually run them, 
> > e.g., python3 -mqui.tray.devices, I get the following:
> > 
> > ERROR:dbus.proxies.Introspect error on 
> > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
> > recipient disconnected from message bus without replying
> > 
> > Followed by a backtrace, the relevant part appears to be:
> > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 22, in 
> > 
> >DOMAINS = qui.models.qubes.DomainManager()
> > 
> > Any advice would be appreciated, since with no icons, I'm also not 
> > appearing to get notifications for devices and VM actions.
> > 
> > Best,
> > Daniel
> 
> Interesting discovery: this problem arose as a result of setting 
> qrexec_timeout on an arbitrary VM to a value larger than an INT32. So the 
> moral of the story: Don't try to set qrexec_timeout too high!
> 
> Daniel

Hello,

I am experiencing the same problem with the final version of 4.0 but I did not 
change a setting of qrexec_timeout. The device tray icon disappeared suddenly.

I am getting tons of "GTK error" when trying to run manually via "python3 
-mqui.tray.devices"?

So far I haven't been able to get the devices tray appear again but I can 
attach devices via command line.

Anyone having the same problem?

-- 
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/8fc3b326-1b29-4cc7-9272-4b56da7c804d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: ProtonMail bridge

2018-04-19 Thread 'Антон Чехов' via qubes-users
On Thursday, April 19, 2018 at 10:47:45 AM UTC+2, chipp...@gmail.com wrote:
> Hello,
>  I've installed the (beta) protonmail bridge for Linux in my personal VM 
> for use with Thunderbird.  It actually worked for a while, but recently, it 
> no longer would start up.  I cannot even manually install and start the 
> bridge.
> 
> Has anyone else experienced this?
> 
> I had not done any other installs or changes that could be associated with 
> the bridge not starting.
>   Part of my troubleshootin included going to the seperate directories 
> and removing the installed items from the original install, and removing the 
> directories that were created during the install, and then re-attempting a 
> fresh install - No Joy.
> 
> Any help/recommendations would be very much appreciated.
> 
> Thank you,
> Chip

Have you tried installing the bridge in a templateVM like debian9?
I have installed the bridge in both Qubes 3.2 and Qubes 4 in the template 
debian 9.
Then I created an app based on debian 9 called protonmail where I started the 
bridge and put all my credentials in and connected it to Thunderbird like 
described in their instructions. 

Worked well for me ever since. Updates have to be installed in the templateVM 
as well. It shouldn't be anything different from other programmes or scripts 
like tasket's VPN which should als be installed in a templateVM.I haven't tried 
fedora but I guess it would work. 

-- 
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/c8e3830d-84e6-43c0-8ac4-a3c5cbb92e51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2017-01-19 Thread Антон Чехов
On Thursday, January 19, 2017 at 6:33:30 PM UTC+1, Reg Tiangha wrote:
> On 2017-01-19 10:30 AM, Антон Чехов wrote:
> > On Thursday, January 19, 2017 at 6:11:19 PM UTC+1, Reg Tiangha wrote:
> >>> Ah, okay. Mine don't start anymore. They jump from green to yellow but 
> >>> the AppVM and templateVM don't start anymore. So I can't change anything 
> >>> in the template anymore which makes it unusable. 
> >>> I did everything by the book, like described by coldhak:
> >>> https://github.com/coldhakca/coldkernel
> >>> I tried the kernel mostly on debian based VM. I built mostly debian based 
> >>> apps after some time. Debian 8, that is. 
> >>>
> >>
> >> Hmm...do you get a qrexec error? This behaviour (in my experience)
> >> usually means that the u2mfm kernel module didn't get compiled or
> >> installed correctly. On Debian VMs, you need to make sure the kernel
> >> header package is installed first before the kernel image package to
> >> make sure that u2mfm is compiled and installed correctly and the proper
> >> initramfs file is generated.
> >>
> >> If you need to fix things in your template, you can switch back to a
> >> normal Qubes kernel using Qubes Manager, rather than using pvgrub2. The
> >> machine should come up fine after that and you can double-check your
> >> settings that way.
> >>
> >> So maybe retry compiling and installing the coldkernel again by pulling
> >> a fresh copy off of github and starting from scratch, and if things
> >> still don't work, try that again using a fresh template.
> > 
> > No qrexex error.
> > Re update: I meant both cases, like you assumed but primarily recompiling 
> > with changes to the coldkernel.config. I did all these steps again, like 
> > described. That includes update grub. I did have the same errors mentioned 
> > earlier in the thread. (/usr/sbin/grub-probe: error: cannot find a GRUB 
> > drive for /dev/mapper/dmroot.  Check your device.map.) but other than that 
> > everything looked fine. Something must have gone wrong. 
> > I will try again like you described. Thanks very much for your help and the 
> > tip with switching back to normal kernel...so obvious that I would have 
> > missed it.
> > 
> 
> Well, keep us posted on how it goes. To be fair, I'm still running
> 4.8.15 of the kernel and haven't had a chance to update it to 4.8.17 so
> there could very well be some issues with the latest version that I
> haven't encountered yet. My plan is to attempt the upgrade this weekend
> when I have more time to play around with things.

Will do. I used the latest kernel 4.8.17 and there were no problems until I 
recompiled so I guess it should work. I mostly run AppVM behind a proxyVM. I 
will try again and report how it went.

-- 
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/1fa9c6e5-2264-40ce-9483-832a563f9c0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2017-01-19 Thread Антон Чехов
On Thursday, January 19, 2017 at 6:11:19 PM UTC+1, Reg Tiangha wrote:
> > Ah, okay. Mine don't start anymore. They jump from green to yellow but the 
> > AppVM and templateVM don't start anymore. So I can't change anything in the 
> > template anymore which makes it unusable. 
> > I did everything by the book, like described by coldhak:
> > https://github.com/coldhakca/coldkernel
> > I tried the kernel mostly on debian based VM. I built mostly debian based 
> > apps after some time. Debian 8, that is. 
> > 
> 
> Hmm...do you get a qrexec error? This behaviour (in my experience)
> usually means that the u2mfm kernel module didn't get compiled or
> installed correctly. On Debian VMs, you need to make sure the kernel
> header package is installed first before the kernel image package to
> make sure that u2mfm is compiled and installed correctly and the proper
> initramfs file is generated.
> 
> If you need to fix things in your template, you can switch back to a
> normal Qubes kernel using Qubes Manager, rather than using pvgrub2. The
> machine should come up fine after that and you can double-check your
> settings that way.
> 
> So maybe retry compiling and installing the coldkernel again by pulling
> a fresh copy off of github and starting from scratch, and if things
> still don't work, try that again using a fresh template.

No qrexex error.
Re update: I meant both cases, like you assumed but primarily recompiling with 
changes to the coldkernel.config. I did all these steps again, like described. 
That includes update grub. I did have the same errors mentioned earlier in the 
thread. (/usr/sbin/grub-probe: error: cannot find a GRUB drive for 
/dev/mapper/dmroot.  Check your device.map.) but other than that everything 
looked fine. Something must have gone wrong. 
I will try again like you described. Thanks very much for your help and the tip 
with switching back to normal kernel...so obvious that I would have missed 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/a0fb61bd-c2bf-4ea7-b7e7-b9d32082e277%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2017-01-19 Thread Антон Чехов
On Thursday, January 19, 2017 at 5:43:56 PM UTC+1, Reg Tiangha wrote:
> On 2017-01-19 9:39 AM, Антон Чехов wrote:
> > On Thursday, January 19, 2017 at 5:25:00 PM UTC+1, Reg Tiangha wrote:
> >> On 2017-01-19 9:18 AM, Антон Чехов wrote:
> >>> On Wednesday, January 18, 2017 at 5:35:53 PM UTC+1, Reg Tiangha wrote:
> >>>> On 2017-01-18 7:14 AM, Антон Чехов wrote:
> >>>>> Hello,
> >>>>>
> >>>>> I am testing coldkernel and I have a few questions. Does or should it 
> >>>>> work with a vpn gateway? Do I have to change some config file or 
> >>>>> special permissions?
> >>>>> I did not use grsec much in the past so I am in the process of 
> >>>>> learning.. 
> >>>>> I could connect to my coldkernel appvm via vpn gateway after freshly 
> >>>>> compiling and starting the appvm. After reboot none of my coldkernel 
> >>>>> appvm is connecting to the internet via vpn gateway anymore but 
> >>>>> connecting to clearnet without a proxyvm.
> >>>>>
> >>>>
> >>>> To get the coldkernel working properly with net/proxyVMs and usbVMs, you
> >>>> need to add at least two more drivers to the kernel's .config file:
> >>>>
> >>>> CONFIG_XEN_BLKDEV_BACKEND=m  
> >>>> CONFIG_XEN_NETDEV_BACKEND=m  
> >>>>
> >>>> The easiest way to do that is to add those two lines to the
> >>>> coldkernel.config file *before* running "make qubes-guest"
> >>>
> >>> Thanks for your answer. I added the lines to the coldkernel.config and 
> >>> compiled the kernel again (in the existing coldkernel-template). Don't 
> >>> know if that's a mistake? Upon starting an appVM with coldkernel the VM 
> >>> pauses (yellow) and the log is giving me loads of this:
> >>> "grsec: denied priority change of process rtkit-daemon:1115 (...)"
> >>> This applies to the templateVM as well so I am asking myself what's best 
> >>> practice of updating the coldkernel template?
> >>> It is obvious that I don't know my way around grsec and I have to do more 
> >>> research into how to do things.
> >>>
> >>
> >> Yeah, I get that too. I think you can ignore it in the sense that the
> >> VMs will still work despite the error, although I don't know if there
> >> are really any adverse effects.
> >>
> >> I haven't tried to fix it myself, though, but I assume a PAX exception
> >> would need to be set for the daemon in order to "fix" it (not hard to
> >> do, but I lack the time to troubleshoot at the moment).
> >>
> >> What the rtkit-daemon is:
> >>
> >> "RealtimeKit is a D-Bus system service that changes the
> >> scheduling policy of user processes/threads to SCHED_RR (i.e. realtime
> >> scheduling mode) on request. It is intended to be used as a secure
> >> mechanism to allow real-time scheduling to be used by normal user
> >> processes."
> >>
> >> I don't know how it affects the operations of VMs though and whether or
> >> not it being denied by the grsec kernel is actually a big deal.
> > 
> > But I can't start neither the AppVm nor the template anymore so it is kind 
> > of a big deal, don't you think?
> > That's why I am asking how to update. 
> > Do I have to start over from scratch or should it work from the template? 
> > Apparently something went wrong although everything looked fine during the 
> > process of compiling.
> > 
> 
> My templates and AppVMs start up just fine despite having that error.
> What do you mean when you say yours don't? As in, they don't start up at
> all, or they do but the indicator on Qubes Manager for that VM is yellow
> instead of green and never changes even after the CPU usage drops to 0%?
> And what VMs are you running the kernel on? Are they Debian based or
> Fedora based? And what versions of those distros?

Ah, okay. Mine don't start anymore. They jump from green to yellow but the 
AppVM and templateVM don't start anymore. So I can't change anything in the 
template anymore which makes it unusable. 
I did everything by the book, like described by coldhak:
https://github.com/coldhakca/coldkernel
I tried the kernel mostly on debian based VM. I built mostly debian based apps 
after some time. Debian 8, that is. 

-- 
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/3a1a3a5d-10b8-4033-a085-da0f9bc9cb2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2017-01-19 Thread Антон Чехов
On Thursday, January 19, 2017 at 5:25:00 PM UTC+1, Reg Tiangha wrote:
> On 2017-01-19 9:18 AM, Антон Чехов wrote:
> > On Wednesday, January 18, 2017 at 5:35:53 PM UTC+1, Reg Tiangha wrote:
> >> On 2017-01-18 7:14 AM, Антон Чехов wrote:
> >>> Hello,
> >>>
> >>> I am testing coldkernel and I have a few questions. Does or should it 
> >>> work with a vpn gateway? Do I have to change some config file or special 
> >>> permissions?
> >>> I did not use grsec much in the past so I am in the process of learning.. 
> >>> I could connect to my coldkernel appvm via vpn gateway after freshly 
> >>> compiling and starting the appvm. After reboot none of my coldkernel 
> >>> appvm is connecting to the internet via vpn gateway anymore but 
> >>> connecting to clearnet without a proxyvm.
> >>>
> >>
> >> To get the coldkernel working properly with net/proxyVMs and usbVMs, you
> >> need to add at least two more drivers to the kernel's .config file:
> >>
> >> CONFIG_XEN_BLKDEV_BACKEND=m
> >> CONFIG_XEN_NETDEV_BACKEND=m
> >>
> >> The easiest way to do that is to add those two lines to the
> >> coldkernel.config file *before* running "make qubes-guest"
> > 
> > Thanks for your answer. I added the lines to the coldkernel.config and 
> > compiled the kernel again (in the existing coldkernel-template). Don't know 
> > if that's a mistake? Upon starting an appVM with coldkernel the VM pauses 
> > (yellow) and the log is giving me loads of this:
> > "grsec: denied priority change of process rtkit-daemon:1115 (...)"
> > This applies to the templateVM as well so I am asking myself what's best 
> > practice of updating the coldkernel template?
> > It is obvious that I don't know my way around grsec and I have to do more 
> > research into how to do things.
> > 
> 
> Yeah, I get that too. I think you can ignore it in the sense that the
> VMs will still work despite the error, although I don't know if there
> are really any adverse effects.
> 
> I haven't tried to fix it myself, though, but I assume a PAX exception
> would need to be set for the daemon in order to "fix" it (not hard to
> do, but I lack the time to troubleshoot at the moment).
> 
> What the rtkit-daemon is:
> 
> "RealtimeKit is a D-Bus system service that changes the
> scheduling policy of user processes/threads to SCHED_RR (i.e. realtime
> scheduling mode) on request. It is intended to be used as a secure
> mechanism to allow real-time scheduling to be used by normal user
> processes."
> 
> I don't know how it affects the operations of VMs though and whether or
> not it being denied by the grsec kernel is actually a big deal.

But I can't start neither the AppVm nor the template anymore so it is kind of a 
big deal, don't you think?
That's why I am asking how to update. 
Do I have to start over from scratch or should it work from the template? 
Apparently something went wrong although everything looked fine during the 
process of compiling.

-- 
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/9d5a2e68-04a0-406a-bdd1-fcc3e96fe0fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Question to Mirage OS firewall users

2017-01-19 Thread Антон Чехов
On Thursday, January 19, 2017 at 1:07:17 AM UTC+1, Reg Tiangha wrote:
> On 2017-01-18 7:30 AM, Антон Чехов wrote:
> > Hi!
> > 
> > Is anyone using the mirage firewall in connection with a proxyVM? How do 
> > you configure it properly? Does it handle qubes-firewall-users-scripts?
> > 
> 
> I've run a Mirage-based firewall both in front of and behind a
> firewallVM and they chain together fine. Mirage Firewall in its current
> iteration does *not* respect modifications to firewall rules via Qubes
> and has to be inputted manually (there are some instructions on how to
> do that on the software author's blog). It isn't to say that Mirage
> Firewall couldn't do it one day, but I believe the author of the code is
> leaving it up as an exercise for the reader. Maybe he'll get around to
> implementing it, or maybe not, but from a purely technical standpoint,
> there's no reason why it couldn't be modified to work with Qubes
> firewall user scripts, it's just that it hasn't been implemented yet.
> 
> Note that even if you're running the latest code off of GitHub,
> currently, Mirage Firewall still doesn't work correctly with DispVMs (or
> at least, I haven't been able to get it to work; the DispVM connects to
> it, but there's no traffic), even though there were some minimal fixes
> applied to try to handle how it handles IP addresses from a different
> pool. Works fine with AppVMs, though, as well as TemplateVMs, at least
> in my experience.

@Reg & Willy
Thank you for sharing your experiences and the advice. I will try to wrap my 
head around this topic.
I have been trying the firewall with an AppVM already and it looked like it was 
working fine but I have to dig deeper into the process (for my understanding). 

-- 
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/00f397a6-f227-4051-8c93-02a566c91887%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2017-01-19 Thread Антон Чехов
On Wednesday, January 18, 2017 at 5:35:53 PM UTC+1, Reg Tiangha wrote:
> On 2017-01-18 7:14 AM, Антон Чехов wrote:
> > Hello,
> > 
> > I am testing coldkernel and I have a few questions. Does or should it work 
> > with a vpn gateway? Do I have to change some config file or special 
> > permissions?
> > I did not use grsec much in the past so I am in the process of learning. 
> > I could connect to my coldkernel appvm via vpn gateway after freshly 
> > compiling and starting the appvm. After reboot none of my coldkernel appvm 
> > is connecting to the internet via vpn gateway anymore but connecting to 
> > clearnet without a proxyvm.
> > 
> 
> To get the coldkernel working properly with net/proxyVMs and usbVMs, you
> need to add at least two more drivers to the kernel's .config file:
> 
> CONFIG_XEN_BLKDEV_BACKEND=m   
> CONFIG_XEN_NETDEV_BACKEND=m   
> 
> The easiest way to do that is to add those two lines to the
> coldkernel.config file *before* running "make qubes-guest"

Thanks for your answer. I added the lines to the coldkernel.config and compiled 
the kernel again (in the existing coldkernel-template). Don't know if that's a 
mistake? Upon starting an appVM with coldkernel the VM pauses (yellow) and the 
log is giving me loads of this:
"grsec: denied priority change of process rtkit-daemon:1115 (...)"
This applies to the templateVM as well so I am asking myself what's best 
practice of updating the coldkernel template?
It is obvious that I don't know my way around grsec and I have to do more 
research into how to do things.

-- 
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/e6cd4016-2852-4cdd-a044-d7b8df34cb9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Error while updating the default Archlinux Community template

2017-01-07 Thread Антон Чехов
On Saturday, January 7, 2017 at 5:42:56 PM UTC+1, anti-...@re-gister.com wrote:
> Hello @all!
> 
> I installed the default arch community template using,
> 
> sudo qubes-dom0-update --enablerepo=qubes-templates-community 
> qubes-template-archlinux
> 
> But when I click on the update button I get an error:
> 
> ::Synchronizing package databases...
> 
> error: failed retrieving file 'core.db' from mirrors.kernel.org : Resolving 
> timed out after 10524 milliseconds
> 
> error: failed to update core (download library error)
> 
> error: failed retrieving file ...
> 
> Although the Template VM is connected to the sys-firewall...
> 
> Appreciate any help!

You have to go to VM Settings in Qubes VM Manager -> Firewall rules -> Allow 
full access for 5 or more (depends on your connection) minutes. Now you can 
update via update vm system in Qubes VM Manager.

-- 
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/df96eb83-145f-402c-9038-5c03fe0f4da0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes 3.2 Dom0 no longer updating.

2017-01-06 Thread Антон Чехов
On Friday, January 6, 2017 at 2:58:00 PM UTC+1, john.david.r.smith wrote:
> On 06/01/17 13:15, Opal Raava wrote:
> > Hi all,
> >
> > Since about a week or so, I'm unable to update dom0 the way I used to. The 
> > VM Manager will tell me there are updates available for Dom0, and when I 
> > click 'Update VM' I see the familiar 'downloading updates' but after that 
> > the window with the updates never appears.
> >
> > If I run qubes-dom0-update it tells me 'No updates available'
> >
> > Does this perhaps have to do with fedora23/fedora24 issues? I asked on IRC 
> > and one person is having this issue as well. Is anybody else having this 
> > issue?
> >
> i have the same issue

I noticed that as well. I usually updated via terminal and it doesn't seem to 
work at the moment.

-- 
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/76224964-0c80-4dff-ae89-a044daa65a29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: [Win7-HVM] Problems with disk space

2016-12-29 Thread Антон Чехов
On Friday, December 30, 2016 at 1:18:23 AM UTC+1, entr0py wrote:
> Did you see this page? https://www.qubes-os.org/doc/resize-disk-image/
> 
> Scroll down to #HVM disk image, Windows 7. You need to grow the volume from 
> within the guest OS after allocating space via dom0.


I did see it but I missed the important part about adjusting within the guest 
OS ("diskmgmt.msc"). Sorry. There I found the 20GB of unallocated space.
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/dfcd071f-d8b0-493b-9bfe-abc62b4930da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Install windows 7 in HVM template on HP Zbook 15

2016-12-27 Thread Антон Чехов
Here is the solution, it works fine:
https://github.com/QubesOS/qubes-issues/issues/2488

After installing with custom-config, the VM did not get stuck again. I was done 
at #9. 

Best regards

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


[qubes-users] Re: [Win7-HVM] Problems with disk space

2016-12-27 Thread Антон Чехов
I managed to free additional disk space by right-clicking on my drive, 
selecting "Properties" and "compress all files". That way I could install the 
latest Windows Tools. Qubes Private Image is now correctly displayed with 
29.9GB of space, but the local disk drive (C:) is still at 19.8GB. If someone 
could tell me what I might miss/do, it would be appreciated. 

Updates are working fine but not until I did the following (I have Win7 
Professional with SP1):
-deactivate updates
-install internet explorer 11
-install Windows6.1-KB3172605-x64




-- 
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/a9544b94-b8c1-4d2b-bfab-c897086cb72d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] [Win7-HVM] Problems with disk space

2016-12-27 Thread Антон Чехов
Hello,

I installed a Win7 HVM template like described in the docs. It's working fine 
but there is one thing I can't work out yet. I have now assigned 40GB of max 
system storage and 30GB of max private storage. I started with the original 
settings. Opening the appvm, my disk shows only 19.8GB of disk space with 
almost all of the space being used. 
Starting WinUpdate I cannot install most of it because there is only 500Mb of 
free space.

I checked the space as to the docs regarding increasing disk size for VM. 
Everything seems to be okay.

Anything I can do, to have more space available?

PS: Windows Tools didn't seem to have installed, but I wanted to sort out the 
problems with disk space at first.

Thanks for taking the time to read.

-- 
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/7724f8a5-d8ba-4da7-86a7-6039d97181c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.