: |
No problems noticed. Qubes certified. Very Fast.
credit: |
code9n
link: |
FIXLINK
--
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 q
:8168] (rev 07)
memory: |
65410
scsi: |
Samsung SSD 870 Rev: 1B6Q
usb: |
1
certified:
'no'
versions:
- works:
'yes'
qubes: |
R4.2.0
xen: |
4.17.2
kernel: |
6.1.62-1
remark: |
Everything seems fine
credit: |
code9n
link: | FIXLINK
.cpio attached.
Thanks for 4.2
On Sunday, January 21st, 2024 at 09:45
Hi,
This is on the Forum:
https://forum.qubes-os.org/t/wireguard-vpn-setup/19141
cheers,
On Saturday 6 January 2024 at 00:16:40 UTC r.wie...@web.de wrote:
> Hi there,
>
> vpnVM and netVM both in-place upgrades from Q4.1 (and worked fine
> there). Template is fedora 38.
> NetVM is online,
, and I'm loving 4.1.
On Friday, 5 November 2021 at 00:46:42 UTC marm...@invisiblethingslab.com
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Thu, Nov 04, 2021 at 03:16:22PM -0700, code9n wrote:
> > Note: Made a Tasket Qubes vpn support networking qube on Qubes
it actually
does use the English UK layout.
Apologies if I should have answered this in a different place.
On Friday, 5 November 2021 at 00:42:54 UTC marm...@invisiblethingslab.com
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Thu, Nov 04, 2021 at 03:10:20PM -0700,
Note: Made a Tasket Qubes vpn support networking qube on Qubes 4.1 rc1
which works efficiently as always but when I check the 'start qube
automatically on boot' box in Qube Settings / manager gui it won't save if
I click on 'apply' first.
But it will save if I just check the box then click
Note: I carefully made sure the GB / UK keyboard option was selected
during install but have the US set up on my UK keyboard Lenovo T430.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
Amendment: I forgot, there was one installation problem - I couldn't get
sys-USB to work, had to do it after install. Sorry about that.
On Sunday, 8 August 2021 at 02:21:23 UTC+1 sv...@svensemmler.org wrote:
> Thank you code9n for your HCL report, which is now part of [this pull
> r
Machine made with Qubes 4.0 in mind by Think Penguin - around a year before
Qubes 3.2 reached EOL.
Hope this is helpful. Thanks to all involved in Qubes OS.
If your machine fulfills these criteria:
* Qubes OS R4.0.4 installs without any workarounds - YES
* Graphics, networking & audio work
Having this same (old now) problem.
Tried adding --releasever=4.0 to sudo qubes-dom0-update and I get most of
the update to download but not all of it.
Unman suggested : "you could manually
download it, copy it to dom0, check signature in dom0 with rpm -K, and
then install."
Which
The pulseaudio issue was fixed in August? I've been waiting for that since
the upgrade to fedora 27. Looked out for it in every fedora update and never
saw it. (Now using fedora 28 - still no sound) - All updates completed that I
know of.
Do you need to have the Qubes 4 developers
Hi Nick,
In case it's any use to you;
I had a couple of vpns working on Q3.2 until about a week ago (moved to 4.0)
and one of them was Expressvpn.
What I did to set it up:
Make a clone of my up to date fedora template ( or use Debian or whatever
you like).
Allow network access
I gave up on trying to back date whonix - there's so much about it on Whonix /
Whonix-Qubes website and warnings about messing with the clock in Whonix ws
konsole I didn't want to mess about.
Tried (in Whonix ws) update-torbrowser chosing 7.5.6 but got the signature
expired message so in the
Same issue but when I try to update-torbrowser (or via Tor Browser Downloader)
the install fails because ttb's signature has expired.
I have to wait for the tor project to resign ttb (7.5.6), right? If I tried to
get the key that comes with it from torproject.org and import it into Whonix
Thanks, you're right. I remembered I had the same problem when I installed
3.2. Disabled wifi adapter in sys-net and it worked. Same this time.
Probably because I haven't got a wifi card - it's a desktop and I only use an
ethernet cable.
--
You received this message because you are
Hi,
I made r4 installation USBs many times to install r4 over the last couple of
days - first fedora media writer in Q3.2, then from Windows with rufus with
several different USB sticks and several different downloads. The downloads
always completed properly, like wise writing onto the
...but only by a day (see Qubes canary #14 -
https://github.com/QubesOS/qubes-secpack/blob/master/canaries/canary-014-2017.txt)
--
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
Solved.
Not sure if it was relevant but since the most recent Whonix updates this has
gone back to normal.
Thanks to all.
--
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
Yeh, the anon-whonix app vm is routed through sys-whonix properly. I haven't
changed that from default.
I do route most non-whonix app vms through a vpn in a proxy vm but that all
works as it should.
Both systems have worked independently and as expected for months.
Checking today some IP
Running the WhonixCheck from the default anon-whonix app vm in the Qubes
manager list; the fail warning basically says:
SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to host])
The browser - anon-whonix app vm (default)/Tor browser - opens like normal to
the Whonix page
20 matches
Mail list logo
