[qubes-users] Re: VPN up/down pop up not working?

2021-06-17 Thread 'b17b7bdb' via qubes-users
On 2021-06-17 07:42, Sven Semmler wrote:
> Do you have a notification daemon installed? If unsure, install and
> run dunst and see if it works then.

I don't know if there is a similar daemon in CentOS, but Debian-minimal 
requires an xfce specific package for the vpn status notifications to work:

apt-get install xfce4-notifyd

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

-- 
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/6PBTCYSMwbJafcFXYMGMsWkCL0Cd5TqQNKEXwke9G7UfAC3jlMtaR7lYXTB0jzth9NvJoi8feE_Fr_q4IqodLX4NkU7LTaUFL9VTKBXfzQo%3D%40protonmail.ch.


[qubes-users] Re: Known issue: Qubes extension not yet working with Thunderbird 78

2021-05-18 Thread 'b17b7bdb' via qubes-users
On 5/18/21 2:57 PM, lama...-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> I just got a new extension version 2.0.6 in both my Fedora and Debian
> VM's. Doesn´t seem to have fixed the 78 compatibility yet, and I can´t
> find on github what is new in version 2.0.6.
>
I was wondering the same thing and checked github. Sounds like it will be a few 
months yet.. Learned a nice workaround thanks to @SvenSemmler though, which 
doesn't appear to be posted to this group yet. Here it is:

- Navigate to Preferences > General in Thunderbird and scroll down to Files and 
Attachments.
- For each file type select the Action "Use Other" and then select the file 
/usr/bin/qvm-copy-to-dvm

Double clicking on an attached file with one of these file types will now 
automatically open in a new dispVM.

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

-- 
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/Z2cV5LMzVZhXvQFLCVOheN6edP3MscXW4KkPhhtyDZ41EYPPgIUY-6IVZP2yaYEqlpkgoy8V1HxNBPra4PVq8FTrWVmTkYL71ZxbwnYzb48%3D%40protonmail.ch.


[qubes-users] Re: Tunderbird in new anon-whonix is refusing to connect to internet

2020-09-26 Thread 'b17b7bdb' via qubes-users
>'awokd' via qubes-users:
>> taran1s:
>>> Hi, I am stuck with the following Thunderbird issue.
>>>
>>> I created new anon-whonix AppVM where I would like to have my new email
>>> account in Thunderbord, but whatever I do, I get "Could not connect to
>>> server xxx connection was refused" immediately after clicking the Get
>>> Messages. At the same time, TB can nicely connect to the network from
>>> that AppVM.
>>>
>>> Thunderbird in older anon-whonix AppVMs are connecting just ok. The
>>> settings are precisely the same in both - the old and new anon-whonix.
>>> The template is the same whonix-ws-15.
>>>
>>> I tried to create anon-whonix through salt or directly from the Qube
>>> Manager with Create a new qube, but still the same issue.
>>>
>>> Any idea how to solve this?
>>
>> From your new anon-whonix AppVM, test using a different app like regular
>> Firefox and see if it can connect to the Internet. Also, verify its
>> NetVM is set to sys-whonix.
>>
>
>As I mention, TB in the anon-whonix AppVM is able to connect to the
>internet, except Thunderbird. All email account settings are ok. The
>same settings are working in the old anon-whonix AppVM just well.
>

I had a similar issue recently with anon-whonix Thunderbird refusing to connect 
to the internet. I simply changed the manual proxy settings 
(Preferences>Network & Disk Space>Connection Settings) from the default of 
127.0.0.1 port 9102 to 127.0.0.1 port 9150, which restored the connection.

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

-- 
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/Yhu-Emxz-kOJnSAJSl6BpaM8AOH-MLwxlKE2_uksqRWKCB5Hb-gbxgRfQi65Em5dZqzbb73esBS3u8s3hNlX_mi8JVWsVqUdP2XoydYWMnM%3D%40protonmail.ch.


[qubes-users] Re: How to use curl in a template VM?

2019-11-08 Thread 'b17b7bdb' via qubes-users
On 11/8/19 5:59 PM, billollib-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:> I 
am trying to install the Brave browser in my debian template VM it
> requires that I add a repository with the command:
>
> curl -s
> https://brave-browser-apt-beta.s3.brave.com/brave-core-nightly.asc |
> sudo apt-key --keyring /etc/apt/trusted.gpg.d/brave-browser-beta.gpg add -
>
> When I try the first part of this alone, I get nothing back, so I'm
> assuming that curl is blocked -- I get the correct key in the
> "untrusted" vm when I do it there.
>
> I have to say that I am still trying to get my head around how qubes does 
> networking, but while I can easily upgrade and add software in the debian 
> template vM using apt, it seems that curl is not getting through.
>
> So:
>
> 1) Is there a document that goes through the networking stuff in detail?
> 2) How would I go about installing this software in the template?

I just installed Brave in Debian Buster following the steps in:
  
