[qubes-users] Re: QSB #46: APT update mechanism vulnerability

2019-01-26 Thread John S.Recdep
On 1/26/19 6:41 PM, Aly Abdellatif wrote:
> @John S.cde
> 
> 1. Go into sys-firewall and delete rpms available in 
> /var/lib/qubes/dom0-updates/packages
> 
> and then in dom0 use sudo qubes-dom0-update qubes-template-whonix-gw-14
> --enablerepo=qubes*testing --clean   
> 
> 

there is nothing in that dir/  (in sys-firewall) nor  in sys-net
/packagesbut  it seems removing them from /var/lib/qubes/updates/rpm
  fixed   the diskquota  error 



on an interesting note folks over at other distros  like  linuxmint seem
wholly unconcerned with reinstall and seem certainthat just
upgrading apt is all that is necessary



when I mentioned that recent comment  in this thread  about  "stolen
keys"  I am asked for a reference for this, and accused of FUD   :)

I am not a SA, so that comment would be very serious if true correct ?

-- 
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/9886bfcb-7e87-85b6-c8c2-46eb6a7d5499%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: QSB #46: APT update mechanism vulnerability

2019-01-26 Thread John S.Recdep
On 1/26/19 9:30 AM, Aly Abdellatif wrote:
> @John S redcap
> 
> Go into the updateVM and delete unneeded rpms :
> /var/lib/qubes/dom0-updates/packages
> 
> If you didnt change your updateVM, it will be in sys-firewall
> 
> And then add  - - clean in your qubes-dom0-update 
> Command
> 


hmm, this is a /var/lib/qubes/updates/rpm/directory with 4 rpm in it
(2 whonix-gw one is the 2018, one the 2019, 1 deb-9 2019 and 1 whonix-ws
 2018)

(there is no /var/lib/qubes/dom0-updatesjust  /updatesin this
4.0-> 4.1 install)


suppose that is the one,  not sure what you mean  by  sys-firewall being
"it"

so something like
sudo qubes-dom0-update qubes-template-whonix-gw-14
--enablerepo=qubes*testing --clean ??

after deleting the 4 template rpms in /rpm  ?

-- 
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/7b32a9e8-4b82-88ba-48ad-56dec611c6a3%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: QSB #46: APT update mechanism vulnerability

2019-01-25 Thread John S.Recdep
On 1/26/19 5:22 AM, John S.Recdep wrote:
> 
> When I remove the whonix templates I get about 12 errors complaining
> about /var/lib/qubes/vm-templates/whonix-ws-14/app.tempicons
>   /vm-whitelisted-appmenus.list
> 
> etc
> 
> no such file or directory
> 
> 
> I suppose just another one of those  mystery errors to ignore ?
> 



sh**t now I am getting the correct whonix 2019 started but it fails with
 "Disk quota exceeded"dnf clean packages  0 files removed   so what
now  please

-- 
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/760d0277-ca5b-0c63-b58d-5ce08cc4890b%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: QSB #46: APT update mechanism vulnerability

2019-01-25 Thread John S.Recdep
somewhere in this large thread it probably states there is an error in
the original whonix install invocation right ?

if one just uses community-testing they end up with 2018 version

so use the --enablerepo=qubes*testing   instead  

-- 
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/04b3d0f9-034a-1675-c41b-7a5f070b9bd8%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: QSB #46: APT update mechanism vulnerability

2019-01-25 Thread John S.Recdep


When I remove the whonix templates I get about 12 errors complaining
about /var/lib/qubes/vm-templates/whonix-ws-14/app.tempicons
  /vm-whitelisted-appmenus.list

etc

no such file or directory


I suppose just another one of those  mystery errors to ignore ?

-- 
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/dc4a2f0f-b966-0339-f88f-9e1b2112c6f0%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: [qubes-devel] QSB #46: APT update mechanism vulnerability

2019-01-25 Thread John S.Recdep
On 1/23/19 9:52 PM, Chris Laprise wrote:
> On 01/23/2019 12:05 PM, Marek Marczykowski-Górecki wrote:
> 
>> Patching
>> =
>>
>> If you are a Qubes user, you should remove all APT-based (including
>> Debian and Whonix) TemplateVMs and StandaloneVMs, then install fresh
>> ones. You can do this by performing the following steps on each such
>> TemplateVM:
> 
> 
> A shortened update procedure for debian-9:
> 
> 1. If your "debian-9" template is customized or contains data, you may
> wish to back it up with qvm-clone first...
> 
> [dom0]$ qvm-clone debian-9 d9-backup
> 
> 2. Run the upgrade command...
> 
> [dom0]$ sudo qubes-dom0-update qubes-template-debian-9 \
> --enablerepo=qubes*testing --action=upgrade
> 
> This will display package info as it begins downloading. The package
> version-date should begin with "4.0.1-20190123" or later.
> 
> 3. Shutdown all VMs so the upgrade can take effect...
> 
> [dom0]$ qvm-shutdown --all --wait --timeout=30
> 
> This method also works with whonix-gw-14 and whonix-ws-14 templates.
> 

Tasket,

Does this mean that a upgrade to testing  is as good as   uninstalling -
re-installing templates ?

I guess your cloning debian-9-nonpatch'd just in case the upgrade fails
, which you'd rather do  than  reinstall  fresh clean
debian-9-new-apt-version?


btw, somewhere in this thread I think I saw  howto  find which debian-9
 useradded  packages  were installed,  but maybe someone could confirm
how please

rec

-- 
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/b1fca1c4-4c8f-9dfc-b79c-906904141b65%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: clock nightmare

2019-01-25 Thread John S.Recdep
On 1/24/19 6:11 AM, haaber wrote:
> Hello, could someone please help me out of the clock nightmare? dom0
> keeps setting itself at -1day, and helpless sys-whonix follows, which
> disturbs tor, the time stamp of this email ETC.
> Concrete question: in which timezone should live  respectively dom0  and
> whonix-* ? How/Where do I configure TZ without messing all up? Thank
> you, Bernhard
> 

I know this may not be the solution you want, but I ended up just
changing sys-net template to debian-9   , then all was well

I did the change to the  private/  dir  but so far haven't tested it fwiw

-- 
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/9cec4c99-7f58-76c4-19a3-cb12d3d1d4fc%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: [qubes-devel] QSB #46: APT update mechanism vulnerability

2019-01-23 Thread John S.Recdep
On 1/23/19 9:08 PM, gone wrote:
> unfortunately the reboot brought no change. Still the
> 201812091508 version.
> 


this is for Fedora, is there something akin to this for  Debian ?


--
What you can do to get the differences between two templates:

1) run "dnf list installed > packagelist1.txt
Do the same in the other VM

2) compare both lists:
grep -Fxv -f packagelist1.txt packagelist2.txt



The problem with that is that it outputs version numbers, which isnt
particularly helpful.
dnf repoquery --qf "%{name}" --userinstalled
Will give you just the names.
--

-- 
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/6924c217-3eb9-0cb6-1560-b626bbccdcb8%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: USB Keyboard

2019-01-20 Thread John S.Recdep
On 1/20/19 10:16 PM, kitchm-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org wrote:
> Upon reading the system requirements and recommendations, I read the 
> statement "A non-USB keyboard or multiple USB controllers".  Please explain 
> the reasoning there.  Thank you.
> 
> 
so, what level did you want an explanation?  I assume your aware of the
risk of putting a USB thumbdrive/flashdrive  into your  computer?

if so, that is basically the  simple  answer

-- 
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/4a2eeb61-e1dc-93c9-b81b-1235d8f36b5e%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: dom0 clock keeps resetting to wrong time again

2019-01-19 Thread John S.Recdep
On 1/14/19 9:55 PM, John S.Recdep wrote:
> On 1/14/19 10:10 AM, John S.Recdep wrote:
>> Hello,
>>
>> I believe my Bios time is UTC
>>
>> qubes-prefs shows my clockvm  as sys-net
>>
>> I have been trying to use sudo date --set <"localtime TZ">  to get my
>> dom0 correct.  Which it does but within 30-60  it is changing to another
>> TZ I don't recognize
>>
>> I have also tried  qvm-sync-clock  ,  and tried a qubes group search as
>> I remember fighting this out many times   with whonix  issues , however
>>
>> I am at a loss what to do further to problem-solve fix this  ,
>> appreciate your help
>>
>>
>> maybe I can switch the template for sys-net back to fedora-28 instead of
>> -29  . ?
>>
> 
> 1-14-19
> 
> changing the clockvm to fed-28 and rerunning qvm-sync-clock did nothing
> BUT*  changing sys-net to debian-9  and qvm-sync-clock  fixed it   sigh
> 
> case anyone else gets this issue again ; prolly will fix whonixcheck
> complaints if any as well
> 
> 'solved'
> 

Must be related to this
https://github.com/QubesOS/qubes-issues/issues/3983

for myself it's not the  minimal fedora-29 its the regular one ; and it
appears if fedora-29 is having time issues  that  that may be why my
thunderbird appvm based on it,  is also  timestamping the messages wrong ?

-- 
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/0af706cf-9095-b6af-20b3-cb4ae592cc96%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: dom0 downloads, but does not update packages

2019-01-14 Thread John S.Recdep
On 1/14/19 6:07 PM, Ivan Mitev wrote:
> 
> 
> On 1/14/19 5:14 PM, meindatenschrott-re5jqeeqqe8avxtiumw...@public.gmane.org 
> wrote:
>> Had the same issue, just do "sudo dnf reinstall anaconda-core anaconda-gui 
>> ..." in dom0 and you're good to go. At least, that's what worked for me :-)
> 
> It worked for me, thanks !
> 
> Still wondering what caused that problem in the first place...
> 

mine magically disappeared  ; not sure if this had anything to do with
my fedora-29 sys-net  clock  issue  .. lol

-- 
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/2f871a42-afb6-340c-6b94-57402eff38ed%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: dom0 clock keeps resetting to wrong time again

2019-01-14 Thread John S.Recdep
On 1/14/19 10:10 AM, John S.Recdep wrote:
> Hello,
> 
> I believe my Bios time is UTC
> 
> qubes-prefs shows my clockvm  as sys-net
> 
> I have been trying to use sudo date --set <"localtime TZ">  to get my
> dom0 correct.  Which it does but within 30-60  it is changing to another
> TZ I don't recognize
> 
> I have also tried  qvm-sync-clock  ,  and tried a qubes group search as
> I remember fighting this out many times   with whonix  issues , however
> 
> I am at a loss what to do further to problem-solve fix this  ,
> appreciate your help
> 
> 
> maybe I can switch the template for sys-net back to fedora-28 instead of
> -29  . ?
> 

1-14-19

changing the clockvm to fed-28 and rerunning qvm-sync-clock did nothing
BUT*  changing sys-net to debian-9  and qvm-sync-clock  fixed it   sigh

case anyone else gets this issue again ; prolly will fix whonixcheck
complaints if any as well

'solved'

-- 
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/78758e3e-d21c-83c0-a1c4-29ee767f1d5d%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] dom0 clock keeps resetting to wrong time again

2019-01-14 Thread John S.Recdep
Hello,

I believe my Bios time is UTC

qubes-prefs shows my clockvm  as sys-net

I have been trying to use sudo date --set <"localtime TZ">  to get my
dom0 correct.  Which it does but within 30-60  it is changing to another
TZ I don't recognize

I have also tried  qvm-sync-clock  ,  and tried a qubes group search as
I remember fighting this out many times   with whonix  issues , however

I am at a loss what to do further to problem-solve fix this  ,
appreciate your help


maybe I can switch the template for sys-net back to fedora-28 instead of
-29  . ?

-- 
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/d55807e7-39de-1845-810c-9fe9102c226b%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: sys-whonix-14 updates issues

2019-01-13 Thread John S.Recdep
On 1/13/19 6:24 AM, John S.Recdep wrote:
> On 1/13/19 8:01 AM, Mathew wrote:
>> Hello,
>>
>> Just to know if there is a solution for whonix-gw/whonix-ws updates ?
>> Noted that I can update/upgrade sys-whonix-14 without any problems ! I have 
>> to do it again after rebooting though.
>>
>> $ sudo apt-get-update-plus dist-upgrade
>> WARNING: Execution of /usr/bin/apt-get prevented by /etc/uwt.d/40_qubes.conf 
>> because no torified Qubes updates proxy found.
>>
>> Please make sure Whonix-Gateway (commonly called sys-whonix) is running.
>>
>> - If you are using Qubes R3.2: The NetVM of this TemplateVM should be set to 
>> Whonix-Gateway (commonly called sys-whonix).
>>
>> - If you are using Qubes R4 or higher: Check your _dom0_ 
>> /etc/qubes-rpc/policy/qubes.UpdatesProxy settings.
>>
>> _At the very top_ of that file.
>>
>> Should have the following syntax:
>> Name-Of-Whonix-TemplateVM $default 
>> allow,target=Whonix-Gateway-TemplateBased-ProxyVM
>>
>> Example entry for Whonix-Gateway TemplateVM:
>> whonix-gw-14 $default allow,target=sys-whonix
>>
>> Example entry for Whonix-Workstation TemplateVM:
>> whonix-ws-14 $default allow,target=sys-whonix
>>
>> Try running in Whonix-Gateway (commonly called sys-whonix):
>> sudo systemctl restart qubes-whonix-torified-updates-proxy-check
>>
>> If this warning message is transient, it can be safely ignored.
>>
>> Thanks !
>>
>> Regards,
>> Mathew
>>
> 
> 
> what is this all about, your telling people who may be having problems
> what to do, but your not having a problem? am confused
> 
> because I am unable to sudo apt-get update whonix-gw-14  which I am
> trying to do because it's complaining again about time issues, and the
> pop up suggestion doesn't fix the problemsigh
> 
user@host:~$ sudo apt-get update
Ign:1 http://deb.whonix.org stretch InRelease


