From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH test-artifacts v1 5/5] Setup ssh access to test systems
Date: Mon, 23 Jun 2025 16:15:48 +0200 [thread overview]
Message-ID: <aFlhlKc8Pl76SgTW@mail-itl> (raw)
In-Reply-To: <fe0adc4b-8bbf-41d6-b33d-54f5f9f18156@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
On Mon, Jun 23, 2025 at 02:56:00PM +0100, Andrew Cooper wrote:
> On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> > For this add also bridge package, so xenbr0 can be configured with
> > /etc/network/interfaces.
> > This allows extracting more logs out of the test system.
> >
> > Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> > ---
> > This enables passwordless root login. It's okay for qubes runners, as
> > they are isolated (even from each other). Is that okay in other places
> > too?
>
> It's potentially a problem on a corporate network.
>
> Can't we have each job generate a random password an insert it via the
> dom0-rootfs overlay?
>
> Or alternatively have the runner drop a public key in
> /root/.ssh/authorised_keys ?
That can work, yes. And is preferred to a password, as easier to do
non-interactively.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-23 14:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:46 [PATCH test-artifacts v1 0/5] Changes for building arbitrary Linux branch and for hw12 runner Marek Marczykowski-Górecki
2025-06-23 13:46 ` [PATCH test-artifacts v1 1/5] Add linux-6.12.34-x86_64 Marek Marczykowski-Górecki
2025-06-23 13:56 ` Andrew Cooper
2025-06-23 20:45 ` Stefano Stabellini
2025-06-23 13:46 ` [PATCH test-artifacts v1 2/5] Enable CONFIG_USB_RTL8152 in kernel for hw12 runner Marek Marczykowski-Górecki
2025-06-23 13:57 ` Andrew Cooper
2025-06-23 20:45 ` Stefano Stabellini
2025-06-23 13:46 ` [PATCH test-artifacts v1 3/5] Include git in the ARM64 build container too Marek Marczykowski-Górecki
2025-06-23 14:02 ` Andrew Cooper
2025-06-23 20:45 ` Stefano Stabellini
2025-06-23 13:46 ` [PATCH test-artifacts v1 4/5] Support building arbitrary Linux branch/tag/commit Marek Marczykowski-Górecki
2025-06-23 21:01 ` Stefano Stabellini
2025-06-23 13:46 ` [PATCH test-artifacts v1 5/5] Setup ssh access to test systems Marek Marczykowski-Górecki
2025-06-23 13:56 ` Andrew Cooper
2025-06-23 14:15 ` Marek Marczykowski-Górecki [this message]
2025-06-23 20:50 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aFlhlKc8Pl76SgTW@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.