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

2019-02-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 14/02/2019 1.27 PM, Vít Šesták wrote: > On February 14, 2019 6:18:47 PM GMT+01:00, "Marek Marczykowski-Górecki" wrote: >> On Thu, Feb 14, 2019 at 05:58:09PM +0100, Vít Šesták wrote: >>> When I update dom0 and then Debian/Whonix without restarting

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

2019-02-14 Thread Vít Šesták
On February 14, 2019 6:18:47 PM GMT+01:00, "Marek Marczykowski-Górecki" wrote: >On Thu, Feb 14, 2019 at 05:58:09PM +0100, Vít Šesták wrote: >> When I update dom0 and then Debian/Whonix without restarting the Qube >Manager or Update “widget”*, is it enough? Or I need to restart the >updater app (or

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

2019-02-14 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Feb 13, 2019 at 04:12:27AM -0800, Vít Šesták wrote: > Since Qubes 4.0.1 was released [1] before your message and before the DSA > [2], I assume it is not a good idea to install Debian and Whonix from the > 4.0.1 installation media, is it?

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

2019-02-13 Thread Vít Šesták
Since Qubes 4.0.1 was released [1] before your message and before the DSA [2], I assume it is not a good idea to install Debian and Whonix from the 4.0.1 installation media, is it? If it is right, then I suggest adding a note on the download page [3] until 4.0.2 release. Regards, Vít Šesták

[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

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

2019-01-26 Thread Aly Abdellatif
@John S.Recdep 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 -- You received this message because you are subscribed to the Google Groups

[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

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

2019-01-26 Thread Aly Abdellatif
@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 -- You received this message because you are subscribed to the Google

[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 >

[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

[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

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

2019-01-24 Thread pixel fairy
On Thursday, January 24, 2019 at 7:35:59 PM UTC-8, Andrew David Wong wrote: > pixel fairy, please let us know of fully removing the old template first > doesn't fix the problem. thats what i ended up doing. i had to reinstall to delete them. then it worked. then, with whonix, sys-firewall was

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

2019-01-24 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 24/01/2019 9.15 PM, Marek Marczykowski-Górecki wrote: > On Thu, Jan 24, 2019 at 08:57:16PM -0600, Andrew David Wong wrote: >> On 23/01/2019 11.54 PM, Chris Laprise wrote: >>> On 01/23/2019 10:39 PM, Andrew David Wong wrote: On 23/01/2019

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

2019-01-24 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Jan 24, 2019 at 08:57:16PM -0600, Andrew David Wong wrote: > On 23/01/2019 11.54 PM, Chris Laprise wrote: > > On 01/23/2019 10:39 PM, Andrew David Wong wrote: > >> On 23/01/2019 9.36 PM, pixel fairy wrote: > >>> On Wednesday, January 23,

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

2019-01-24 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 23/01/2019 11.54 PM, Chris Laprise wrote: > On 01/23/2019 10:39 PM, Andrew David Wong wrote: >> On 23/01/2019 9.36 PM, pixel fairy wrote: >>> On Wednesday, January 23, 2019 at 7:24:57 PM UTC-8, Andrew David Wong >>> wrote: >>> The Whonix

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

2019-01-24 Thread Lorenzo Lamas
On Thursday, January 24, 2019 at 4:13:36 PM UTC+1, Lorenzo Lamas wrote: > Please help, after updating dom0 with security-testing(which installed not > only qubes-desktop-linux-manager and qubes-manager, but also > qubes-mgmt-salt-dom0-update-4.0.5-1 and reboot, no VM at all will start. > Failed

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

2019-01-24 Thread Lorenzo Lamas
Please help, after updating dom0 with security-testing(which installed not only qubes-desktop-linux-manager and qubes-manager, but also qubes-mgmt-salt-dom0-update-4.0.5-1 and reboot, no VM at all will start. Failed to connect to qmmemman:[Errno 2] No such file or directory. Text boot shows:

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

2019-01-23 Thread Chris Laprise
On 01/23/2019 10:39 PM, Andrew David Wong wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 23/01/2019 9.36 PM, pixel fairy wrote: On Wednesday, January 23, 2019 at 7:24:57 PM UTC-8, Andrew David Wong wrote: The Whonix packages are in qubes-templates-community-testing. $ sudo

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

2019-01-23 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 23/01/2019 9.36 PM, pixel fairy wrote: > On Wednesday, January 23, 2019 at 7:24:57 PM UTC-8, Andrew David Wong wrote: > >> The Whonix packages are in qubes-templates-community-testing. > > > $ sudo qubes-dom0-update

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

2019-01-23 Thread pixel fairy
On Wednesday, January 23, 2019 at 7:24:57 PM UTC-8, Andrew David Wong wrote: > The Whonix packages are in qubes-templates-community-testing. $ sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing qubes-template-whonix-gw-14 Using sys-firewall as UpdateVM to download updates

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

2019-01-23 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 23/01/2019 8.53 PM, pixel fairy wrote: > is whonix in the repo? i keep getting "Error: Unable to find a > match" tried copy/pasting from the command to delete the templates > to make sure they're spelled right. tried qubes-templates-itl and >

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

2019-01-23 Thread pixel fairy
is whonix in the repo? i keep getting "Error: Unable to find a match" tried copy/pasting from the command to delete the templates to make sure they're spelled right. tried qubes-templates-itl and qubes-templates-itl-testing. -- You received this message because you are subscribed to the Google