Ign:2 http://security.debian.org stretch/updates InRelease


Ign:3 http://deb.qubes-os.org/r4.0/vm stretch InRelease

Ign:4 http://ftp.us.debian.org/debian stretch InRelease

Err:5 http://deb.whonix.org stretch Release


  500  Unable to connect
Err:6 http://ftp.us.debian.org/debian stretch Release


  500  Unable to connect
Err:7 http://security.debian.org stretch/updates Release

  500  Unable to connect
Err:8 http://deb.qubes-os.org/r4.0/vm stretch Release

  500  Unable to connect
Ign:9
tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion
stretch InRelease
Ign:10 tor+http://vwakviie2ienjx6t.onion/debian stretch InRelease
Ign:11 tor+http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease
Err:12 tor+http://sgvtcaew4bxjd7ln.onion stretch/updates Release
  Connection failed
Err:13
tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion
stretch Release
  Connection failed
Err:14 tor+http://vwakviie2ienjx6t.onion/debian stretch Release
  Connection failed
Reading package lists... Done
E: The repository 'http://deb.whonix.org stretch Release' does no longer
have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository 'http://ftp.us.debian.org/debian stretch Release' does
no longer have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository 'http://security.debian.org stretch/updates Release'
does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does
no longer have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository 'tor+http://sgvtcaew4bxjd7ln.onion stretch/updates
Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository
'tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion
stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
E: The repository 'tor+http://vwakviie2ienjx6t.onion/debian stretch
Release' does 

[qubes-users] Re: sys-whonix-14 updates issues

2019-01-13 Thread John S.Recdep
On 1/13/19 8:01 AM, Mathew wrote:
> Hello,
> 
> Just to know if there is a solution for whonix-gw/whonix-ws updates ?
> Noted that I can update/upgrade sys-whonix-14 without any problems ! I have 
> to do it again after rebooting though.
> 
> $ sudo apt-get-update-plus dist-upgrade
> WARNING: Execution of /usr/bin/apt-get prevented by /etc/uwt.d/40_qubes.conf 
> because no torified Qubes updates proxy found.
> 
> Please make sure Whonix-Gateway (commonly called sys-whonix) is running.
> 
> - If you are using Qubes R3.2: The NetVM of this TemplateVM should be set to 
> Whonix-Gateway (commonly called sys-whonix).
> 
> - If you are using Qubes R4 or higher: Check your _dom0_ 
> /etc/qubes-rpc/policy/qubes.UpdatesProxy settings.
> 
> _At the very top_ of that file.
> 
> Should have the following syntax:
> Name-Of-Whonix-TemplateVM $default 
> allow,target=Whonix-Gateway-TemplateBased-ProxyVM
> 
> Example entry for Whonix-Gateway TemplateVM:
> whonix-gw-14 $default allow,target=sys-whonix
> 
> Example entry for Whonix-Workstation TemplateVM:
> whonix-ws-14 $default allow,target=sys-whonix
> 
> Try running in Whonix-Gateway (commonly called sys-whonix):
> sudo systemctl restart qubes-whonix-torified-updates-proxy-check
> 
> If this warning message is transient, it can be safely ignored.
> 
> Thanks !
> 
> Regards,
> Mathew
> 


what is this all about, your telling people who may be having problems
what to do, but your not having a problem? am confused

because I am unable to sudo apt-get update whonix-gw-14  which I am
trying to do because it's complaining again about time issues, and the
pop up suggestion doesn't fix the problemsigh

-- 
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/c0b86093-4b26-6e0d-2164-440e595a831b%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: dom0 downloads, but does not update packages

2019-01-13 Thread John S.Recdep
On 1/13/19 11:04 AM, pixel fairy wrote:
> heres the output of qubes-dom0-update. it just stops after downloading. done 
> this for at least a week. 
> 
> Fedora 25 - x86_64  913 kB/s |  50 MB 00:56   
>  
> Qubes Dom0 Repository (updates) 686 kB/s | 8.0 MB 00:11   
>  
> determining the fastest mirror (15 hosts).. done..5 kB/s | 2.7 kB 00:00 
> ETA
> Qubes Templates repository  1.7 kB/s |  10 kB 00:06   
>  
> Last metadata expiration check: 0:00:01 ago on Sun Jan 13 12:53:10 2019.
> Dependencies resolved.
> 
>  Package  Arch   Version   Repository  
> Size
> 
> Reinstalling:
>  anaconda-corex86_64 1000:25.20.9-14.fc25  qubes-dom0-current 1.5 
> M
>  anaconda-gui x86_64 1000:25.20.9-14.fc25  qubes-dom0-current 386 
> k
>  anaconda-tui x86_64 1000:25.20.9-14.fc25  qubes-dom0-current 186 
> k
>  anaconda-widgets x86_64 1000:25.20.9-14.fc25  qubes-dom0-current 119 
> k
>  python3-blivet   noarch 2:2.1.6-5.fc25qubes-dom0-current 1.0 
> M
>  python3-kickstartnoarch 1000:2.32-4.fc25  qubes-dom0-current 370 
> k
>  qubes-anaconda-addon noarch 4.0.9-1.fc25  qubes-dom0-current  34 
> k
>  xorg-x11-drv-ati x86_64 18.0.1-1.fc25 qubes-dom0-current 168 
> k
>  xorg-x11-drv-intel   x86_64 2.99.917-32.20171025.fc25 qubes-dom0-current 696 
> k
> 
> Transaction Summary
> 
> 
> Total download size: 4.4 M
> Installed size: 4.4 M
> DNF will only download packages for the transaction.
> Downloading Packages:
> (1/9): anaconda-tui-25.20.9-14.fc25.x86_64.rpm  136 kB/s | 186 kB 00:01   
>  
> (2/9): anaconda-widgets-25.20.9-14.fc25.x86_64. 709 kB/s | 119 kB 00:00   
>  
> (3/9): anaconda-gui-25.20.9-14.fc25.x86_64.rpm  231 kB/s | 386 kB 00:01   
>  
> (4/9): python3-blivet-2.1.6-5.fc25.noarch.rpm   914 kB/s | 1.0 MB 00:01   
>  
> (5/9): python3-kickstart-2.32-4.fc25.noarch.rpm 367 kB/s | 370 kB 00:01   
>  
> (6/9): qubes-anaconda-addon-4.0.9-1.fc25.noarch 585 kB/s |  34 kB 00:00   
>  
> (7/9): anaconda-core-25.20.9-14.fc25.x86_64.rpm 543 kB/s | 1.5 MB 00:02   
>  
> (8/9): xorg-x11-drv-ati-18.0.1-1.fc25.x86_64.rp 512 kB/s | 168 kB 00:00   
>  
> (9/9): xorg-x11-drv-intel-2.99.917-32.20171025. 1.1 MB/s | 696 kB 00:00   
>  
> 
> Total   860 kB/s | 4.4 MB 00:05   
>   
> Complete!
> The downloaded packages were saved in cache until the next successful 
> transaction.
> You can remove cached packages by executing 'dnf clean packages'.
> Qubes OS Repository for Dom0   27 MB/s |  37 kB 00:00 
>
> 


ya I've got same thing except mine is just the two python  packages,  I
posted here, but no one  seems to have  answered  my query

this persists through reboot of the 4.0.1  system


now I am having whonix-14-gw  unable to update as well, though, doubtful
they are related

-- 
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/679cffec-1703-5c38-acf5-a54c34c8a9b8%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1

2019-01-11 Thread John S.Recdep
On 1/11/19 8:08 AM,
scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> Hello,
> 
> I am a new user to Qubes and I like it very much.
> 
> I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 templates. 
>  Below are the errors for both:
> 
> Fedora-29:
> 
> Fedora Modular 29 - x86_64
> Error: Failed to synchronize cache for repo 'fedora-modular'
> Done.
> 
> Debian-9 (snippet):
> 
> Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release
>   500 Unable to connect
> Err:6 https://deb.debian.org/debian stretch Release
>   Received HTTP code 500 from proxy after CONNECT
> Err:7 https://deb.debian.org/debian-security stretch/updates Release
>   Received HTTP code 500 from proxy after CONNECT
> Err:8 https://deb.debian.org/debian jessie-backports Release
>   Received HTTP code 500 from proxy after CONNECT
> E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no 
> longer have a Release file.
> E: The repository 'https://deb.debian.org/debian stretch Release' does no 
> longer have a Release file.
> E: The repository 'https://deb.debian.org/debian-security stretch/updates 
> Release' does no longer have a Release file.
> E: The repository 'https://deb.debian.org/debian jessie-backports Release' 
> does no longer have a Release file.
> 
> TIA
> 

try doing it via a terminal in the templates

$sudo dnf update

$sudo apt-get update
sudo apt-get dist-upgrade

fwiw for myself, the qubes manager fails or is so slow I only use it to
make appvms or change/add applications  lately


so I guess this is a new install of yours?

-- 
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/cd0a9206-336a-3512-7124-b42d1607d69b%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: dom0 update: sys-whonix: command failed with code: 1

2019-01-10 Thread John S.Recdep
On 1/8/19 9:19 AM, John S.Recdep wrote:
> On 1/2/19 8:20 AM, John S.Recdep wrote:
>> On 1/1/19 12:29 PM, qubes-fan-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org 
>> wrote:
>>> Hi, during dom0 update I get following output:
>>>
>>> $ sudo qubes-dom0-update
>>> Using sys-whonix as UpdateVM to download updates fro dom0; this may take 
>>> some time...
>>> sys-whonix: command failed with code: 1
>>> No new updates available
>>> Qubes OS Repository for Dom0  23 MB/s | 52 kB
>>>
>>> The update than goes as normal. What does that mean and is there any action 
>>> needed from my side?
>>>
>>
>> ditto here except mine is sys-net  code:1
>>
>> fwiw
>>
> 
> 
> Is this also in testing  or  can someone help / advise a fix to this ?
> my updatevm per qubes-prefs is sys-net   but I always thought that other
> file had it set up to use  sys-whonix-14
> 
> haven't had any issues with previous  qubes updates
> 
> I am running
> $sudo qubes-dom0-update  and getting
> 
> 
> 
> Using sys-net as UpdateVM to download updates
> 
> sys-net: command failed with code: 1
> 
> 
> Last metadata expiration check: 0:09:40 ago on Tue Jan  8 08:59:27 2019.
> 
> Dependencies resolved.
> 
> 
> 
>  Package  Arch  Version Repository
>Size
> 
> 
> 
> Reinstalling:
> 
>  python3-blivet   noarch2:2.1.6-5.fc25  qubes-dom0-current
>   1.0 M
> 
>  python3-kickstartnoarch1000:2.32-4.fc25qubes-dom0-current
>   370 k
> 
> 
> 
> Transaction Summary
> 
> 
> 
> 
> 
> Total size: 1.3 M
> 
> Installed size: 1.3 M
> 
> DNF will only download packages for the transaction.
> 
> Downloading Packages:
> 
> [SKIPPED] python3-blivet-2.1.6-5.fc25.noarch.rpm: Already downloaded
> 
> 
> [SKIPPED] python3-kickstart-2.32-4.fc25.noarch.rpm: Already downloaded
> 
> 
> Complete!
> 
> The downloaded packages were saved in cache until the next successful
> transaction.
> 
> You can remove cached packages by executing 'dnf clean packages'.
> 
> 


Sorry what exactly does this mean ?  After reboot, it now says it is
reinstalling   the two python packages and "saved in cache until "

no code 1 message, but I've never seen this before when running


sudo qubes-dom0-update



-- 
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/ef644b45-d17b-0e91-4ec5-1d9974c42b86%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: dom0 update: sys-whonix: command failed with code: 1

