public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 05/11] image-account-extension: Add copy-ci-key flag for user
Date: Wed, 25 Jan 2023 09:45:43 +0100	[thread overview]
Message-ID: <20230125094543.296194ac@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <1900519.7Z3S40VBb9@hp>

Am Wed, 25 Jan 2023 10:36:55 +0300
schrieb Uladzimir Bely <ubely@ilbers.de>:

> In mail from вторник, 24 января 2023 г. 10:18:28 +03 user Henning
> Schild wrote:
> > Am Tue, 24 Jan 2023 08:09:24 +0100
> > 
> > schrieb Henning Schild <henning.schild@siemens.com>:  
> > > Am Fri, 13 Jan 2023 08:19:36 +0100
> > > 
> > > schrieb Uladzimir Bely <ubely@ilbers.de>:  
> > > > If the flag enabled, CI ssh public key is copied
> > > > `authorized_keys` in `$USER/.ssh/` directory.
> > > > 
> > > > This allows non-interactive SSH access to the machine with
> > > > executing custom commands on the guest VM.  
> > > 
> > > I would suggest to make that a debian raw package, examples on
> > > how to do that can be found in many public layers.
> > > 
> > > You could i.e. drop an authorized-keys file into /etc/ssh/ and
> > > using postinst append/change the AuthorizedKeysFile line in the
> > > global ssh config  
> > 
> > Create the user ci like we create the user isar in example-raw, and
> > drop that file into HOME/.ssh/, maybe depend on sudo and make sure
> > that user can run any command without password.
> > We could also use a trivial password and not have a key at all.
> > 
> > And when it is a package we can depend on regen-keys.
> > 
> > Henning
> >   
> 
> Yes, it sounds reasonable. I't should be easier to manage everything
> in one recipe, instead of specific image and image extensions.
> 
> I'm just not sure we can avoid using keys - I didn't manage to
> execute commands (by running `ssh <options> <cmd>` ) in
> non-interactive way with only user passwords.

Quick google pointed me to "sshpass -p ci ssh <options> <cmd>". The
tool would have to be installed with apt-get like we do with
qemu-system. In fact ssh will also have to be installed.

If that does not work, we use the key.

Henning

> > > That way we know which package owned that file and if we have a
> > > prerm we can even remove everything with apt.
> > > 
> > > Henning
> > >   
> > > > Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> > > > ---
> > > > 
> > > >  meta/classes/image-account-extension.bbclass | 14
> > > > +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
> > > > 
> > > > diff --git a/meta/classes/image-account-extension.bbclass
> > > > b/meta/classes/image-account-extension.bbclass index
> > > > 70950a7b..c9b86250 100644 ---
> > > > a/meta/classes/image-account-extension.bbclass +++
> > > > b/meta/classes/image-account-extension.bbclass @@ -17,7 +17,7 @@
> > > > USERS ??= "" #USER_root[home] = "/home/root"
> > > > 
> > > >  #USER_root[shell] = "/bin/sh"
> > > >  #USER_root[groups] = "audio video"
> > > > 
> > > > -#USER_root[flags] = "no-create-home create-home system
> > > > allow-empty-password clear-text-password force-passwd-change"
> > > > +#USER_root[flags] = "no-create-home create-home system
> > > > allow-empty-password clear-text-password force-passwd-change
> > > > copy-ci-key" GROUPS ??= ""
> > > > @@ -263,5 +263,17 @@ image_postprocess_accounts() {
> > > > 
> > > >              sudo -E chroot '${ROOTFSDIR}' \
> > > >              
> > > >                  /usr/bin/passwd --expire "$name"
> > > >          
> > > >          fi
> > > > 
> > > > +
> > > > +        # Add CI ssh key for noninteractive login
> > > > +        if [ "${flags}" != "${flags%*,copy-ci-key,*}" ]; then
> > > > +            echo "Add CI ssh key for \"$name\""
> > > > +            sudo sh -c " \
> > > > +                mkdir -p ${ROOTFSDIR}/${home}/.ssh && \
> > > > +                cat ${TESTSUITEDIR}/keys/ssh/id_rsa.pub >
> > > > ${ROOTFSDIR}/${home}/.ssh/authorized_keys && \
> > > > +                chmod -R go-rwx ${ROOTFSDIR}/${home}/.ssh
> > > > +            "
> > > > +            sudo -E chroot '${ROOTFSDIR}' \
> > > > +                chown -R ${name}:${gid} ${home}/.ssh
> > > > +        fi
> > > > 
> > > >      done
> > > >  
> > > >  }  
> 
> 
> 
> 


  reply	other threads:[~2023-01-25  8:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  7:19 [PATCH 00/11] Support running custom commands in VM Uladzimir Bely
2023-01-13  7:19 ` [PATCH 01/11] testsuite: Fix failing hostname service in qemu guest Uladzimir Bely
2023-01-13  7:19 ` [PATCH 02/11] testsuite: Allow custom image names in start_vm.py Uladzimir Bely
2023-01-24  6:59   ` Henning Schild
2023-01-13  7:19 ` [PATCH 03/11] testsuite: Fix terminal broken after run test executed Uladzimir Bely
2023-01-13  7:19 ` [PATCH 04/11] testsuite: Add SSH key pair for using in CI Uladzimir Bely
2023-01-13  7:19 ` [PATCH 05/11] image-account-extension: Add copy-ci-key flag for user Uladzimir Bely
2023-01-24  7:09   ` Henning Schild
2023-01-24  7:18     ` Henning Schild
2023-01-25  7:36       ` Uladzimir Bely
2023-01-25  8:45         ` Henning Schild [this message]
2023-01-13  7:19 ` [PATCH 06/11] meta-isar: Fix PCI bus initialization in qemuarm machine Uladzimir Bely
2023-02-08 13:03   ` Uladzimir Bely
2023-01-13  7:19 ` [PATCH 07/11] testsuite: Use random free port for qemu SSH forwarding Uladzimir Bely
2023-01-24  7:11   ` Henning Schild
2023-02-08 13:04   ` Uladzimir Bely
2023-01-13  7:19 ` [PATCH 08/11] testsuite: Support running custom commands in VM Uladzimir Bely
2023-01-24  7:14   ` Henning Schild
2023-01-24  7:14     ` Henning Schild
2023-01-13  7:19 ` [PATCH 09/11] meta-isar: Use a separate image recipe in CI Uladzimir Bely
2023-01-13  7:19 ` [PATCH 10/11] isar-image-ci: Make ethernet inerface auto bring up in ubuntu-focal Uladzimir Bely
2023-01-24  7:24   ` Henning Schild
2023-01-24  7:27     ` Henning Schild
2023-01-13  7:19 ` [PATCH 11/11] testsuite: Run custom commands on some qemu targets Uladzimir Bely
2023-01-24  7:39   ` Henning Schild

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=20230125094543.296194ac@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox