mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Mircea Ciocan <m.ciocan@ppc-ag.de>
Subject: Re: [ptxdist] Installing a file in the /root directory.
Date: Wed, 24 Jun 2020 12:01:05 +0200	[thread overview]
Message-ID: <20200624100105.GE23174@pengutronix.de> (raw)
In-Reply-To: <10680640-fd44-5c11-1ce4-7879f56c2409@ppc-ag.de>

On Tue, Jun 23, 2020 at 05:16:45PM +0200, Mircea Ciocan wrote:
> On 23.06.20 15:59, Alexander Dahl wrote:
> > Hei hei,
> > 
> > On Tue, Jun 23, 2020 at 02:20:30PM +0200, Mircea Ciocan wrote:
> > > I want to install /root/.ssh/authorized_keys file from my board projectroot
> > > directory.
> > > 
> > > Sadly even after reading the previous mail regarding a similar issue with
> > > systemd directory I'm not able to correctly install the file.
> > > 
> > > I can create the /root/.ssh empty directory with the correct 0700
> > > permissions, but I haven't found any way of putting a file there, everything
> > > fails with:
> > > 
> > > Incompatible ownership or permissions for '/root':
> > > dropbear: 0.0 0755 (implicit)
> > > rootfs: 0.0 0700
> > > 
> > > One of these packages must be fixed!
> > > 
> > > Could a kind soul give me a quick hint how to do this, in my projectroot,
> > > the directories and file are having proper permissions.
> > > 
> > > 
> > > Line that fails:
> > > 
> > >          @$(call install_alternative, dropbear, 0, 0, 0600,
> > > /root/.ssh/authorized_keys, n)
> > This is not part of ptxdist master branch 'rules/dropbear.make' and
> > from a quick glance in Git it was not for the last 10 years.  Do you
> > have a customized rule in your BSP?
> > 
> > Greets
> > Alex
> > 
> That's the only "customization" made, I want to install an access key, the
> rest of the rule is vanilla dropbear.make

1. Don't overwrite the dropbear package for this. Just create a new package
   with the 'files' template to install your file.

2. You need to explicitly create /root in your package (or dropbear if you
   want to stick with that) with the same permissions as the rootfs
   package. And you should probably create /root/.ssh with the correct
   permissions as well:

	@$(call install_copy, dropbear, 0, 0, 0700, /root)
	@$(call install_copy, dropbear, 0, 0, 0700, /root/.ssh)
	@$(call install_alternative, dropbear, 0, 0, 0600, \
		/root/.ssh/authorized_keys, n)

Note, there is a bug in the latest ptxdist release. I think this will still
fail, so you need to copy scripts/lib/ptxd_lib_check_dir_permissions.awk
from ptxdist master into your BSP.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

      reply	other threads:[~2020-06-24 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 12:20 Mircea Ciocan
2020-06-23 13:59 ` Alexander Dahl
2020-06-23 15:16   ` Mircea Ciocan
2020-06-24 10:01     ` Michael Olbrich [this message]

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=20200624100105.GE23174@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=m.ciocan@ppc-ag.de \
    --cc=ptxdist@pengutronix.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