2019-01-08 Thread John S.Recdep
On 1/2/19 8:20 AM, John S.Recdep wrote:
> On 1/1/19 12:29 PM, qubes-fan-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org 
> wrote:
>> Hi, during dom0 update I get following output:
>>
>> $ sudo qubes-dom0-update
>> Using sys-whonix as UpdateVM to download updates fro dom0; this may take 
>> some time...
>> sys-whonix: command failed with code: 1
>> No new updates available
>> Qubes OS Repository for Dom0  23 MB/s | 52 kB
>>
>> The update than goes as normal. What does that mean and is there any action 
>> needed from my side?
>>
> 
> ditto here except mine is sys-net  code:1
> 
> fwiw
> 


Is this also in testing  or  can someone help / advise a fix to this ?
my updatevm per qubes-prefs is sys-net   but I always thought that other
file had it set up to use  sys-whonix-14

haven't had any issues with previous  qubes updates

I am running
$sudo qubes-dom0-update  and getting



Using sys-net as UpdateVM to download updates

sys-net: command failed with code: 1


Last metadata expiration check: 0:09:40 ago on Tue Jan  8 08:59:27 2019.

Dependencies resolved.



 Package  Arch  Version Repository
   Size



Reinstalling:

 python3-blivet   noarch2:2.1.6-5.fc25  qubes-dom0-current
  1.0 M

 python3-kickstartnoarch1000:2.32-4.fc25qubes-dom0-current
  370 k



Transaction Summary





Total size: 1.3 M

Installed size: 1.3 M

DNF will only download packages for the transaction.

Downloading Packages:

[SKIPPED] python3-blivet-2.1.6-5.fc25.noarch.rpm: Already downloaded


[SKIPPED] python3-kickstart-2.32-4.fc25.noarch.rpm: Already downloaded


Complete!

The downloaded packages were saved in cache until the next successful
transaction.

You can remove cached packages by executing 'dnf clean packages'.


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


[qubes-users] Re: fed29 templates/upgrade

2019-01-05 Thread John S.Recdep
On 1/4/19 2:34 AM, unman wrote:
> dnf repoquery --qf "%{name}" --userinstalled

this works then using the grep command

of interesting note is that of the few packages found is pulseaudio-qubes

which I think I accidentally autoremoved and had to reinstall so maybe
it got a new name or package name, but doesn't mean I must install it
again in fed-29 template

-- 
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/7bf1bd60-986f-2823-e963-1d0b5dfd8427%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: fed29 templates/upgrade

2019-01-05 Thread John S.Recdep
On 1/5/19 12:26 AM, 799 wrote:
> Hello,
> 
> Am Sa., 5. Jan. 2019, 05:01 hat John S.Recdep 
> 
> geschrieben:
> 
>> [...]
>> BTW all: no luck with the suggested methods of determining what extra
>> packages I may have installed in the fedora-28 Template . but I'll
>> just live with the fresh fedora-29 template
> 
> 
> I had the same problem and that's why I am setting up my templates only via
> scripts which I can run from dom0.
> This improves speed to rebuild templates and also I know exactly what I
> have installed.
> 
> What you can do to get the differences between two templates:
> 
> 1) run "dnf list installed > packagelist1.txt
> Do the same in the other VM
> 
> 2) compare both lists:
> grep -Fxv -f packagelist1.txt packagelist2.txt
> 
> - O
> 

I'm running this in fed-28 terminal and fed-29 template terminal ; mv
file2 to the other template  but your grep cmd is just showing a list of
all packages, maybe because of the version update numerical changes ...
guess I can look back at previous post of how to remove the version
change numbers, if it might matter

-- 
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/46304afe-f53d-1c09-6849-d0edd4cfeb1a%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: fed29 templates/upgrade

2019-01-04 Thread John S.Recdep
On 1/4/19 5:00 PM, Andrew David Wong wrote:
> On 1/4/19 1:13 PM, John S.Recdep wrote:
>> On 1/4/19 1:37 AM, Andrew David Wong wrote:
>>> On 1/3/19 11:31 PM, John S.Recdep wrote:
>>>> On 1/3/19 2:51 PM,
>>>> 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:
>>>>> Thanks 799...I learned something!
>>>>>
>>>>> Similar to 799 but less hardcore...I always download a fresh 
>>>>> template(vs upgrade). In my case I ran with a full/fresh 
>>>>> Fedora-29 after the Fedora-28 hplip issues, and added any
>>>>> new software from fresh:
>>>>>
>>>>> https://www.qubes-os.org/doc/templates/
>>>>>
>>>
>>>
>>>> hmm, ok let's say I just use the new fresh 29 template, is
>>>> there some way that I can know what non-stock software I
>>>> installed on my Fedora-28 template, as I can't remember all
>>>> that I may have installed 
>>>
>>>
>>> This is more of a Fedora question than a Qubes question. As far
>>> as I know, there isn't a clean way to do this. Following Marek's
>>> advice from years ago, I just keep a list of the packages that I
>>> install in each of my templates.
>>>
>>>
>>>> So, no advice on upgrading from my 28 template at this time? I
>>>> find it strange that the template is in the dom0 updates
>>>> available, but I see no notice  in the news section on qubes
>>>> website nor here ..
>>>
>>>
>>> See:
>>>
>>> https://github.com/QubesOS/qubes-issues/issues/4223
>>>
>>> and
>>>
>>> https://github.com/QubesOS/qubes-doc/pull/739
> 
>> So, Andrew does this mean that although the Fedora-29 Template is 
>> available via sudo qubes-dom0-update  that it still has issues and
>> hence it is not officially advisable to use it ? ( whether via
>> 'fresh' d/l nor 'upgrades' ? )
> 
>> Forgive me, am just a layman, not sure what I would expect to
>> interpret from the github links (perhaps the fact that there are
>> any issues provides the answer?)
> 
>> My repos are just the default qubes 4.0+ versions
> 
> 
> Well, you said you found it strange that there was no documentation or
> announcement for the Fedora 29 template. These links show why: the
> documentation is still being worked on, and the necessary steps prior to
> the announcement have not yet been completed. (In fact, at the time of
> this writing, the issue still indicates that the template has not yet
> migrated to the stable repo, which appears to be false.)
> 
> In order to avoid this sort of confusion in the future, perhaps we
> should refrain from migrating new templates to the stable repo until
> documentation and an announcement are ready to be published, then do
> it all simultaneously. What do you think, Marek?
> 
> 

OK understood, thx for the clarification.


BTW all: no luck with the suggested methods of determining what extra
packages I may have installed in the fedora-28 Template . but I'll
just live with the fresh fedora-29 template

-- 
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/ecccbac3-75a7-31d0-c181-db9e172e6a72%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: fed29 templates/upgrade

2019-01-04 Thread John S.Recdep
On 1/4/19 1:37 AM, Andrew David Wong wrote:
> On 1/3/19 11:31 PM, John S.Recdep wrote:
>> On 1/3/19 2:51 PM, 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org
>> wrote:
>>> Thanks 799...I learned something!
>>>
>>> Similar to 799 but less hardcore...I always download a fresh
>>> template(vs upgrade). In my case I ran with a full/fresh
>>> Fedora-29 after the Fedora-28 hplip issues, and added any new
>>> software from fresh:
>>>
>>> https://www.qubes-os.org/doc/templates/
>>>
> 
> 
>> hmm, ok let's say I just use the new fresh 29 template, is there
>> some way that I can know what non-stock software I installed on my
>> Fedora-28 template, as I can't remember all that I may have
>> installed 
> 
> 
> This is more of a Fedora question than a Qubes question. As far as I
> know, there isn't a clean way to do this. Following Marek's advice
> from years ago, I just keep a list of the packages that I install in
> each of my templates.
> 
> 
>> So, no advice on upgrading from my 28 template at this time? I find
>> it strange that the template is in the dom0 updates available, but
>> I see no notice  in the news section on qubes website nor here
>> ..
> 
> 
> See:
> 
> https://github.com/QubesOS/qubes-issues/issues/4223
> 
> and
> 
> https://github.com/QubesOS/qubes-doc/pull/739

So, Andrew does this mean that although the Fedora-29 Template is
available via sudo qubes-dom0-update  that it still has issues and hence
it is not officially advisable to use it ? ( whether via 'fresh' d/l nor
'upgrades' ? )

Forgive me, am just a layman, not sure what I would expect to interpret
from the github links (perhaps the fact that there are any issues
provides the answer?)

My repos are just the default qubes 4.0+ versions



-- 
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/a7ea5b94-5d94-0b0e-7125-8f66092507ba%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: fed29 templates/upgrade

2019-01-03 Thread John S.Recdep
On 1/3/19 2:51 PM, 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:
> Thanks 799...I learned something!
> 
> Similar to 799 but less hardcore...I always download a fresh template(vs 
> upgrade). In my case I ran with a full/fresh Fedora-29 after the Fedora-28 
> hplip issues, and added any new software from fresh:
> 
> https://www.qubes-os.org/doc/templates/
> 


hmm, ok let's say I just use the new fresh 29 template, is there some
way that I can know what non-stock software I installed on my Fedora-28
template, as I can't remember all that I may have installed 


So, no advice on upgrading from my 28 template at this time? I find it
strange that the template is in the dom0 updates available, but I see no
 notice  in the news section on qubes website nor here ..


Seems like this happened with 28 release as well

-- 
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/c2b28fdf-7ae8-e7cc-216d-6f70977aef12%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] fed29 templates/upgrade

2019-01-03 Thread John S.Recdep
Hello, since there are now templates available with dom0 for fedora-29
does that mean one could also upgrade from 28->29   safely in a
similar/same way  as say from 26->27 27->28  etc

please advise


PS: could you plz remind me what the qvm command was to determine which
templates are available via  sudo dom0 update?

-- 
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/afb3ab54-44fd-60c6-51a8-7d48aa23f419%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Split gpg is just too cool.

2019-01-02 Thread John S.Recdep
On 12/26/18 4:49 AM,
brendan.hoar-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> On Tuesday, December 25, 2018 at 9:56:40 PM UTC-5, John Smiley wrote:
>> U2F Proxy is not so cool. So far no joy getting it to work. Someone on reddit
>> had similar issues and questions and resolved by installing USB keyboard
>> support. That’s not mentioned in the Qubes docs and I hope we don’t have to
>> resort to that.
> 
> I haven't yet tried the U2F proxy, it is on my todo list.
> 
> I'm also not quite so happy about the complexity of getting a security 
> focused device (yubikey) working with a security focused OS (QubesOS). 
> 
> I believe I understand the nature of the yubikey problem, though: Qubes is 
> engineered to protect you from untrusted peripherals...and this somewhat 
> conflicts with the design of yubikeys on multiple fronts: we want to use 
> yubikeys across multiple VMs (using devices across VMs increases risk); 
> yubikeys are composite USB devices, which means they often have multiple 
> endpoints for different functions (HID keyboard plus, CCID 
> smartcard/javacard, U2F) which makes securely proxying them more complex; and 
> for those who have serious safety risks, a fake yubikey could destroy one's 
> opsec in multiple ways...even a real one could if you are not careful with 
> your usage.
> 
> In my case, I have decided to somewhat compromise QubesOS security a bit and 
> disable the USB/HID keyboard protections in Qubes dom0 for now so that I 
> could log into LastPass with my yubikey OTP in a couple of my VMs without too 
> much fiddling. I have kept notes on the changes and how to reverse them.
> 
> So, as I said above, I haven't addressed the U2F compatibility on my current 
> R4 build (but neither do I have a multipmedia VM set up with Chrome yet :) ). 
> So, I use my backup method of yubico authenticator on another device and type 
> in six-digit TOTP codes instead of using the U2F functionality.
> 
> Anyway, I suggest keeping a running log of modifications/configurations (both 
> TODO and done) somewhere easily accessible across devices (I use a google 
> doc) to speed future configurations/rebuilds. I don't keep anything that 
> needs to be secure there, just notes, simple scripts, etc.
> 
>> If that were a requirement, surely the docs would have
>> mentioned it.
> 
> Haha. Er, I mean, that *should* be the case... :)
> 
> Brendan
> 

I'd like to see your "notes" on the yubikey and lastpass,  as I long ago
gave up  on using my Yubikey in OTP mode, despite many trials 

I have the U2F proxy working it seems but just use it for 2FA for gmail
and such , lastpass I'm stuck using the Authenticator on a Mobile phone
. because I can't use the OTP

my qubes system has a USB -> PS/2  converter, I might run qubes on
another computer but it has no PS/2  port and I fear botching the
sys-usb and getting locked out of the install again . so I don't try

-- 
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/c85ee45a-b685-c6d3-0fc4-f4a6a9120af0%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 4.0 UEFI Installation not recognizing

2019-01-02 Thread John S.Recdep
On 1/1/19 12:14 PM,
brandonmaytham06-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> Hi all,
> 
> I have a new PC and I want to setup Qubes with UEFI however after the install 
> with UEFI the HDD isn't detected.
> 
> If I change to legacy/UEFI the HDD shows I have seen the article which says 
> to edit the boot loader file however there never seems to be that file on any 
> USB I make.
> 

What is your "new" hardware?

please post the URL link or "the article"

and what "file"

