Franz:
> On Tue, Aug 14, 2018 at 1:55 PM, Patrick Schleizer <
> patrick-mailingli...@whonix.org> wrote:
>
>> Franz:
>>> when I try to uninstall whonix-ws
>>>
>>> sudo dnf remove qubes-template-whonix-ws*
>>>
>>> I get
>>> No match for argument: qubes-template-whonix-ws*
>>> Error: No packages
Please contribute here:
https://www.whonix.org/wiki/Qubes/Disposable_VM
sm...@tutamail.com:
> 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
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
https://getmonero.org/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.html
is missing how to actually use it.
I guess it is simply: run `monero-wallet-cli` or monero gui in
monero-wallet-ws."
0xB44EFD8751077F97:
> Patrick Schleizer:
>> I didn't notice this thread until now.
>>
>>
On Tue, Aug 14, 2018 at 1:55 PM, Patrick Schleizer <
patrick-mailingli...@whonix.org> wrote:
> Franz:
> > when I try to uninstall whonix-ws
> >
> > sudo dnf remove qubes-template-whonix-ws*
> >
> > I get
> > No match for argument: qubes-template-whonix-ws*
> > Error: No packages marked for
On 08/15/2018 08:40 AM, Rusty Bird wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sphere:
https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/
There are other vulnerabilities disclosed along with this today and
On Wednesday, August 15, 2018 at 8:50:28 PM UTC+8, Rusty Bird wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Sphere:
> > https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/
> >
> > There are other
Surely you have checked that your boot sequence really starts at the HDD where
you installed qubes right? I got a case where my bios completely could not
recognize the drive where I installed my Qubes as bootable and had to do sum
stuff in the Boot sector to make it work. The same may apply to
On 08/07/2018 06:41 PM, perme...@gmail.com wrote:
> Q: if a domU kernel enables VF devices in a mapped PF device instance, will
> the dom0 kernel discover the VF devices? IE: what is the mechanism whereby a
> kernel discovers the need for a bus-walk?
> This has to work correctly for Xen, no?
Hmm, thats strange because it is working for me and it was working for you
before.
I've updated the github version to explicit install cryptsetup.
Please let me know if this fixes the problem.
On Wed, Aug 15, 2018 at 9:45 PM, Joeviocoe Gmail
wrote:
> Thanks. Something messed up though.
>
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
On Wed, Aug 8, 2018 at 1:30 PM, <3mp...@gmail.com> wrote:
> Hi everyone,
>
> actually I'm a happy Qubes 3.2 user on Intel platform for more than a year
> now !
>
> I'm looking to upgrade my actual Skylake build with an AMD one with the new
> Ryzen Pinnacle Ridge CPU (R7 2700) and installing
Thanks. I'll try it.
What's the best to add the UUID? I assume edit the grub.cfg directly. But
will kernel updates overwrite? Do I need to edit something else and run dracut
-f?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
Hi,
i've modified the module to support multiple LUKS devices (UUIDs). It works
with my setup which has only one LUKS device but it should work with more
than one.
You have to add the UUIDs of you luks devices separated by comma (e.g.
rd.ykluks.uuid=UUD1,UUID2,UUID3).
Hope this works and happy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sphere:
> https://www.bleepingcomputer.com/news/security/researchers-disclose-new-foreshadow-l1tf-vulnerabilities-affecting-intel-cpus/
>
> There are other vulnerabilities disclosed along with this today and
> if possible, I would like to confirm
> Please note that the current version will probably not work with a default
> qubes LUKS-on-LVM installation. But if some experienced user is willing to
> help testing i'll try to come up with a version that supports this too.
>
> Besides the yubikey/luks stuff the module handles the
On Wed, August 15, 2018 4:22 am, taii...@gmx.com wrote:
> On 08/12/2018 03:36 PM, 'awokd' via qubes-users wrote:
>
>>
>> No experience with that exact configuration. You can often passthrough
>> devices individually even if they are in the same IOMMU group (older
>> versions of Xen had trouble).
>
On Tuesday, August 14, 2018 at 4:36:29 PM UTC+1, Pablo Di Noto wrote:
> Kudos to the `qvm-volume revert` feature!
>
> I just did
> ```
> qvm-volume info debian-9-root
> qvm-volume revert debian-9-root XX-back
> ```
> and went back to the pre-update template and the issue disappeared.
>
>
On Mon, August 13, 2018 5:03 pm, Djon Snow wrote:
> понедельник, 13 августа 2018 г., 13:24:52 UTC+3 пользователь awokd
> написал:
>> At which step of
>> https://www.qubes-os.org/doc/pentesting/kali/#katoolin3_2
>> or
>> https://www.qubes-os.org/doc/pentesting/kali/#templatevm-from-debian3_2
>> ?
On Tue, August 14, 2018 5:03 am, joevio...@gmail.com wrote:
> $ qvm-create --verbose Win10 --class StandaloneVM --property
> virt_mode=hvm --property kernel='' --property memory=4096 --property
> maxmem=4096 --label=red --root-copy-from Win10.raw
How large is the root created when you use this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-08-14 21:38, Sphere wrote:
> CVE-2018-3646 in particular is alarming:
> "The third flaw, CVE-2018-3646, has a CVSS Base Score of 7.1 and enables bad
> actors to attack virtual machines (VM), via virtualization software and
> Virtual
On 08/12/2018 03:36 PM, 'awokd' via qubes-users wrote:
>
> No experience with that exact configuration. You can often passthrough
> devices individually even if they are in the same IOMMU group (older
> versions of Xen had trouble).
This is a bad recommendation security wise and I expect better
22 matches
Mail list logo
