From: Nico Lastzka <Nico.Lastzka@ATSonline.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Hard-coded directory permissions
Date: Wed, 10 Jun 2020 13:42:25 +0200 [thread overview]
Message-ID: <20200610114225.GH4898@develop-10-146> (raw)
In-Reply-To: <AM0PR04MB69779583FFFA07CD16048539DC830@AM0PR04MB6977.eurprd04.prod.outlook.com>
On Wed 10/06/20 11:32, Bruno Thomsen wrote:
>> From: ptxdist <ptxdist-bounces@pengutronix.de> on behalf of Nico Lastzka <Nico.Lastzka@ATSonline.de>
>> Sent: Wednesday, June 10, 2020 11:35
>> To: ptxdist@pengutronix.de <ptxdist@pengutronix.de>
>> Subject: [ptxdist] Hard-coded directory permissions
>>
>> Hi,
>>
>> I ran into a problem with the latest ptxdist 2020.06 when trying to install an ssh key to
>> "/root/.ssh/authorized_keys".
>>
>>
>> Here, the "image-enhancements rule" contains the following code which breaks the image creation:
>>
>> @$(call install_copy, image_enhancements, 0, 0, 0400, $(PTXDIST_PLATFORMCONFIGDIR)/access/key-develop_id_ed25519.pub, /root/.ssh/authorized_keys )
>
>I think you need to create the parent directory first with correct permissions.
>
>@$(call install_copy, image_enhancements, 0, 0, 0400, /root/.ssh)
>
Already tried that without success.
>/Bruno
>_______________________________________________
>ptxdist mailing list
>ptxdist@pengutronix.de
>To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
>
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-06-10 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 9:35 Nico Lastzka
2020-06-10 11:32 ` Bruno Thomsen
2020-06-10 11:42 ` Nico Lastzka [this message]
2020-06-11 5:46 ` Michael Olbrich
2020-06-11 6:19 ` Nico Lastzka
2020-06-12 6:51 ` Michael Olbrich
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=20200610114225.GH4898@develop-10-146 \
--to=nico.lastzka@atsonline.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