-- 
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/940b27ad-39c3-1a43-6fda-79f4081d8cca%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: dom0 update: sys-whonix: command failed with code: 1

2019-01-02 Thread John S.Recdep
On 1/1/19 12:29 PM, qubes-fan-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org wrote:
> Hi, during dom0 update I get following output:
> 
> $ sudo qubes-dom0-update
> Using sys-whonix as UpdateVM to download updates fro dom0; this may take some 
> time...
> sys-whonix: command failed with code: 1
> No new updates available
> Qubes OS Repository for Dom0  23 MB/s | 52 kB
> 
> The update than goes as normal. What does that mean and is there any action 
> needed from my side?
> 

ditto here except mine is sys-net  code:1

fwiw

-- 
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/442de159-48d6-85da-71f3-15954a6cfdb5%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: hplib complaint with fedora-28 qube manager update , what to do?

2018-12-31 Thread John S.Recdep
On 12/31/18 3:50 AM,
brendan.hoar-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> On Monday, December 31, 2018 at 5:07:06 AM UTC-5, unman wrote:
>> On Sun, Dec 30, 2018 at 06:15:32PM -1000, John S.Recdep wrote:
>>> Hello,
>>>
>>> The following below was/is after using a manually opened xterm that
>>> successfully runs  $sudo dnf update
>>> and closing the template/s 
>>>
>>>
>>> The Qubes Manager is showing green dots on the Fed-28 (Q4.0.1?)
>>> templates  needing update but:
>>>
>>> when I use the QManager to update I am seeing some complaint about  hplip
>>>
>>> I tried to highlight and copy it but any clicking in the xterm and it
>>> disappears .
>>>
>>> start a terminal for the template gives me this:
>>>
>>> [user@fedora-28 ~]$ sudo dnf upgrade
>>> Last metadata expiration check: 4:24:34 ago on Sun 30 Dec 2018 01:46:31
>>> PM HST.
>>> Dependencies resolved.
>>>
>>>  Problem 1: cannot install the best update candidate for package
>>> hplip-3.18.6-7.fc28.x86_64
>>>   - nothing provides libnetsnmp.so.35()(64bit) needed by
>>> hplip-3.18.6-11.fc28.x86_64
>>>  Problem 2: cannot install the best update candidate for package
>>> hplip-libs-3.18.6-7.fc28.x86_64
>>>   - nothing provides libnetsnmp.so.35()(64bit) needed by
>>> hplip-libs-3.18.6-11.fc28.x86_64
>>>  Problem 3: cannot install the best update candidate for package
>>> libsane-hpaio-3.18.6-7.fc28.x86_64
>>>   - nothing provides libnetsnmp.so.35()(64bit) needed by
>>> libsane-hpaio-3.18.6-11.fc28.x86_64
>>>  Problem 4: package hplip-libs-3.18.6-7.fc28.x86_64 requires
>>> hplip-common(x86-64) = 3.18.6-7.fc28, but none of the providers can be
>>> installed
>>>   - cannot install both hplip-common-3.18.6-11.fc28.x86_64 and
>>> hplip-common-3.18.6-7.fc28.x86_64
>>>   - problem with installed package hplip-libs-3.18.6-7.fc28.x86_64
>>>   - cannot install the best update candidate for package
>>> hplip-common-3.18.6-7.fc28.x86_64
>>>   - nothing provides libnetsnmp.so.35()(64bit) needed by
>>> hplip-libs-3.18.6-11.fc28.x86_64
>>> 
>>>  PackageArchVersion
>>> RepositorySize
>>> 
>>> Skipping packages with conflicts:
>>> (add '--best --allowerasing' to command line to force their upgrade):
>>>  hplip-common   x86_64  3.18.6-11.fc28
>>> updates  110 k
>>> Skipping packages with broken dependencies:
>>>  hplip  x86_64  3.18.6-11.fc28
>>> updates   16 M
>>>  hplip-libs x86_64  3.18.6-11.fc28
>>> updates  204 k
>>>  libsane-hpaio  x86_64  3.18.6-11.fc28
>>> updates  127 k
>>>
>>> Transaction Summary
>>> 
>>> Skip  4 Packages
>>>
>>> Nothing to do.
>>> Complete!
>>>
>>
>> It's an upstream bug: net-snmp-libs is still in testing. You can wait
>> for it to reach stable or run (as suggested)
>> dnf --best --allowerasing --enablerepo=updates-testing update hplip
>>
>> Keep an eye out to see if anything is being removed.
> 
> ...and if anything qubes-* related is removed, dnf install those packages 
> *before* restarting the template.
> 
> (yes, I've been burned by that before)
> 
> Brendan
> 


If it doesn't effect security or break anything I can wait.

BTW, in the past I've never done  $sudo dnf upgrade   is this
really necessary?

Have always wondering if the scheme was similar to the debian
dist-upgrade   , which Does seem to be required but somehow on Fedora
seems it might not be ?



Lastly, is Fedora-29  going to be officially recommended as a upgrade
sometime / somewhere soon ?


regards, recdep

-- 
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/25d68827-dfad-a974-ea0a-ceee232cb61a%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] hplib complaint with fedora-28 qube manager update , what to do?

2018-12-30 Thread John S.Recdep
Hello,

The following below was/is after using a manually opened xterm that
successfully runs  $sudo dnf update
and closing the template/s 


The Qubes Manager is showing green dots on the Fed-28 (Q4.0.1?)
templates  needing update but:

when I use the QManager to update I am seeing some complaint about  hplip

I tried to highlight and copy it but any clicking in the xterm and it
disappears .

start a terminal for the template gives me this:

[user@fedora-28 ~]$ sudo dnf upgrade
Last metadata expiration check: 4:24:34 ago on Sun 30 Dec 2018 01:46:31
PM HST.
Dependencies resolved.

 Problem 1: cannot install the best update candidate for package
hplip-3.18.6-7.fc28.x86_64
  - nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-3.18.6-11.fc28.x86_64
 Problem 2: cannot install the best update candidate for package
hplip-libs-3.18.6-7.fc28.x86_64
  - nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-libs-3.18.6-11.fc28.x86_64
 Problem 3: cannot install the best update candidate for package
libsane-hpaio-3.18.6-7.fc28.x86_64
  - nothing provides libnetsnmp.so.35()(64bit) needed by
libsane-hpaio-3.18.6-11.fc28.x86_64
 Problem 4: package hplip-libs-3.18.6-7.fc28.x86_64 requires
hplip-common(x86-64) = 3.18.6-7.fc28, but none of the providers can be
installed
  - cannot install both hplip-common-3.18.6-11.fc28.x86_64 and
hplip-common-3.18.6-7.fc28.x86_64
  - problem with installed package hplip-libs-3.18.6-7.fc28.x86_64
  - cannot install the best update candidate for package
hplip-common-3.18.6-7.fc28.x86_64
  - nothing provides libnetsnmp.so.35()(64bit) needed by
hplip-libs-3.18.6-11.fc28.x86_64

 PackageArchVersion
RepositorySize

Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 hplip-common   x86_64  3.18.6-11.fc28
updates  110 k
Skipping packages with broken dependencies:
 hplip  x86_64  3.18.6-11.fc28
updates   16 M
 hplip-libs x86_64  3.18.6-11.fc28
updates  204 k
 libsane-hpaio  x86_64  3.18.6-11.fc28
updates  127 k

Transaction Summary

Skip  4 Packages

Nothing to do.
Complete!

-- 
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/4b8be1e4-7abb-d740-a26b-0ddefc95473d%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-02 Thread John S.Recdep
On 9/29/18 4:12 PM, 'Setherson' via qubes-users wrote:
> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime 
> within the past week.
> 
> Since about the same time, my Workstation TemplateVM and every AppVM based on 
> it has been unable to connect to the internet.
> 
> The Whonix Gateway TemplateVM works fine, as does the sys-whonix NetVM. 
> Furthermore, all the AppVMs based on the Fedora and Debian templates work 
> even when routed through sys-whonix. I also have all the TemplateVMs set to 
> update through sys-whonix, and every one of them is able to do this with the 
> sole exception of whonix-ws-14. So if I had to guess, I’d say the problem 
> lies with the Whonix Workstation TemplateVM itself.
> 
> When I try updating whonix-ws-14, it “hits” everything until the 10th 
> repository. Once it gets there, the screen shows “[working]” and stays there.
> 
> Has anyone else run into this problem? What steps can I take to begin 
> troubleshooting it?
> 
> Thanks in advance!
> 

OK looks solved

https://forums.whonix.org/t/unable-to-connect-to-internet-from-within-whonix-workstation-based-appvms-qubes-3-2/6092/5

issue was autoremove  removed the workstation  , sigh

sudo apt-get install qubes-whonix-workstation   which looks to be about
1000 packages  LOL

-- 
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/b5c78007-e964-5d6a-ddb4-52ee030b28bd%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: qubes-u2f not installing on templates

2018-10-02 Thread John S.Recdep
On 9/26/18 9:48 AM, paigemarie-sgozh3hwpm2stnjn9+b...@public.gmane.org
wrote:
> 
>  
>> All u2f-related packages area already in stable repository (since
>> yesterday), so the above is not needed anymore.
> 
> When I run `sudo apt install qubes-u2f` in my Debian template or `sudo dnf 
> install qubes-u2f` in my Fedora template, I get errors about not being able 
> to locate or match the package.
> 
> I was able to install the dom0 package.
> 
> I'm using Qubes v3.2
> 

Debian-9 and
Fedora-28  Templates ?

-- 
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/570134bb-5491-9852-a7c9-88311c5d11cd%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread John S.Recdep
On 10/1/18 10:13 AM, 'Setherson' via qubes-users wrote:
>> On Oct 1, 2018, at 3:18 AM, 'awokd' via qubes-users 
>>  wrote:
>>
>> 'Setherson' via qubes-users wrote on 9/30/18 2:12 AM:
>>
>>> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime 
>>> within the past week.
>>>
>>> Since about the same time, my Workstation TemplateVM and every AppVM based 
>>> on it has been unable to connect to the internet.
>>>
>>> The Whonix Gateway TemplateVM works fine, as does the sys-whonix NetVM. 
>>> Furthermore, all the AppVMs based on the Fedora and Debian templates work 
>>> even when routed through sys-whonix. I also have all the TemplateVMs set to 
>>> update through sys-whonix, and every one of them is able to do this with 
>>> the sole exception of whonix-ws-14. So if I had to guess, I’d say the 
>>> problem lies with the Whonix Workstation TemplateVM itself.
>>>
>>> When I try updating whonix-ws-14, it “hits” everything until the 10th 
>>> repository. Once it gets there, the screen shows “[working]” and stays 
>>> there.
>>>
>>> Has anyone else run into this problem? What steps can I take to begin 
>>> troubleshooting it?
>>>
>>> Thanks in advance!
>>
>> You might have caught a bad update last week, and it sounds like one of
>> the repositories you're using is unavailable right now. You can try the
>> suggestions in
>> https://forums.whonix.org/t/errors-updating-september-2018/6028/8, or
>> wait a day or so and try updating 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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/ez6zc...@public.gmane.org
>> To post to this group, send email to 
>> qubes-users-/JYPxA39Uh5TLH3MbocFF+G/ez6zc...@public.gmane.org
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/qubes-users/ffa818ac-b732-a43f-657f-b679dcb5ad93%40danwin1210.me.
>> For more options, visit https://groups.google.com/d/optout.
> 
> Thanks for the link! I did what they advised and the Workstation-14 
> TemplateVM seems to have updated fine.
> 
> However, the most serious issues remain.
> 
> I am still unable to access the internet from any of my Workstation-based 
> AppVMs. Here’s what happens:
> 
> When I first open the Tor Browser, I receive a warning that my activities may 
> be linked if the Tor Browser is already running. I have gotten this sort of 
> warning in the past when I already have an instance of the TB running, but 
> that’s not the case here.
> 
> I click “yes” to get rid of the warning box and the Tor Browser proceeds to 
> open. The first sign that something is (still) not right is that it’s unable 
> to find the local Whonix splash page file that always pops up when the 
> browser first starts. Weird, but certainly not a huge issue.
> 
> Then, when I try to do a random search (I use DDG’s Onion service to conduct 
> searches), I’m told that the server has reloaded while the request was being 
> made (or something to that effect; it’s a super-common error message). 
> Whatever the cause may be, the result is that I’m unable to visit any 
> website; Google, DDG Onion, DDG Clearnet, and so on all give me the same 
> error.
> 
> It occurred to me that this might be a Tor Browser problem, so I opened up 
> the Electrum bitcoin client in the same AppVM to see if that works. 
> Unfortunately, Electrum doesn’t connect either.
> 
> Then—again in the same AppVM—I open up konsole and ping google (both 
> google.com and 8.8.8.8): Interestingly, when I ping google.com the terminal 
> shows me the site’s corresponding numerical IPv4 address, so there must be 
> some sort of DNS access, right? Anyway, aside from seeing the IPv4 address I 
> get no feedback whatsoever for the next 20-30 seconds, so I finally Ctrl-C 
> the process and see a packet loss of 100%.
> 
> Finally, I open Firefox in my “Untrusted” AppVM, which uses Fedora 28 as its 
> template and sys-whonix as its NetVM. It takes me to Google without a hitch.
> 
> Any ideas? Is this just a bad update I’m going to have to wait out, or are 
> there steps I can take to remedy the situation in the meantime?
> 

