Hi,
Updating my qubes templates (debian-9, fedora-29/-30, whonix-14) have
been failing all day with `Failed to synchronize cache for repo
'qubes-vm-r4.0-current'`
There's also this bug report:
https://github.com/QubesOS/qubes-issues/issues/5130
Any updates?
thank you!
-m0ssy
--
You received
g80vmgm...@riseup.net:
> mossy:
>> Hello Qubes Community,
>>
>> Has anyone noticed the blue/white noscript S button is missing since a
>> recent whonix-torbrowser update? AFAIK this is needed use javascript in
>> whonix.
>>
>> Anyone notice this
Hello Qubes Community,
Has anyone noticed the blue/white noscript S button is missing since a
recent whonix-torbrowser update? AFAIK this is needed use javascript in
whonix.
Anyone notice this or have a workaround?
thx!
-m0ssy
--
You received this message because you are subscribed to the Go
unman:
> On Wed, Dec 19, 2018 at 11:06:25PM +0000, mossy wrote:
>> Hello all,
>>
>> I was looking to see if I could update an offline standalone VM, by
>> appending a line to `etc/qubes-rpc/policy/qubes.UpdatesProxy` and I now
>> have some questions.
Hello all,
I was looking to see if I could update an offline standalone VM, by
appending a line to `etc/qubes-rpc/policy/qubes.UpdatesProxy` and I now
have some questions.
First, I noticed the lines:
~~~
# Default rule for all TemplateVMs - direct the connection to sys-net
$type:TemplateVM $defa
John Smiley:
> I only ask because my, admittedly limited, exposure left me with no
> confidence at all that it would protect me. I was hitting software and doc
> bugs left and right. They haven’t gotten basics down yet, so no way I can
> trust. Fun toy though.
It's important to understand tha
799:
> I have setup /rw/config/gpg-split-domain to include the Vault AppVM as
> described in the Qubes 3.2 documentation.
> It seems that Enigmail needs this setting.
hey thanks to both of you for troubleshooting this, indeed this is
required and fixed my enigmail split-gpg woes under whonix-ws-14
mossy:
> Patrick Schleizer:
>> qubes-...@tutanota.com:
>>> Hi, I learned that in Whonix-14 in Qubes 4.0 there is no default support
>>> for pEp in Enigmail-Thunderbird. Is it Qubes specific or Whonix specific?
>>> Is there any reason for not supporting pEp in
Patrick Schleizer:
> qubes-...@tutanota.com:
>> Hi, I learned that in Whonix-14 in Qubes 4.0 there is no default support for
>> pEp in Enigmail-Thunderbird. Is it Qubes specific or Whonix specific? Is
>> there any reason for not supporting pEp in Whonix?
>>
>> In other templates after installing
qubes-...@tutanota.com:
> Should I put it into the ~/.bash_profile of which VM: vault-safe VM or work
> VM in this case?
>
> --
> Securely sent with Tutanota. Claim your encrypted mailbox today!
> https://tutanota.com <https://tutanota.com>
>
> 10. May 201
mossy:
>>> On 05/14/2018 10:33 AM, magionemagi...@gmail.com wrote:
>>> I know that right now details are sketchy but the advice of disabling
>>> PGP is sound at least until we get to know more information, especially
>>> since it's coming from reputable res
>> On 05/14/2018 10:33 AM, magionemagi...@gmail.com wrote:
>> I know that right now details are sketchy but the advice of disabling
PGP is sound at least until we get to know more information, especially
since it's coming from reputable researchers and the EFF (links below
but I guess everybody her
mossy:
> 'awokd' via qubes-users:
>> Think I got it working with the -14 templates from unstable. In dom0:
>>
>> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable
>> qubes-template-whonix-gw-14
>> qvm-create sys-whonix-14 --class AppVM --template
'awokd' via qubes-users:
> Think I got it working with the -14 templates from unstable. In dom0:
>
> sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable
> qubes-template-whonix-gw-14
> qvm-create sys-whonix-14 --class AppVM --template whonix-gw-14 --label black
> qvm-prefs sys-whonix-14 provid
qubes-...@tutanota.com:
> I set up the split-gpg with vault-safe VM, where my private keys are stored,
> and the work VM, with pub keys and server communication.
>
> All runs well after executing the
> [user@work ~]$ export QUBES_GPG_DOMAIN=vault-safe
>
> The issue is, that the export doesnt s
john:
> Q4.0 Whonix Torbrowser no sound, says to install pulseaudio ...
>
> but is that a plugin for the AppVM or something to install in Whonix-ws
> Template or ? am confused
>
This issue (and others) are resolved in whonix 14, now in testing -- you
can upgrade here:
https://www.whonix.org/
Michael Carbone:
>
>
> On 03/27/2018 01:58 PM, 'TFQOS' via qubes-users wrote:
>> On 27 March 2018 5:40 PM, cubit wrote:
>>
>>> 27. Mar 2018 09:45 by mich...@qubes-os.org:
>>>
couldn't figure out a fast solution so I downgraded back to v1.9.9 for
the time being.
You can do the
Michael Carbone:
> On 03/27/2018 06:41 AM, 'Eric Barrett' via qubes-users wrote:
>> On Tuesday, March 27, 2018 at 5:45:56 AM UTC-4, Michael Carbone wrote:
>>> couldn't figure out a fast solution so I downgraded back to v1.9.9 for
>>> the time being.
>>>
>>> You can do the same by downloading v1.9.9
Todd Lasman:
> On 12/11/17 14:58, Sven Semmler wrote:
>> I just get started with R4 and restored my email vm. Everything works
>> great, except that now everytime I am in the To: of Subject: line I get
>> a pop-up from dom0 asking:
>>
>> [dom0] Operation execution
>>
>> Do you want to allow the fol
xxx.l...@gmail.com:
> On Wednesday, January 17, 2018 at 9:08:40 AM UTC+8, mossy-nw wrote:
>> miaoski:
>>
>> Just checking in to see if you (or anyone) is still using that laptop
>> and has made the switch to Qubes R4 and has an easy fix. I'll post more
>&g
Hello,
I noticed for Qubes R4.0 the package `qubes-usb-proxy` must be installed
in the fedora-26-minimal to serve as template for sys-usb (and in any
destination usb proxy domain, e.g. sys-net if using a usb ethernet
adapter). I've added the relevant pull request to Qubes 4.0 section of
the minim
Marek Marczykowski-Górecki:
> On Thu, Jan 18, 2018 at 07:21:14PM +0000, mossy-nw wrote:
>> OK thanks, Marek. I'll try to help get that backup bug reproduced
>> then... should I file a permissive mode bug report based on this
>> discussion, or do you feel like all of the
'[799]' via qubes-users:
> Sorry for my first empty email, which has been send to early.
>
> I am using a fedora template which has wäre Horizon View installed, so that I
> can use the AppVM to access my corporate desktop.
>
> I can start the application, login, launch my virtual desktop and work
Marek Marczykowski-Górecki:
> On Thu, Jan 18, 2018 at 01:05:46AM +0000, mossy-nw wrote:
>> Marek Marczykowski-Górecki:
>>> On Wed, Jan 17, 2018 at 11:54:23PM +, mossy-nw wrote:
>>>> Dear Qubes community,
>>>
>>>> Has anyone using Qu
Marek Marczykowski-Górecki:
> On Wed, Jan 17, 2018 at 11:54:23PM +0000, mossy-nw wrote:
>> Dear Qubes community,
>
>> Has anyone using Qubes R4.0 been able to resolve any issues (e.g. with
>> wifi) by setting PCI permissive mode? (as described in:)
>
>> https
Dear Qubes community,
Has anyone using Qubes R4.0 been able to resolve any issues (e.g. with
wifi) by setting PCI permissive mode? (as described in:)
https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues
I successfully used this in Qubes R3.2 to get wifi working for dell xps
13
miaoski:
> Hi.
>
> A simple solution is to use PCIe permissive mode, which weakens device
> isolation.
> Please refer to "PCI passthrough issues" of
> https://www.qubes-os.org/doc/assigning-devices/
>
> Although there is a dmesg saying
> [2.411487] brcmfmac :00:00.0: Direct firmware loa
I've experienced this, too. It could be a side-effect of a recent
presumably security enhancement disabling qvm-copy-to-vm and
qvm-move-to-vm, replacing with qvm-copy and qvm-move, requiring the user
to enter the target domain in a dom0 confirmation popup window.
using qvm-copy-to-vm (within a VM
Styles Grant:
> Obviously theres some issues with amd discreet gpu and qubes, to put it
> slightly. Uh, theres one example on the hardware compatibility list that
> stood out though as a bit of encouragement
>
> "ASRock AB350 Pro4
> Ryzen 5 1600 AMD AMD Radeon HD"
>
> Uh, I'd like to try. I've
29 matches
Mail list logo