https://medium.com/@connorrfin10/how-to-install-brave-browser-on-debian-10-buster-f95c9d30556c

First I cloned my template as debian-10-brave, so that I wouldn't mess up one 
of my regular templates.  In order to execute the curl and echo commands in 
Step 1: Preparing for installation, I temporarily enabled sys-whonix as the 
NetVM for this template, but set it back to the default none setting for NetVM 
immediately afterward.  Not ideal, but it solves problem above.

Note, in Step 4: Final Fixes, I had to open the terminal as root in order to 
execute the echo command.  From the dom0 terminal:
$  qvm-run -u root debian-10-brave xterm

then type in the command manually into the debian-10-brave root terminal.

-- 
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/bXCOgs5pACoBfMIDfWMASwk9iyz59mGGDmFxAbVuYBRvD_-0alEtmACg946lV_0DXutQHeHXlTkWsjig29xCSSKVg-nosBdKi59q2PAQ4oA%3D%40protonmail.ch.


[qubes-users] Re: Whonix Tor Browser Starter safest setting fails

2019-09-13 Thread 'b17b7bdb' via qubes-users
‐‐‐ Original Message ‐‐‐
On Friday, September 13, 2019 5:16 PM, b17b7bdb <> wrote:

> On 9/13/19 9:31 AM, 'awokd' via qubes-users wrote:> 'b17b7bdb' via 
> qubes-users:
>>> Setting tb_security_slider_safest=true (either by selecting Yes in the Tor 
>>> Browser Starter screen or by creating a line in 
>>> /etc/torbrowser.d/50_user.conf) does not result in the expected behavior.
>>
>>> Actual Behavior:
>>> - Shield icon is fully colored
>>> - Security Level is set to Safest in about:preferences#privacy
>>> - JavaScript is ALLOWED on selected sites.
>>> To view these sites click on the NoScript Preferences button in the 
>>> about:addons page and then select the Per-Site Permissions tab.
>>>
>> When I do this in a fresh DispVM with the above setting, I see no sites
>> listed on the Per-Site Permissons tab. Are you using a disposable VM?
>>
>
> That's correct.  I observed the same behavior in the Whonix DispVMs on two 
> different machines, one of which is a fresh (and updated) install of R4.0.1.  
> Notably, if I manually set the security level to safer in 
> about:preferences#privacy then the per-site permissions disappear.
>
> These permissions are clearly the default permissions included with no-script 
> add-on.  For example, a variety of google, microsoft, yahoo, paypal, and 
> netflix sites are default trusted, among others.

> We might be miscommunicating. I'm saying when I set
> /etc/torbrowser.d/50_user.conf with tb_security_slider_safest=true and
> start a new DispVM (on current-testing), I see zero sites listed. Did
> you add the setting in whonix-ws-15 template? I tried it in the DVM
> template first, but it didn't stick. I do see what you mean with about
> 30 sites listed when I start a DispVM (on a different client on current)
> without that setting. Is your Tor Browser 8.5? Odd that you're
> experiencing different behavior. Might want to mention on qubes-whonix
> forum too.
>

Yes, I created /etc/torbrowser.d/50_user.conf in the whonix-ws-15 template and 
added the line tb_security_slider_safest=true, which persisted across all 
DispVMs.  Everything worked as expected, no TB starter window and js was 
disabled for all sites, except for the per-site permissions listed as trusted 
by no-script.  I observed the same behavior after commenting out the line and 
choosing yes in the starter window.  Both machines have TB 8.5.5 installed.  It 
is indeed surprising that we're observing different behaviors.