Yes, exactly the same here,  commenting out allows update  but I've been
noticing these DDG .onion resets for maybe a week or more 

and just last few days , maybe because I haven't rebooted the AppVM for
a while  the  warning  about  activity "being linked" 

two other things: 1) the Qube manager despite sucessfully updates, the
green arrow to need update persists , even after restarting the Q
manager and
2) update-torbrowser gives a scary warning  in  whonix-ws-14 to
override it two options  , I haven't tried either ..

btw, this is all in Q4.0  with  the latest  dom0  patches , most recent
just a few days ago .


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To 

[qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread John S.Recdep
On 9/30/18 10:18 PM, 'awokd' via qubes-users wrote:
> 'Setherson' via qubes-users wrote on 9/30/18 2:12 AM:
>> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated
>> sometime within the past week.
>>
>> Since about the same time, my Workstation TemplateVM and every AppVM
>> based on it has been unable to connect to the internet.
>>
>> The Whonix Gateway TemplateVM works fine, as does the sys-whonix
>> NetVM. Furthermore, all the AppVMs based on the Fedora and Debian
>> templates work even when routed through sys-whonix. I also have all
>> the TemplateVMs set to update through sys-whonix, and every one of
>> them is able to do this with the sole exception of whonix-ws-14. So if
>> I had to guess, I’d say the problem lies with the Whonix Workstation
>> TemplateVM itself.
>>
>> When I try updating whonix-ws-14, it “hits” everything until the 10th
>> repository. Once it gets there, the screen shows “[working]” and stays
>> there.
>>
>> Has anyone else run into this problem? What steps can I take to begin
>> troubleshooting it?
>>
>> Thanks in advance!
> 
> You might have caught a bad update last week, and it sounds like one of
> the repositories you're using is unavailable right now. You can try the
> suggestions in
> https://forums.whonix.org/t/errors-updating-september-2018/6028/8, or
> wait a day or so and try updating again.
> 
> 

actually the method from the whonix forum still fails : (# commenting
out the 2  onion repo references

sudo apt-get dist-upgrade works but not  , as below

user@host:~$ sudo apt-get update
Hit:1 http://deb.whonix.org stretch InRelease

Hit:2 http://deb.qubes-os.org/r4.0/vm stretch InRelease

Hit:3 http://security.debian.org stretch/updates InRelease
Ign:4 http://ftp.us.debian.org/debian stretch InRelease
Hit:5 http://ftp.us.debian.org/debian stretch Release
Reading package lists... Done
E: The method driver /usr/lib/apt/methods/tor+http could not be found.
N: Is the package apt-transport-tor installed?
E: Failed to fetch
tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/dists/stretch/InRelease

E: Some index files failed to download. They have been ignored, or old
ones used instead.

-- 
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/7c777292-fdd6-0c1c-91b0-0334cb4e1a67%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Whonix-Workstation VM and associate AppVMs not connecting in Qubes 3.2

2018-10-01 Thread John S.Recdep
On 9/29/18 4:12 PM, 'Setherson' via qubes-users wrote:
> I am using Qubes 3.2. All TemplateVMs and dom0 have been updated sometime 
> within the past week.
> 
> Since about the same time, my Workstation TemplateVM and every AppVM based on 
> it has been unable to connect to the internet.
> 
> The Whonix Gateway TemplateVM works fine, as does the sys-whonix NetVM. 
> Furthermore, all the AppVMs based on the Fedora and Debian templates work 
> even when routed through sys-whonix. I also have all the TemplateVMs set to 
> update through sys-whonix, and every one of them is able to do this with the 
> sole exception of whonix-ws-14. So if I had to guess, I’d say the problem 
> lies with the Whonix Workstation TemplateVM itself.
> 
> When I try updating whonix-ws-14, it “hits” everything until the 10th 
> repository. Once it gets there, the screen shows “[working]” and stays there.
> 
> Has anyone else run into this problem? What steps can I take to begin 
> troubleshooting it?
> 
> Thanks in advance!
> 

yes, same here for many days now   Whonix-ws-14   dies  at Hit 8
ftp.us.debian.org/debian Stretch Release

-- 
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/c9f68fb4-3cd8-8996-9183-3fd6303bfe53%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Open in Qube 3.0 beta released!

2018-09-14 Thread John S.Recdep
On 09/14/2018 07:02 AM, 'Raffaele Florio' via qubes-users wrote:
> Dear Qubes community,
> I've released a new version of "Open in Qube" (aka qubes-url-redirector) 
> [v3.0_beta]. The repository is at [repo].
> This is a browser extension inspired by [gsoc idea] and it's written using 
> standard WebExtension APIs. Each customization is done via the browser 
> because it's highly integrated in it.
> 
> ### What does it do
> The extension allows you to choose which URLs are whitelisted in the browser, 
> with a lot of flexibility. Indeed you can specify allowed URLs also with 
> regular expression. Non whitelisted URLs are treated in a custom way: you can 
> choose to block them only, or to block and redirect them to a 
> specific/disposable qube. In this way unwanted/malicious URLs will not be 
> opened in the current browser, so in the current qube.
> Furthermore there are three context menu entry ([menu issue]) through which 
> you can choose how to handle specific link. Then there is the toolbar's popup 
> that allows you to whitelist a **specific** resource currently blocked in the 
> **active** tab. In the popup is indicated the URL and the type (i.e. image, 
> stylesheet, script, xhr and so on..) of each resource.
> In the repo there are some screenshot and other infos. Furthermore after the 
> first installation the browser will open a welcome page whose will guide you.
> 
> ### Installation
> Installation is really easy and it's covered in the [repo]. As you can see in 
> [contrib issue] its integration in Qubes OS is scheduled for the 4.1 release.
> 
> I hope that it will be useful to a lot of us and for whatever issue don't 
> hesitate to contact me! :D
> 
> [v3.0_beta] = 
> https://github.com/raffaeleflorio/qubes-url-redirector/releases/tag/v3.0_beta
> [gsoc idea] = 
> https://www.qubes-os.org/gsoc/#thunderbird-firefox-and-chrome-extensions
> [menu issue] = https://github.com/QubesOS/qubes-issues/issues/4105
> [contrib_issue] = https://github.com/QubesOS/qubes-issues/issues/3152
> [repo] = https://github.com/raffaeleflorio/qubes-url-redirector/
> 
> Best Regards,
> Raffaele.
> 
> 

Nice.

Can't quite understand how or why this would be used, though..?  am
sure it makes sense to the smart folks :)


here's my vote for whatever "gsoc idea" is , 'cause:

I wish I could click on a URL in ThunderbirdVM  and have it open a
whonix-dvm  by default  .  afaik there is no current way to do that.

-- 
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/4856f04f-8761-0c74-dcf5-63293134b3e4%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: "Introducing the Qubes U2F Proxy" by Wojtek Porczyk

2018-09-14 Thread John S.Recdep
On 09/12/2018 04:08 AM, Ivan Mitev wrote:
> 
> 
> On 9/12/18 4:33 PM, Sergio Matta wrote:
>> Em terça-feira, 11 de setembro de 2018 13:38:09 UTC-3, Brendan Hoar  
>> escreveu:
>>> On Tuesday, September 11, 2018 at 5:18:49 AM UTC-4, Andrew David Wong wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 Dear Qubes Community,

 Wojtek Porczyk has just published a new article titled "Introducing
 the Qubes U2F Proxy." The article is available on the Qubes website:

 https://www.qubes-os.org/news/2018/09/11/qubes-u2f-proxy/
>>>
>>> *FANTASTIC*. Thanks, this is very useful.
>>>
>>> Brendan
>> Good news, thank you. But sudo dnf install qubes-u2f results not found on 
>> fedora-28 repo. Please check.
> 
> It is in the current-testing repo:
> 
> dnf --enablerepo=qubes-vm-r4.0-current-testing install qubes-u2f
> 
> (same goes for dom0 - only the current testing repo name is different)
> 


...and it will move out of "testing"  in about 2 weeks to the main
repo  like security updates ?

...so for the cautious what till then ?

-- 
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/f30c2eec-29f8-0b93-737b-ea5cedf05385%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Strange sys-whonix-14 starts ; /etc/qubes-rpc/policy/qubes.UpdatesProxy

2018-09-07 Thread John S.Recdep
On 09/07/2018 12:48 AM, 'awokd' via qubes-users wrote:
> On Thu, September 6, 2018 8:19 pm, John S.Recdep wrote:
>> On 09/06/2018 02:45 AM, 'awokd' via qubes-users wrote:
>>
>>> On Wed, September 5, 2018 12:21 am, John S.Recdep wrote:
>>>
>>>> Hello,
>>>>
>>>>
>>>>
>>>> while upgrading to sys-whonix-14 many weeks ago, I was fighting to
>>>> maintain  my Fedora and Debian Template to keep using sys-net  not
>>>> sys-whonix-14
>>>>
>>>> and sys-whonix-gw and -ws to use sys-whonix-14  , which are otherwise
>>>>  working fine and I hesitate to mess with
>>>> /etc/qubes-rpc/policy/qubes.UpdatesProxy
>>>>
>>>>
>>>>
>>>>
>>>> However, once in a while I am concerned that sys-whonix-14 is
>>>> starting when I am NOT updating anything  eg in  dom0  today :
>>>>
>>>> qvm-run -a fooappVM fooapplication   (for a fooappVM that wasn't
>>>> open) and sys-whonix-14  was shutdown
>>>>
>>>> for some reason it started up
>>>
>>> This could happen if fooappVM's netvm is set to sys-whonix-14.
>>>
>>>
>>>> my  /etc/qubes-rpc/policy/qubes.UpdatesProxy ; looks like this :
>>>
>>>> $type:TemplateVM $default allow,target=sys-whonix-14
>>>>
>>>
>>> This line, since it is first, means all templates will be updated
>>> through sys-whonix-14. Maybe when you started fooapplication, Qubes
>>> checked the related template for any updates?
>>>
>>>
>>
>> Thanks for your reply, well I've checked only anon-whonix dispVM3400 and
>> whonix-ws-dvm-14 are using  sys-whonix-14
> 
> OK.
> 
>> I'm pretty sure  fedora-28 and Debian-9  are updating over sys-net
> 
> They're not. :)


> 
>> 3)hmm, oh so, dom0 when it starts checks templates for any new versions
>> say of firefox, and that requires the template to start and use the
>> designated netvm even if the templates are set to "none" .
>> .maybe this only applies if the application is started from dom0
>> via qvm-run  with  its associated appvm also closed  guess I needed to
>> further test it 
> 
> Close- when dom0 checks for template updates it needs to start the VM
> specified for template updates, which in your case is sys-whonix-14.

a) Are you saying that  booting an  AppVM (maybe with or without qvm-run
) would cause dom0 to check if the template that AppVM is based on for
updates?   if dom0 is set to sys-net, doesn't seem to make sense,
unless  the template is being called , perhaps the /qubes.UpdatesProxy
designated netvm is invoked even thought the template doesn't actually
start ?

> 
>> 4) if you are using sys-net for  Deb/Fedora  updates and sys-whonix-14
>> for  -gw -ws  update   could you please  post your  /qubes.UpdatesProxy for
>> me
> 
> I'm not, but to do so you would change the FIRST occurrence to read
> "$type:TemplateVM $default allow,target=sys-net". The existing
> "$tag:whonix-updatevm $default allow,target=sys-whonix-14" line means your
> whonix related templates will continue to be updated through
> sys-whonix-14.
> 

b) hmm, maybe there are good reason to leave it as sys-whonix-14 , since
it seems fast enough d/l speed  then

-- 
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/56668945-964c-ebc6-dabe-936dc6326103%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Strange sys-whonix-14 starts ; /etc/qubes-rpc/policy/qubes.UpdatesProxy

