On Wed, Nov 02, 2022 at 10:44:11AM +0100, Michal Suchánek wrote:
> why is Qubes limited to x86?
[...]
> arm64 on the other hand does have Xen port already.
a.) because this is a rather recent thing and
> So is tehre anything actually blocking running Qubes on non-x86?
b.) someone (tm) has to
On Wed, Aug 31, 2022 at 06:02:23PM -0400, Demi Marie Obenour wrote:
> I hope so too, and I would like it to become fast enough to be the
> default.
I have the same concern. On slow computers (eg x230) it's not only slow
but might also be using one cpu 100%
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
On Sun, Feb 13, 2022 at 11:52:53AM +0100, David Hobach wrote:
> I never stated it is. It was just a general comment on code review and
> bash in specific - especially since I'm aware that Qubes has a lot of
> bash in sometimes security relevant places (qubes-dom0-update, qubes-rpc,
> ...).
ah,
On Sat, Feb 12, 2022 at 01:03:35PM +0100, David Hobach wrote:
> just stumbled across it and was wondering what a reviewer would expect from
> this code to do:
[...]
> At least on my amchine it executes "badCode" in both domU and dom0.
I might miss where you stumbled upon this, but how is this
On Tue, Feb 08, 2022 at 03:29:04AM +0100, Marek Marczykowski-Górecki wrote:
> Generally, booting the installer is more reliable in some cases, since
> it doesn't rely on dom0 being in any usable state.
right.
> But since that may be
> inconvenient at times, you can get shell in initramfs using
hi,
recently I had some hw issues which I needed to debug so I tried
booting with systemd rescue mode (by appending systemd.unit=rescue.target
to the kernel cmdline) but that failed because the root account is locked
on Qubes.
So I'm wondering what is the recommended resuce mode for Qubes?
On Wed, Mar 31, 2021 at 10:13:49AM +0200, Frédéric Pierret wrote:
> > I guess you have ran diffoscope on two builds, how is the result? Do you
> > already have this in CI too? (this is for testing for reproducible
> > builds...)
> Not yet but I've discussed few days ago with Marek on how to do
Hi Frédéric,
On Sun, Mar 21, 2021 at 11:33:05PM +0100, Frédéric Pierret wrote:
> Due to recent troubles with kernels 5.4.X and 5.10.X, I've decided to add
> again to this weekly pipeline, the build of a fresh Qubes R4.1 ISO. I don't
> build any package or any template. It uses only Qubes OS
On Mon, Jul 27, 2020 at 04:04:07AM +0200, Marek Marczykowski-Górecki wrote:
> > If I recall correctly, they use signatures on *source* packages,
> > but not on *binary* packages.
> Yes. And those formats are completely different.
well. technically, signed .changes files are uploaded, these
On Fri, May 29, 2020 at 09:33:24AM +, tetrahedra via qubes-devel wrote:
> I find the markdown files are human-readable enough for troubleshooting
> purposes that I can just read them with vim.
same here.
--
cheers,
Holger
hi Mihai,
On Fri, May 29, 2020 at 12:17:13PM +0200, Mihai Moldovan wrote:
> Sorry for the late response. I've been busy, and, honestly, also always forgot
> to actually answer.
thanks for your reply & don't worry, this happens often & to many people, me
included.
> unman seems to be
Hi unman,
On Sun, May 03, 2020 at 05:07:14PM +0100, unman wrote:
> I'd be happy to take on maintenance of this package, and may be anything
> else that's Qubes required but seems to be lapsing in Debian.
cool. I'll be happy to review & sponsor these uploads to Debian!
> Also, I wonder if there
Hi Mihai,
On Fri, Sep 13, 2019 at 05:36:55PM +0200, Mihai Moldovan wrote:
> I've packaged DNF
cool!
> for Debian and would like to find someone to take over these
> packages and maintain them as part of the distribution.
>
> I'm not a DD and while I believe the packages to be of reasonable if
On Wed, Mar 20, 2019 at 01:57:47AM +0100, Marek Marczykowski-Górecki wrote:
> https://ftp.qubes-os.org/~qubesosbot/status.html
> It's updated daily.
very nice, thank you! :)
--
tschau,
Holger
---
On Wed, Feb 06, 2019 at 05:54:29PM +0100, Marek Marczykowski-Górecki wrote:
> It may be a good idea to introduce regular schedule for stable [point
> releases[1]. It would minimize the need to download a lot of updates
> just after installation. This is even more significant, if some updates
> may
On Sun, Dec 23, 2018 at 02:48:55AM +0100, Marek Marczykowski-Górecki wrote:
> Also note that we'd like to have at least some level of hiding metadata
> - like VM names (leaked through file names).
I think it would be nice if this was an optional feature (on by
default), as I find it super
On Fri, Oct 05, 2018 at 10:26:18PM -0500, Andrew David Wong wrote:
> the Qubes OS
> Project will continue to support Qubes 3.2 as planned until 2019-03-28. [6]
thank you, Qubes OS!
> [...] Users who decide to continue using Whonix on Qubes 3.2 do so
> at their own risk.
this has been the case
On Thu, Sep 13, 2018 at 09:00:40PM -0500, Andrew David Wong wrote:
> * One month after a new stable version of Qubes OS is released, Whonix
>TemplateVMs will no longer be supported on any older version of Qubes
>OS.
I'm quite disappointed by this.
--
cheers,
Holger
On Thu, Sep 13, 2018 at 12:58:20AM +0200, Marek Marczykowski-Górecki wrote:
> The alternative would be releasing Qubes 3.2.1 as is, adding a note that
> single-layer DVD is not enough for installation. Since this release is
> looong overdue, I tend to this option, but want to hear opinions of
>
On Thu, May 24, 2018 at 07:29:18PM -0500, Andrew David Wong wrote:
> Thank you for the correction. I've updated the announcement on the
> website to clarify this:
> https://github.com/QubesOS/qubes-posts/commit/3db9a35e297b3defa0863f8ab02ebd56e8384053
thank you, looks good!
--
cheers,
On Mon, May 14, 2018 at 11:30:09AM -0400, Jean-Philippe Ouellet wrote:
> On Mon, May 14, 2018 at 11:26 AM, Holger Levsen <hol...@layer-acht.org> wrote:
> > On Mon, May 14, 2018 at 11:20:29AM -0400, Jean-Philippe Ouellet wrote:
> >> The immediate impact on Qubes developer
On Mon, Mar 12, 2018 at 08:43:47PM +0100, Marek Marczykowski-Górecki wrote:
> Hmm, indeed something is not right. But since the removal failed, it
> should be safe...
"should"...
> What was your previous qubes-core-agent package version?
3.2.22-1+deb9u1
> > and the missing dconf commands feels
hi,
I just upgraded my 3.2 installation and on Debian 9 templates I saw
this:
Preparing to unpack .../qubes-core-agent_3.2.25-1+deb9u1_amd64.deb ...
Unpacking qubes-core-agent (3.2.25-1+deb9u1) over (3.2.22-1+deb9u1) ...
dpkg: warning: unable to delete old directory '/var/run/qubes': Directory
On Wed, Jan 24, 2018 at 04:29:14PM +0100, Marek Marczykowski-Górecki wrote:
> On Wed, Jan 24, 2018 at 06:35:15AM -0800, joeh9...@gmail.com wrote:
> > Hi, this is in no way meant to appear impatience but I'm going to install
> > Qubes OS on my new laptop (Lenovo P71) and am just wondering whether
On Tue, Jan 23, 2018 at 02:47:30PM +0100, 'Tom Zander' via qubes-devel wrote:
> On Tuesday, 23 January 2018 03:13:17 CET Kelly Dean wrote:
> > If a user needs Qubes, that means he needs more security than a
> > conventional OS gives.
> I'd like to challange that assumption.
me too. Qubes is
On Thu, Jan 18, 2018 at 03:16:26PM +0100, Marek Marczykowski-Górecki wrote:
> Let me try (on f26):
> $ sakura
hmpf. I've only tried in on f25… (IOW: still using xterm in dom0 as less
is more there.)
--
cheers,
Holger
--
You received this message because you are subscribed to the
On Thu, Jan 18, 2018 at 02:58:14PM +0100, 'Tom Zander' via qubes-devel wrote:
> Thats rather unfortunate, I would suggest trying Konsole as an alternative,
I found "sakura" to be much more lightweight and still supporting
font-resizing with ctrl+(plus|minus) by default. It's also available on
On Sun, Jan 14, 2018 at 04:28:49PM -0600, Andrew David Wong wrote:
> I agree that:
>
> 1. We should keep our promise to support R3.2 for a full year after the
>release of R4.0 stable.
>
> 2. We should not force R3.2 users to install an upgrade that may break
>their stable installations.
On Mon, Dec 11, 2017 at 12:45:34PM -0500, Jean-Philippe Ouellet wrote:
> Marmarek or HW42 could probably give you better answers, but the
> following is my understanding:
>
> The terminology is admittedly somewhat confusing, especially since Xen
> people no longer talk about a discrete set of
On Mon, Oct 16, 2017 at 03:45:24PM +0200, Marek Marczykowski-Górecki wrote:
> Given those two options, we've decided it's better to have cleaner
> situation longterm (option 2) at the cost of less convenient rc stage,
> than the other way around. After all, we'll need to support this for a
> much
On Fri, Aug 25, 2017 at 09:16:07PM +0200, Marek Marczykowski-Górecki wrote:
> I see a few options for this problem:
>
> 1. Use "unstable" repository for non-longterm kernels. We've done this
> before, for 4.8 kernels. [...] Or create new repository specifically for
> non-longterm kernels.
I like
On Tue, Aug 15, 2017 at 04:05:27PM +0200, Marek Marczykowski-Górecki wrote:
> Actually:
> sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing
q.e.d. & thanks!
--
cheers,
Holger
--
You received this message because you are subscribed to the Google Groups
"qubes-devel"
Hi,
first of all: thanks for this handling this update!
On Tue, Aug 15, 2017 at 08:31:31AM -0500, Andrew David Wong wrote:
> Patching
> =
[...]
> The packages are to be installed in dom0 via the qubes-dom0-update command or
> via the Qubes VM Manager. A system restart will be required
On Mon, Jun 19, 2017 at 09:30:37AM +0200, Marek Marczykowski-Górecki wrote:
> > > As for Qubes 3.2.1 - exactly as Reg said - it's blocked on 4.9 kernel
> > > testing.
> > does it not make sense to anyone else that at the least the testing
> > image should also be released to get more eyes on it
On Tue, May 30, 2017 at 02:21:57AM +0200, Marek Marczykowski-Górecki wrote:
> > > Package: qubes-core-agent-network
> > > Package: qubes-core-agent-network-manager
> > maybe qubes-core-agent-network_ing_(-support) and
> > qubes-core-agent-network-manager?
> Those names are long enough
On Mon, May 29, 2017 at 07:30:04AM +0200, Marek Marczykowski-Górecki wrote:
> > > > While at it - is it better to name it qubes-nautilus or
> > > > qubes-core-agent-nautilus?
> > >
> > > I think the latter is definitly better than the former, but maybe
> > > rather
Hi Marek,
sorry for the late reply…
On Mon, Apr 24, 2017 at 02:08:39AM +0200, Marek Marczykowski-Górecki wrote:
> Currently the package in title is "everything but the kitchen sink" type
> of package. It contains at least:
>
> - qrexec-agent
> - all kind of qrexec services (file copy, etc)
>
Hi Marek,
sorry for the late reply, your replies often include lots of data to process…
that's awesome just sometimes hard to find the time to :)
Thanks a lot for all this information!
On Tue, Mar 07, 2017 at 12:36:17AM +0100, Marek Marczykowski-Górecki wrote:
> Yes, we currently do not fill
Hi,
I just did a dom0 upgrade and was offered to update qubes-gui-dom0 to version
3.2.9-1.fc23, however when I clicked on "package changelog" in yum-extender
the changelog was empty.
This has happened before…
So I'm wondering: how can I find out, what has changed and why does Qubes 3.2
receive
On Tue, Dec 20, 2016 at 03:15:29PM -0500, Jean-Philippe Ouellet wrote:
> > CTRL-Shift-K maybe?
> Is this because you are worried about accidental use? Or some other reason.
yes
> We already do have a confirmation dialog before a VM is actually
> killed, keyboard shortcut or not.
I was aware
Hi,
first of all: yay, keyboard shortcuts! Thanks for your work on this!
two minor comments:
On Tue, Dec 20, 2016 at 02:31:13PM -0500, Jean-Philippe Ouellet wrote:
> 3. Ctrl+C for Clone, because Clone and Copy start with C
> Ctrl+Shift+N may also be a good candidate here, idk.
CTRL-C is
Hi Marek,
thanks for sharing this information. I found it quite interesting!
(and wouldnt mind to see such posts every 3 months or so…)
--
cheers,
Holger
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group
Package: wnpp
Severity: wishlist
Owner: Holger Levsen <hol...@layer-acht.org>
* Package name: qubes-gui-daemon
Upstream Author : Joanna Rutkowska <joa...@invisiblethingslab.com>
* URL : https://github.com/QubesOS/qubes-gui-daemon.git
* License : GPL2+
Prog
Package: wnpp
Severity: wishlist
Owner: Holger Levsen <hol...@layer-acht.org>
* Package name: qubes-gui-common
* Upstream Author : Joanna Rutkowska <joa...@invisiblethingslab.com>
Rafal Wojtczuk <ra...@invisiblethingslab.com>
Marek M
Package: wnpp
Severity: wishlist
Owner: Holger Levsen <hol...@layer-acht.org>
* Package name: qubes-gui-agent
Upstream Author : Joanna Rutkowska <joa...@invisiblethingslab.com>
* URL : https://github.com/QubesOS/qubes-gui-agent-linux.git
* License : GPL2+
Package: wnpp
Severity: wishlist
Owner: Holger Levsen <hol...@layer-acht.org>
* Package name: libvchan-xen-qubes
Upstream Author : Joanna Rutkowska <joa...@invisiblethingslab.com>
Rafal Wojtczuk <ra...@invisiblethingslab.com>
Package: wnpp
Severity: wishlist
Owner: Holger Levsen <hol...@layer-acht.org>
* Package name: qubes-core-agent
Upstream Author : Joanna Rutkowska <joa...@invisiblethingslab.com>
Rafal Wojtczuk <ra...@invisiblethingslab.com>
* URL : https://
Package: wnpp
Severity: wishlist
Owner: Holger Levsen <hol...@layer-acht.org>
* Package name: qubes-core-admin-linux
Upstream Author : Marek Marczykowski <marma...@invisiblethingslab.com>
* URL : https://github.com/QubesOS/qubes-core-admin-linux.git
* License
Package: wnpp
Severity: wishlist
Owner: Holger Levsen <hol...@layer-acht.org>
* Package name: qubes-core-admin
Upstream Author : Joanna Rutkowska <joa...@invisiblethingslab.com>
Rafal Wojtczuk <ra...@invisiblethingslab.com>
* URL : https://
Package: yum
Version: 3.4.3-3
Severity: wishlist
Hi,
to be able to use Debian for sys-firewall VM of Qubes-OS.org yum needs
to support the --downloadonly option, which it currently does not.
Fedora has version 3.4.3-507 so it seems this functionality was added
via a patch. It would be great if
On Sun, Jun 12, 2016 at 01:01:00PM +0200, Marek Marczykowski-Górecki wrote:
> > what version of yum is needed? Debian indeed has only 3.4.3-3, even in
> > unstable :/
> Hmm, Fedora has 3.4.3-507, so I'm afraid --downloadonly option is added
> only in some Fedora local patch :/
hmpf. if that
51 matches
Mail list logo