(Btw, my apologies if this creates another new thread.  Not sure how to get 
around this since I'm not able to respond directly in protonmail.)

-- 
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/PMtFoDg5HNlRT-9u1RcVMLW93gD1uyX_fVzQsqwTIihKWiS1TdYUD-waqpg0LsdNub8QR0wvUVwAD3hvlcKwunqBtW-66qMbcn-tb9Oeb8s%3D%40protonmail.ch.


[qubes-users] Re: Whonix Tor Browser Starter safest setting fails

2019-09-13 Thread 'b17b7bdb' via qubes-users
On 9/13/19 9:31 AM, 'awokd' via qubes-users wrote:> 'b17b7bdb' via qubes-users:
>> Setting tb_security_slider_safest=true (either by selecting Yes in the Tor 
>> Browser Starter screen or by creating a line in 
>> /etc/torbrowser.d/50_user.conf) does not result in the expected behavior.
>
>> Actual Behavior:
>> - Shield icon is fully colored
>> - Security Level is set to Safest in about:preferences#privacy
>> - JavaScript is ALLOWED on selected sites.
>> To view these sites click on the NoScript Preferences button in the 
>> about:addons page and then select the Per-Site Permissions tab.
>>
> When I do this in a fresh DispVM with the above setting, I see no sites
> listed on the Per-Site Permissons tab. Are you using a disposable VM?
>

That's correct.  I observed the same behavior in the Whonix DispVMs on two 
different machines, one of which is a fresh (and updated) install of R4.0.1.  
Notably, if I manually set the security level to safer in 
about:preferences#privacy then the per-site permissions disappear.

These permissions are clearly the default permissions included with no-script 
add-on.  For example, a variety of google, microsoft, yahoo, paypal, and 
netflix sites are default trusted, among others.

-- 
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/rfw47hJPVkOO1jkWxDuue2dwqS3Ga3MJkphci1lXAbxY_lXjy7xxwUcizvnkjAMADJeN7MYVw2-eArkTaZgKDLZYcwRjgDTafZWpoSljk4M%3D%40protonmail.ch.


[qubes-users] Whonix Tor Browser Starter safest setting fails

2019-09-12 Thread 'b17b7bdb' via qubes-users
Setting tb_security_slider_safest=true (either by selecting Yes in the Tor 
Browser Starter screen or by creating a line in /etc/torbrowser.d/50_user.conf) 
does not result in the expected behavior.

Expected Behavior:
- Shield icon is fully colored
- Security Level is set to Safest in about:preferences#privacy
- JavaScript is disabled by default on ALL sites

Actual Behavior:
- Shield icon is fully colored
- Security Level is set to Safest in about:preferences#privacy
- JavaScript is ALLOWED on selected sites.
To view these sites click on the NoScript Preferences button in the 
about:addons page and then select the Per-Site Permissions tab.

-- 
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/YhL10GmrV7yk0L2xjHpqblDZ8yRK2dMGORVtHSpv4GdicmT9kfLoUtMvy8eXlPMRNRUrtCIm8ckxrJMuNrLcCamWqdOHHoyLf9yDL8F7WAg%3D%40protonmail.ch.


Re: [qubes-users] qubes-tunnel service fails in VPN ProxyVM

2019-05-29 Thread 'b17b7bdb' via qubes-users


‐‐‐ Original Message ‐‐‐
On Wednesday, May 29, 2019 1:33 AM, Chris Laprise <> wrote:

> On 5/28/19 8:44 PM, 'b17b7bdb' via qubes-users wrote:
>
> > I set up a VPN gateway in a ProxyVM using the qubes-tunnel service, but
> > the service fails after restarting the VM.
> > journalctl -u qubes-tunnel shows the failure happening after:
> > ... qtunnel-setup[663]: -su: notify-send: command not found
> > ... systemd[1]: qubes-tunnel.service: Control process exited.
> > code=exited status=127
> > the command:  /usr/lib/qubes/qtunnel-setup --config
> > worked fine, so I'm not sure what's going awry.  fwiw, I had the same
> > setup working in R3.2, but started from scratch in R4.0.1.  I downloaded
> > the github project and installed it in the template VM before completing
> > the following instructions in the ProxyVM:
> > https://github.com/tasket/qubes-doc/blob/tunnel/configuration/vpn.md#set-up-a-proxyvm-as-a-vpn-gateway-using-the-qubes-tunnel-service
>
> It seems like the notify-send command is missing in the templatevm. I
> recommend not using minimal templates, and for now avoid fedora-29
> (fedora-28 and debian are OK).
>

I was indeed using a debian-9-minimal clone.  After customizing the full 
debian-9 template my ProxyVM is now working fine.  Thanks for the spot on 
advice and for all of your work on qubes, which is much 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 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/I2O0BOYqToGQynAUGK8uTeKMLRP_2zhMN2uYGJcp0-pwg4Zn3Vp1h3hDLNJYxZydJtdQ6h6GRZUNQvq0TAv4EuJalXXSXLY3-ckHCIexrHk%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] qubes-tunnel service fails in VPN ProxyVM

2019-05-28 Thread 'b17b7bdb' via qubes-users
I set up a VPN gateway in a ProxyVM using the qubes-tunnel service, but the 
service fails after restarting the VM.
journalctl -u qubes-tunnel shows the failure happening after:
... qtunnel-setup[663]: -su: notify-send: command not found
... systemd[1]: qubes-tunnel.service: Control process exited. code=exited 
status=127

the command:  /usr/lib/qubes/qtunnel-setup --config
worked fine, so I'm not sure what's going awry.  fwiw, I had the same setup 
working in R3.2, but started from scratch in R4.0.1.  I downloaded the github 
project and installed it in the template VM before completing the following 
instructions in the ProxyVM:
https://github.com/tasket/qubes-doc/blob/tunnel/configuration/vpn.md#set-up-a-proxyvm-as-a-vpn-gateway-using-the-qubes-tunnel-service

-- 
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/3voGBReT1G57oqJvBCbSloJrWsuryNYAYKe7p2Kq0RaXllYqs5xHrmJhHMjtsl-Wol1ncidoA-akXsoFbWXFG5aPJpWRhsohXhypBHSFYOE%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.