2018-09-06 Thread John S.Recdep
On 09/06/2018 02:45 AM, 'awokd' via qubes-users wrote:
> On Wed, September 5, 2018 12:21 am, John S.Recdep wrote:
>> Hello,
>>
>>
>> while upgrading to sys-whonix-14 many weeks ago, I was fighting to
>> maintain  my Fedora and Debian Template to keep using sys-net  not
>> sys-whonix-14
>>
>> and sys-whonix-gw and -ws to use sys-whonix-14  , which are otherwise
>> working fine and I hesitate to mess with
>> /etc/qubes-rpc/policy/qubes.UpdatesProxy
>>
>>
>>
>> However, once in a while I am concerned that sys-whonix-14 is starting
>> when I am NOT updating anything  eg in  dom0  today :
>>
>> qvm-run -a fooappVM fooapplication   (for a fooappVM that wasn't open) and
>> sys-whonix-14  was shutdown
>>
>> for some reason it started up
> 
> This could happen if fooappVM's netvm is set to sys-whonix-14.
> 
>> my  /etc/qubes-rpc/policy/qubes.UpdatesProxy ; looks like this :
> 
>> $type:TemplateVM $default allow,target=sys-whonix-14
> 
> This line, since it is first, means all templates will be updated through
> sys-whonix-14. Maybe when you started fooapplication, Qubes checked the
> related template for any updates?
> 
> 

Thanks for your reply, well I've checked only anon-whonix dispVM3400 and
whonix-ws-dvm-14 are using  sys-whonix-14


I'm pretty sure  fedora-28 and Debian-9  are updating over sys-net

$qubes-prefs
updatevm  -  sys-net

is the dom0 says


1)so how can I proceed further to problem-solve this ?

2)maybe the mismatch is causing issues ?

3)hmm, oh so, dom0 when it starts checks templates for any new versions
say of firefox, and that requires the template to start and use the
designated netvm even if the templates are set to "none" .
.maybe this only applies if the application is started from dom0
via qvm-run  with  its associated appvm also closed  guess I needed to
further test it 

4) if you are using sys-net for  Deb/Fedora  updates and sys-whonix-14
for  -gw -ws  update   could you please  post your  /qubes.UpdatesProxy
for me

5) do most folks NOT  use sys-whonix  for  templates updates?



-- 
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/a9bd1c3d-39ca-a4c8-928b-eda9583ae88d%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: ANN: Testing new VPN code for Qubes

2018-09-06 Thread John S.Recdep
On 09/06/2018 04:22 AM, 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:
> It appears as if I am getting a TLS error? Why would this suddenly start?
> 
> Wed Sep  5 17:23:39 2018 TLS Error: TLS handshake failed
> Wed Sep  5 17:23:39 2018 SIGUSR1[soft,tls-error] received, process restarting
> Wed Sep  5 17:23:39 2018 Restart pause, 5 second(s)
> Wed Sep  5 17:23:44 2018 TCP/UDP: Preserving recently used remote address: 
> [AF_INET]xxx.xxx.xxx.xx:port xxx
> 
> I have restarted the computer, I am using Qubes 4.0 and leveraging a Debian 9 
> template.
> 
> The other devices are using OpenVPN...
> 
> Any ideas?
> 
> John,
> Not sure what " script in an appvm/qube  instead of the "tunnel"  version ?" 
> is...I had tried to set up the "iptables and CLI scripts" 
> https://www.qubes-os.org/doc/vpn/ but really struggled. I found the Tasket 
> solution easier to set up for a relative novice in desperate need of VPN 
> security. I am also able to setup a few configurations so I can use different 
> destinations. Is this the version you are using?  
> 

Sorry by "script"  I meant  "Qubes-vpn-support"
https://github.com/tasket

vs.  "qubes-tunnel"


btw, it's a bit hard to tell your  the OP ?   Mr. 22rip ?

you installed qubes-tunnel  in  a  Debian Template  and it was working ,
now it is not


PS: tasket doesn't think  trying "Qubes-vpn-support" in an AppVM  will
make any difference, I noted   goodluck

-- 
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/062963a7-8614-1b3e-6345-48bf4c4de4ae%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: ANN: Testing new VPN code for Qubes

2018-09-05 Thread John S.Recdep
On 09/05/2018 05:32 AM, 22rip-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:
> Correctionmy TOR is working. Any ideas how to trouble shoot?
> 
> 
> Everything has been working fine, however recently my VPN tunnel is failing?
> 
> I ran: sudo journalctl -u qubes-tunnel
> 
> and I get:
> 
> Sep 05 10:17:48 VPN-Mid qtunnel-setup[1138]: Wed Sep  5 10:17:48 2018 All 
> connections have been connect-retry-max (7) times unsuccessful, e
> Sep 05 10:17:48 VPN-Mid qtunnel-setup[1138]: Wed Sep  5 10:17:48 2018 Exiting 
> due to fatal error
> Sep 05 10:17:48 VPN-Mid systemd[1]: qubes-tunnel.service: Main process 
> exited, code=exited, status=1/FAILURE
> Sep 05 10:17:48 VPN-Mid qtunnel-setup[1149]: STOP-ing network forwarding!
> Sep 05 10:17:48 VPN-Mid systemd[1]: qubes-tunnel.service: Unit entered failed 
> state.
> Sep 05 10:17:48 VPN-Mid systemd[1]: qubes-tunnel.service: Failed with result 
> 'exit-code'.
> 
> Some additional notes:
> My connection works on other devices
> I am able to get Internet access via non-VPN connection
> I did update Dom0 and my templates but it worked shortly afterwards
> 
> Any ideas how to trouble shoot this?
> 
> Thanks for any help...
> 

I know this isn't your question but,  have you tried the script in an
appvm/qube  instead of the "tunnel"  version ?

That is what I use fwiw

-- 
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/acda1e2f-9f7c-b797-66b7-cce55a6030ca%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Strange sys-whonix-14 starts ; /etc/qubes-rpc/policy/qubes.UpdatesProxy

2018-09-04 Thread John S.Recdep
Hello,

while upgrading to sys-whonix-14 many weeks ago, I was fighting to
maintain  my Fedora and Debian Template to keep using sys-net  not
sys-whonix-14

and sys-whonix-gw and -ws to use sys-whonix-14  , which are otherwise
working fine and I hesitate to mess with
/etc/qubes-rpc/policy/qubes.UpdatesProxy


However, once in a while I am concerned that sys-whonix-14 is starting
when I am NOT updating anything  eg in  dom0  today :

qvm-run -a fooappVM fooapplication   (for a fooappVM that wasn't open)
and sys-whonix-14  was shutdown

for some reason it started up

my  /etc/qubes-rpc/policy/qubes.UpdatesProxy ; looks like this :


--
# Default rule for all TemplateVMs - direct the connection to sys-net

$type:TemplateVM $default allow,target=sys-whonix-14

$tag:whonix-updatevm $default allow,target=sys-whonix-14
$tag:whonix-updatevm $anyvm deny



## Note that policy parsing stops at the first match,
## so adding anything below "$anyvm $anyvm action" line will have no effect

## Please use a single # to start your custom comments


# Default rule for all TemplateVMs - direct the connection to sys-net

$type:TemplateVM $default allow,target=sys-net





$anyvm $anyvm deny

--


It is in this order, because it works  and a bit fearful to change  it
, but  curious   what others looks like  and maybe it is obvious  what
the problem 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/eb13f022-47e1-0f88-fe04-b62dc8bcc175%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Use Internal Mic for Skype in Standalone AppVM

2018-08-24 Thread John S.Recdep
On 08/22/2018 04:27 AM,
robertwalz35-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> Hello,
> 
> does anybody have experience in using the internal mic inside an AppVM for 
> skype?
> 
> I just created a Standalone AppVM based on fedora-26 template (Qubes R4.0) 
> and attached the mic to this VM. In PulseAudio Volume Control I selected 
> "Audio Stereo Duplex", my speakers are working on this AppVM. As Input Device 
> I selected "Internal Microphone" and in skypeforlinux's audio settings 
> "Microphone: Qubes VCHAN source", "Automatically adjust microphone settings: 
> On"
> 
> I also tried to record with audacity, but I got an error message, that it is 
> unable to capture the stream...
> 
> I use a Lenovo X220 and Qubes R4.0 (Fedora-26 template, Standalone AppVM)
> 
> Would be thankful for an advice!
> 
> Regards
> 

if you do qvm-block or qvm-usb  what choices do you see?

I have a thinkpad with int mic worked on skype but wasn't in a
standalone, looks like you may be confusing 'standalone based on
template' with App-template-based-VM ; iirc there are 3 flavors , appvm,
SAbasedontemplate, and SAnotbasedontemplate (the SA's can be changed
from PVH to HVM, SA's and AppVms are PVH by default --
https://www.qubes-os.org/doc/glossary/


PS: sudo qubes-dom0-update qubes-template-fedora-28  or so  , as sure
you know fed-26  is no longer supported or soon won't be.  things may
work better with the up to date template?
https://www.qubes-os.org/doc/templates/fedora/

-- 
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/e304a7a3-d1f1-823e-a68c-1ca00f6bbc51%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Asking Template VM 'user' passsword after running autoremove.

2018-08-24 Thread John S.Recdep
On 08/24/2018 03:18 AM,
wlminimal-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> Hi
> I wanted to clean up my Template VM by running sudo dnf autoremove and sudo 
> apt autoremove..
> But after this, Template vm started asking user's password which I don't know 
> and can run sudo..
> And After restart qubes os, network manager is not running so I can't connect 
> to the internet..
> How can I solve this issue?
> 
as I recall it asks for your sudo pw , which is Not  the one decrypt
your drive,  nor your user,  in Qubes there is no sudo pw by default ,

tasket has a script you can use, iirc that would create one, but that
probably won't solve this 

in my case debian was ok, just fedora  broke iirc

-- 
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/2eeaa0e7-2d9d-7199-e36f-05aeaccf5c25%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Asking Template VM 'user' passsword after running autoremove.

2018-08-24 Thread John S.Recdep
On 08/24/2018 03:18 AM,
wlminimal-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> Hi
> I wanted to clean up my Template VM by running sudo dnf autoremove and sudo 
> apt autoremove..
> But after this, Template vm started asking user's password which I don't know 
> and can run sudo..
> And After restart qubes os, network manager is not running so I can't connect 
> to the internet..
> How can I solve this issue?
> 

I think this happened to a number of people some weeks back(rumor I
heard it that some package maintainer made a mistake somewhere),
happened to me and in the end I just reinstalled the Template from
qubes-dom0-update  instead of trying to fix it, and for me, probably
breaking something else,  if you do a search you can see my thread on
here, lesson learned: make a clone of your clean and/or altered
Templates from time to time, and be cautious with autoremove (though
I'll probably use it again) 

also, one qubster on here backs up his templates to another media source
nightly :)


-- 
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/e6a37f7a-8f84-ab47-80d1-72f1282f3f6c%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 4.0 sluggish feel

2018-08-21 Thread John S.Recdep
On 08/10/2018 12:54 PM,
brendan.hoar-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> On Friday, August 10, 2018 at 12:49:05 AM UTC-4, Outback Dingo wrote:
>> On Fri, Aug 10, 2018 at 6:18 AM John S.Recdep wrote:
>>> I blame intel speedstep for everything in your local uefi ,  and dingos :)
>>
>> great but how do we resolve it... its makes Qubes itself really unuseable
> 
> Maybe try this?
> In dom0:
> sudo xenpm set-scaling-governor performance
> 
> Brendan
> 

seems it wants a   , what would that be?

-- 
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/dc1522e8-23e6-ea09-5c5f-1d578abff2f9%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Both dVM gnome-terminals are not launching

2018-08-20 Thread John S.Recdep
On 08/16/2018 03:09 AM, Marcus Linsner wrote:
> On Friday, June 1, 2018 at 11:31:14 PM UTC+2, 
> qube...-DIVuIKq8I9LqlBn2x/y...@public.gmane.org wrote:
>> The Qubes docs at:
>>
>> https://www.qubes-os.org/doc/dispvm-customization/
>>
>> note the following for disposable vms:
>>
>> __
>>
>> Note that currently only applications whose main process keeps running 
>> until you close the application (i.e. do not start a background process 
>> instead) will work. One of known examples of incompatible applications 
>> is GNOME Terminal (shown on the list as “Terminal”). Choose different 
>> terminal emulator (like XTerm) instead.
> 
> Also nautilus (shown on the list as "Files") even though its main process (at 
> least when run from another terminal) doesn't return (like gnome-terminal 
> does) until its window is closed (actually 11 seconds after its window is 
> closed: try "time nautilus; echo returned" and alt+f4 the window as soon as 
> it appears - shows like 13 seconds then "returned"). Can anyone explain?
> 

Can you rewrite this, if it is not solved?

What are you trying to do ?Open a dispVM  and you want it to work
when it isn'tand/or  it's too slow ..   your question isn't clear

-- 
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/e2a3083f-3a25-1ced-20e9-e5b90b704e48%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: how to forward webcam to a VM?

2018-08-17 Thread John S.Recdep
On 08/17/2018 02:54 AM, Aliaksandr Kavaliou wrote:
> 
> 
> On 11/26/17 16:10, Unman wrote:
>> On Sun, Nov 26, 2017 at 01:04:39PM +0100, evo wrote:
>>>
>>>
>>> Am 26.11.2017 um 00:58 schrieb awokd:
 On Sat, November 25, 2017 16:46, evo wrote:

> I have connected a webcam and i see it via lsusb on sys-usb. I also can
> use it with "cheese" programm on the sys-usb-VM. But how can i forward
> it to webcam-VM and use it there??

 Many webcams can be used over USB proxy. From dom0, enter "qvm-usb" with
 the webcam connected. You should see a list of available USB devices,
 including the webcam. From there, you'd enter "qvm-usb -a webcam-VM
 sys-usb:12.3". Use the correct name for your VM and sys-usb:device
 identifier for your webcam.

 See https://www.qubes-os.org/doc/usb/ for more instructions.


>>>
>>>
>>> Hey! Thanks!
>>> i installed qubes-usb-proxy on the webcam-VM and tried to attach it
>>> there, but i get this error: "device attach failed: Invalid speed received"
>>>
>>> find nothing about such error in the docs.
>>
>> Which Qubes version are you using?
>>
>> What's the device you are trying to use?
>> Can you provde more information?
>>
>> This is an error that has been reported before and there's an open
>> ticket on qubes issues.
>> It seems to be device and circumstance dependent. (e.g an android in
>> debug mode throws this error but the same device NOT in debug mode
>> attaches properly.)
>>
> 
> 
> Hey Guys!
> after some time i installed Qubes 4.0 and here the usb-proxy goes over
> the grafic icon. But i still can not run my webcam Logitech C920. I
> attach it to the webcam-VM, run the software (tox, but also cheese), but
> there is no device found.
> 
> hmm... can somebody help?
> 

so you tried it in both Fedora-28 and Debian-9  appvms?

-- 
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/f84884f7-7343-7c71-3b8e-667a10b4fda0%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Installation help please

2018-08-17 Thread John S.Recdep
On 08/17/2018 02:41 AM, Bengt Thuree wrote:
> Asus Prime A320M-E

you saw the HCL ?

 ASUS PRIME H270-PLUS/CSM
i7-7700 Kaby Lake HD Graphics   0808yes yes yes unknown 
R4.04.8.2
4.9.56-21   

set BIOS to Legacy OPROM only

I realize its not a exact match but
https://www.qubes-os.org/hcl/

the whole  legacy v. uefi  boot  I don't see mentioned in your  writeup
; & can be the 1st thing to try ; the crux of some installs

otherwise, another common Bios thing is to "disable discrete graphics"
if there exists such an option in the Bios,  otherwise,   it
shouldn't be that complicated  unless your doing something special,
of which much of your writeup   is beyond my level :)

-- 
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/c8c6e941-daa7-5eed-cc75-8c6017ddac72%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Whonix 14 - Updated, just lost Tor Browser for Whonix-dvm??

2018-08-17 Thread John S.Recdep
On 08/16/2018 02:34 PM,
bm-2ctjsegdfzqngqwuqjswro6jrwlc9b3mn3-A7g8B5KuuXnx/jn5l+7...@public.gmane.org
wrote:
> On Wed, 15 Aug 2018 12:59:06 -0700 (PDT)
> smcmj-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:
> 
>> I just transitioned to the new Whonix 14 templates, everything was
>> working great however I just updated both the -gw and -ws templates
>> and lost the Tor Browser(AnonDist) from the whonix-ws-14-dvm after
>> update? When I launch a "whonix-ws-14-dvm" browser I get a pop-up
>> asking: "Tor Browser not installed/Start Tor Browser download?".
>>
>> What I tried:
>>
>> To customize the -dvm's in Debian and Fedora I have run the following
>> to customize -dvm's (other then whonix):
>>
>> [user@dom0 ~]$ qvm-run -a debian-dvm gnome-terminal
>>
>> Then in new terminal of “-dvm” type “firefox” to launch firefox, then
>> I customize the browser.
>>
>> I tried the following with Whonix-dvm:
>> [user@dom0 ~]$ qvm-run -a whonix-ws-14-dvm gnome-terminal
>>
>> The problem I am having is:
>> 1) The "whonix-ws-14-dvm" starts but no gnome terminal launches?
>> 2) Since whonix doesn't use "Firefox" what would I type to launch the
>> "Tor Browser"? Assuming I eventually get a gnome terminal to launch
>> 3) How do I install the Tor Browser safely into either the template
>> or -dvm?
>>
>> Other notes:
>> - I created an AppVM using the updated "whonix-ws-14" template,
>> received a popup that "Tor Browser" is not installed, installed the
>> oldest browser per the recommendation on the pop-up, however after
>> installing another pop-up states: "Signature looks quite old
>> already...check signature looks sane".  I was able to navigate to an
>> Onion site, whonix check came back OK.
>>
>>
>> Thanks again for the help...
>>
> 
> 
> The same happened to me after updates. Running 'update-torbrowser' in
> whonix-ws fixed the problem. 
> 

thx this solved the same issue I was having ; i had thought maybe it was
normal to be asked everytime to d/l  torbrowser lol

-- 
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/31000cc9-9656-0da9-4945-772fd8afb658%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: please stay tuned on Whonix news re: "updater"

2018-08-17 Thread John S.Recdep
On 08/16/2018 05:37 PM, John S.Recdep wrote:
> On 08/15/2018 07:23 PM, Patrick Schleizer wrote:
>> It is important to read the latest Whonix news to stay in touch with
>> ongoing developments. This way users benefit from notifications
>> concerning important security vulnerabilities and improved releases
>> which address identified issues, like those affecting the updater or
>> other core elements.
>>
>> Read more:
>> https://www.whonix.org/wiki/Stay_Tuned
>>
> 
> did something happen?
> 
> by "updater"  meaning sudo apt-get update && sudo apt-get dist-upgrade   ?
> 
> seemed to be broken the other day, but seems ok
> don't see anything new on vuln issues
> https://forums.whonix.org/c/news
> 
> guess I can check again next month  :)
> 

Actually the failing updates are back , if you don't mind I prefer to
ask here for now:
in whonix-ws-14 Konsole

$sudo apt-get update

Err:20
tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion
stretch Release
  Connection failed
Reading package lists... Done


E: The repository
'tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion
stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user
configuration details.

-- 
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/d1bc2438-879f-2fd6-c397-3c345d4afa23%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: how do you clear "move/copy to other app vm" context windows

2018-08-17 Thread John S.Recdep
On 08/16/2018 09:34 PM, cubit wrote:
> 17. Aug 2018 03:24 by yrebstv-sgozh3hwpm2stnjn9+b...@public.gmane.org 
> :
> 
>> On 08/16/2018 08:32 AM, cubit wrote:
>>> Is there a way to copy the suggested VMs in the "move/copy to other app vm" 
>>> as I have a few entries that no longer exist and would like to get rid of 
>>> them?
>>>
>>>
>>> CuBit
>>>
>>
>> I suppose you've tried  qvm-sync-appmenus in dom0
>>
>> and/or  in the VMM  "refresh applications" 
>>
>>
>> though, just a wild guess not an educated one
>>
> 
> 
> 
> 
> 
> 
> 
> I think I was not too clear.   In the file browsers (nautilus) there is a 
> right click context menu option to copy or move a file to another appvm.  I 
> am trying to find how to clear these dialog boxes of the appvm names that are 
> saved in them.
> 
> 
> 
> 
> CuBit
> 

And it's  Qubes 4.0 ?

In 3.2 I remember a problem like this , I recall someone in here,
probably Tasket,  saying the ability to go and manually remove old
removed VM references  was now gone.

If it is 3.2 it may be possible to do it manually,  in 4.0  better ask
Unman or Awokd   .

-- 
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/8edb2385-4cc7-4fc0-bef0-4cc2142e7c9c%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Whonix 14 - upgrade or re-install? Whats more smooth, less troublesome?

2018-08-17 Thread John S.Recdep
On 08/12/2018 08:16 AM,
qubes-fan-q7wo9g+UVklWk0Htik3J/w...@public.gmane.org wrote:
> I am planning to move from my Whonix 13 to Whonix 14 on Qubes. My question is 
> what way it should be easier, based on the Q user experiences. What would you 
> propose - upgrade or re-install? Are there any known issues which would call 
> for one or other way?
> 
> I have few VMs based on the Whonix template with data and settings on it. 
> Will the contents of these VMs remain, or will it be destroyed - re-install 
> vs upgrade?
> 
> Thank you
> 


https://github.com/Qubes-Community/Contents/blob/master/docs/misc/iaq.md#manually-install-whonix-14-templates


worked for me, I'd call it a new install not a "re-install"

-- 
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/2e70610c-96c3-53d5-7e12-23ed43be7903%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Suggested order for loading Qubes 4.0?

2018-08-17 Thread John S.Recdep
On 08/17/2018 03:13 AM, 'awokd' via qubes-users wrote:
> On Fri, August 17, 2018 6:03 am, Patrick Bouldin wrote:
>> On Thursday, August 16, 2018 at 11:34:48 PM UTC-4, John S.Recdep wrote:
>>
>>> On 08/16/2018 04:25 AM, Patrick Bouldin wrote:
>>>
>>>> Hello, I got some great advice about having two hard drives since I
>>>> want Windows on one drive and qubes on another. So I now have a good
>>>> I7 laptop with two - 1/2 TB SSDs. I had in mind to load it this way,
>>>> is the following correct?
>>>>
>>>> I'm starting with both SSDs empty, no OS on either.
>>>>
>>>>
>>>> 1 Physically install both drives
>>>>
>>>>
>>>> 2 Install Windows on disk 1 after booting to flash drive with windows
>>>> ISO
>>>>
>>>>
>>>> 3 Unplug windows based SSD drive just to be sure I'm on the right
>>>> drive next
>>>>
>>>> 4 Boot to bios, modify bios to change 2nd SSD (to be Qubes) FROM
>>>> Windows UEFI to other OS (correct?)
>>>>
>>>>
>>>> 5 Boot to a flash drive loaded with the Qubes 4.0 install ISO
>>>>
>>>>
>>>> This is the part I'm really not clear about, remember I'm working
>>>> with two drives, booting to either the drive to windows or the drive
>>>> to qubes. So, am I following the advice here?:
>>>> https://www.qubes-os.org/doc/multiboot/
>>>> - select custom layout, assign existing /boot partition as /boot,
>>>> deselect the 'Format' option, continue with installation.
>>>>
>>>>
>>>> Or, do I let Qubes install in automatic configuration and then
>>>> manually modify the grub file?
>>>>
>>>>
>>>> Thanks,
>>>> Patrick
>>>>
>>>>
>>>
>>> Sounds like what I did/do   with windows 10 ; since it doesn't involve
>>> Grub ,  probably won't be a problem ..
>>>
>>>
>>> In my case however,  the uefi, I believe doesn't label the drive with
>>> the  drive name, but changes it to  "windows" or "qubes" , which concerns
>>> me , as I think it incorrect, I think that may be how uefi works  ymmv,
>>> why not try it
>>>
>>> what is a "windows uefi" ? looks to me like
>>> https://www.qubes-os.org/doc/multiboot
>>>
>>>
>>> doesn't apply to you, its for single disk dual booting
>>
>> Hi John and thanks. I agree but I think after I install qubes then I will
>> need to delay the grub screen in order to be able to choose either Win 10
>> or Qubes. And I think I have to somehow tell qubes to look for the
>> windows drive and then allow to choose it...  Anyway you're right, I
>> think once I have them both loaded I hope to figure it out.
> 
> UEFI uses an EFI partition on one of your drives, so if you pull the
> Windows drive it might get confused. You can try it, but if you have
> problems might want to re-install with legacy/grub boot for both OSes.
> 
> 

I don't think Grub has to be involved at all, you just change  the boot
order in  the  Bios-Uefi

If it doesn't work pulling the drive,  just leave it, When I put either
win10 or Q4.0   , there is no Grub choice  being asked

-- 
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/2d7d4483-7c69-2794-101d-be085b77454d%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: please stay tuned on Whonix news

2018-08-16 Thread John S.Recdep
On 08/15/2018 07:23 PM, Patrick Schleizer wrote:
> It is important to read the latest Whonix news to stay in touch with
> ongoing developments. This way users benefit from notifications
> concerning important security vulnerabilities and improved releases
> which address identified issues, like those affecting the updater or
> other core elements.
> 
> Read more:
> https://www.whonix.org/wiki/Stay_Tuned
> 

did something happen?

by "updater"  meaning sudo apt-get update && sudo apt-get dist-upgrade   ?

seemed to be broken the other day, but seems ok
don't see anything new on vuln issues
https://forums.whonix.org/c/news

guess I can check again next month  :)

-- 
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/d1af25f4-68c7-3cd0-04e7-b49470e2c37a%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Suggested order for loading Qubes 4.0?

2018-08-16 Thread John S.Recdep
On 08/16/2018 04:25 AM, Patrick Bouldin wrote:
> Hello, I got some great advice about having two hard drives since I want 
> Windows on one drive and qubes on another. So I now have a good I7 laptop 
> with two - 1/2 TB SSDs. I had in mind to load it this way, is the following 
> correct?
> 
> I'm starting with both SSDs empty, no OS on either.
> 
> 1 Physically install both drives
> 
> 2 Install Windows on disk 1 after booting to flash drive with windows ISO
> 
> 3 Unplug windows based SSD drive just to be sure I'm on the right drive next
> 
> 4 Boot to bios, modify bios to change 2nd SSD (to be Qubes) FROM Windows UEFI 
> to other OS (correct?)
> 
> 5 Boot to a flash drive loaded with the Qubes 4.0 install ISO 
> 
> This is the part I'm really not clear about, remember I'm working with two 
> drives, booting to either the drive to windows or the drive to qubes. So, am 
> I following the advice here?: https://www.qubes-os.org/doc/multiboot/
>   - select custom layout, assign existing /boot partition as /boot, deselect 
> the 
> 'Format' option, continue with installation.   
> 
> Or, do I let Qubes install in automatic configuration and then manually 
> modify the grub file?
> 
> 
> Thanks,
> Patrick
> 

Sounds like what I did/do   with windows 10 ; since it doesn't involve
Grub ,  probably won't be a problem ..

In my case however,  the uefi, I believe doesn't label the drive with
the  drive name, but changes it to  "windows" or "qubes" , which
concerns me , as I think it incorrect, I think that may be how uefi
works  ymmv,  why not try it

what is a "windows uefi" ?
looks to me like
https://www.qubes-os.org/doc/multiboot

doesn't apply to you, its for single disk dual booting

-- 
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/2efb6aec-c949-f5fc-6d4c-7420f9a7d8f4%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: how do you clear "move/copy to other app vm" context windows

2018-08-16 Thread John S.Recdep
On 08/16/2018 08:32 AM, cubit wrote:
> Is there a way to copy the suggested VMs in the "move/copy to other app vm" 
> as I have a few entries that no longer exist and would like to get rid of 
> them?
> 
> 
> CuBit
> 

I suppose you've tried  qvm-sync-appmenus in dom0

and/or  in the VMM  "refresh applications" 


though, just a wild guess not an educated one

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


[qubes-users] Re: Qubes 4.0 sluggish feel

2018-08-10 Thread John S.Recdep
On 08/09/2018 06:48 PM, Outback Dingo wrote:
> On Fri, Aug 10, 2018 at 6:18 AM John S.Recdep 
>  wrote:
>>
>> On 08/06/2018 01:50 PM, Outback Dingo wrote:
>>> I dont remeber qubes being so sluggish on a skylake laptop with 64Gb,
>>> qubes is installed on a SSD, however it now seems to take an awful
>>> long time to switch windows, change tabs in firefox and chhrome,
>>> launch VMs
>>>
>>> also note that screen rendering, i can actually watch web pages paint,
>>> as though video is being quirly or something, it is an NVIDIA card
>>>
>>> any suggestions, nothing is swapping, memory seems ok, ive even
>>> allocated 8192 mb to 2 vms which i see it in, both fedora and debian,
>>> and i am up to date update wise.
>>>
>>
>> I blame intel speedstep for everything in your local uefi ,  and dingos :)
> 
> great but how do we resolve it... its makes Qubes itself really unuseable
> 


i guess You  would disable it and reboot  but ymmv

-- 
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/aa659861-b0d4-538b-1996-d0b419ade031%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 4.0 sluggish feel

2018-08-09 Thread John S.Recdep
On 08/06/2018 01:50 PM, Outback Dingo wrote:
> I dont remeber qubes being so sluggish on a skylake laptop with 64Gb,
> qubes is installed on a SSD, however it now seems to take an awful
> long time to switch windows, change tabs in firefox and chhrome,
> launch VMs
> 
> also note that screen rendering, i can actually watch web pages paint,
> as though video is being quirly or something, it is an NVIDIA card
> 
> any suggestions, nothing is swapping, memory seems ok, ive even
> allocated 8192 mb to 2 vms which i see it in, both fedora and debian,
> and i am up to date update wise.
> 

I blame intel speedstep for everything in your local uefi ,  and dingos :)

-- 
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/95ee05c4-3ae9-b96b-23e4-3e08ba5c45aa%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: VM Manager update / VMM setup for AppQube for web or mail only?

2018-08-08 Thread John S.Recdep
On 08/04/2018 02:04 PM, smcmj-2xk3N/kkaK1Wk0Htik3J/w...@public.gmane.org wrote:
> I'll take a shot, also willing to learn more if I am missing something:
> 
> I would try to find the IP of the email provider if you are using a VM for 
> email, e.g. Tutanota's IP address is: 81.3.6.162(no IMAP wit them), therefore 
> my firewall settings for that VM would be:
> 
> IP: 81.3.6.162
> Service: https (or port 443)
> Protocol: TCP
> 
> Things I have learned about the firewall include:
> 1) You can type a port number into the service field vs just using whats in 
> the "Services" dropdown selection
> 2) MXToolbox is a good tool to find an IP address of a website
> 3) I created a print VM that only allows access to my networked printer IP 
> and the network printer's port. With this VM I can access only the printer. 
> Maybe your vault uses this VM as its DVM. I don't trust printers in general 
> but at least its restricted
> 
> For web only 443(https) and 80(http) are all that is needed for the most 
> part. I believe ICMP(pings) and port 53(DNS) are allowed automatically. Open 
> to being corrected? It would be nice to control the DNS more (Quad9 DNS 
> resolver or OpenDNS). Not sure how to do this with ease.
> 
> For Thunderbird, you could research your email providers IP and change the 
> "*"/ANY for the specific IPs or IP.

And what do you use to make it so your Network Printer is all that is
allowed access.

Thats true, as per the Qubes docs on network printers, I cloned the F
Template and installed the printer driver in it, then use it as the
Template for an AppVM that just does printing, but occasional I'll
browse to some URL to print a webpage.  BUT, I also use the AppVM as the
default for disp appvm's to be based on so I can print from attachments
to emails etc ,  and hence,  for the vault, it was also the default...

so did go and change that fwiw :)

PS
AM not using webmail, as primary, so would need more something for IMAP
or ? IMAPS ,  not sure if it is really necessary on top of whatever
sys-firewall does  etc

which is why I was asking what if anything typical qubes users do with
the  firewall tab in the VMM

-- 
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/7dade891-d9fd-778f-3053-d07865abb031%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] VM Manager update / VMM setup for AppQube for web or mail only?

2018-08-04 Thread John S.Recdep
Looks like the last dom0 update fixed the  notifications of open/close
VMs, and I believe the 'refresh' VMM is gone now? Is that right, so I
assume it auto-refreshes in Q4.0 ?

My question is simple, and sorry I'm iptables/fw  illiterate but I was
thinking for some time.  For another layer of security I should use the
VMM fw , which currently is blank in all the AppVMs except for one

where in the Firewall rules Tab I've entered :

address  *
Service  https
Protocol  TCP

and

address  *
Service  http
Protocol  TCP


in 9/10 of my AppVMs  I am just webbrowsing ; occasionally I use
Hexchat  or VLC  , Signal or other messengers

I use Thunderbird in it's own AppVM

Is there anything further I would want for  a  Web only  fw  in the VMM

and

What should I use for  Thunderbird ?

address  *
Service  SMTP
Protocol  ANY

address  *
Service  IMAP
Protocol  TCP

address  *
Service  IMAPS
Protocol  TCP

or do most folks just not bother with further   fw   AppVM  settings

Lastly,  what exactly happens in  sys-firewall  with default settings ?



thx

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


[qubes-users] Re: Qubes 4, copy/paste not working between AppVM's

2018-08-04 Thread John S.Recdep
On 08/04/2018 09:34 AM,
max.militant-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> fredag den 3. august 2018 kl. 16.28.37 UTC-4 skrev John S.Recdep:
>> On 08/03/2018 04:45 AM,
>> max.militant-re5jqeeqqe8avxtiumwx3w-xmd5yjdbdmrexy1tmh2...@public.gmane.org 
>> wrote:
>>>> If you open the VM Manager and go to Qube-> Keyboard Layout what is it
>>>> set to ?
>>> It's default on my individual VM's (set to qubes default layout). My Qubes 
>>> (Dom0) model is Generic 105-key (intl) PC on my Purism 13v2 laptop. The 
>>> layout is Danish.
>>>  
>>
>> I suppose you've tried setting dom0 to default to troubleshoot ? And
>> sorry to ask but when was it last working, and did you change/install
>> something etc ?
> 
> Actually you hit the spot. If I'm running danish keyboard (system tools - 
> keyboard), the copying doesn't work. If I run system default in qubes and set 
> the layout to danish on every VM, it works.
> 
> Thank you for showing me the forest, I apparently missed because of all the 
> trees :)
> 
> Sincerely
> Max
> 

happens to me all the time, I just need to write it out, and hear it
back from someone, sometimes :)

-- 
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/b14b2ced-0843-cec9-d03a-19c3ef04cb64%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: newbie question about converting pictures into a trusted image

2018-08-04 Thread John S.Recdep
On 08/04/2018 06:11 AM,
tirejeremy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> Can you help please to understand how it works more deeper
> 
> Why all random pic (jpeg,png, bmp etc) marked as untrusted. Are they not 
> passing the tests on dispvms?
> 
> *.jpg-untrusted - Does it usable or not?
> 
> if I have many different virtual machines (dispvms based on different 
> templates, which one do the tests start and do they run at all? how to check 
> it? very grateful.
> 
> https://github.com/QubesOS/qubes-issues/issues/2437
> https://theinvisiblethings.blogspot.com/2013/02/converting-untrusted-pdfs-into-trusted.html
> 

I am guessing "untrusted" is just the Name of your  AppVM (qube),  there
is no tests .

There is the ability to "create trusted pdfs" via an Disp Qube which
transforms the pdf format to all pixels  then it puts a larger copy back
in your original App Qube  and changes the name to  "foo-trusted.pdf"
but its no longer a pdf per se

I hope that helps ?

-- 
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/20f1a263-a4a4-00ba-17d2-b95f170cfc1d%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 4, copy/paste not working between AppVM's

2018-08-03 Thread John S.Recdep
On 08/03/2018 04:45 AM,
max.militant-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
>> If you open the VM Manager and go to Qube-> Keyboard Layout what is it
>> set to ?
> It's default on my individual VM's (set to qubes default layout). My Qubes 
> (Dom0) model is Generic 105-key (intl) PC on my Purism 13v2 laptop. The 
> layout is Danish.
>  

I suppose you've tried setting dom0 to default to troubleshoot ? And
sorry to ask but when was it last working, and did you change/install
something etc ?


-- 
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/aedd11ea-6cb6-c9b1-13fc-30beb079beef%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 4, copy/paste not working between AppVM's

2018-08-03 Thread John S.Recdep
On 08/02/2018 02:56 AM,
max.militant-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> torsdag den 2. august 2018 kl. 01.28.12 UTC-4 skrev 
> max.mi...-re5jqeeqqe8avxtiumw...@public.gmane.org:
>> Hi,
>>
>> I have a Qubes 4 installation on my laptop, and copy/paste between appVMs is 
>> not working.
>>
>> I usually(on other Qubes installations) get an infobox on copy/paste to the 
>> clipboard in upper right corner whenever I press the sequence (ctrl-c, 
>> ctrl-shift-c) and again in the destination vm (ctrl-shift-v, ctrl-v). But 
>> there is nothing and nothing gets copied.
>>
>> I tried the instructions here: https://www.qubes-os.org/doc/copy-paste/ and 
>> removed the # on the 2 lines in /etc/qubes/guid.conf to enforce it's usage:
>>
>> secure_copy_sequence = "Ctrl-Shift-c";
>> secure_pate_sequence = "Ctrl-Shift-v";
>>
>> I also checked the /etc/qubes-rpc/policy/qubes.ClipboardPaste and ensured 
>> that it had the follwoing:
>>
>> dom0   $anyvm   ask
>> $anyvm $anyvm   ask
>>
>> Restarting the whole laptop, after changes did not help.
>>
>> Am I missing something somewhere, from the switch from 3.2 to 4, or is my 
>> install broken?
>>
>> Any ideas are greatly appreciated.
>>
>> Sincerely
>> Max
> 
> I do remember installing the laptop and having minor issues back then with 
> language during install: (https://github.com/QubesOS/qubes-issues/issues/3753)
> 
> Also I had some issues with purism, but maybe not directly related to this: 
> https://forums.puri.sm/t/keyboard-layout-unable-to-recognize-pipe/2022/3
> 
> Is there any way to see what I should produce as output when pressing these 3 
> keys and compare it to the result on my laptop?
> 
> Sincerely
> Max
> 

If you open the VM Manager and go to Qube-> Keyboard Layout what is it
set to ?

Sounds like you are aware cut/paste to terminals doesn't work with
keybinding, I have to use right-click  IIRC

-- 
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/0c0b29dd-aac1-c16b-1442-e79a4367193b%40riseup.net.
For more options, visit https://groups.google.com/d/optout.