From: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>
To: "Bilgin, Enes" <enes.bilgin@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Dag, Ahmet Oguzhan" <oguzhan.dag@siemens.com>
Subject: Re: Apt Auth Mechanism for ISAR
Date: Wed, 27 Sep 2023 11:19:29 +0000 [thread overview]
Message-ID: <8ca7622f-ad06-641c-bed2-8ab609dcab0c@siemens.com> (raw)
In-Reply-To: <GV2PR10MB6041B51CD024A71E4E8316AAEBF8A@GV2PR10MB6041.EURPRD10.PROD.OUTLOOK.COM>
Hello
On 21/09/2023 11:56, Bilgin, Enes (ADV D EU TR MI&C MI 1) wrote:
>
> Hi Everyone,
>
> Can you add an authentication mechanism for PRODUCT_EXTRA_SOURCES?
>
This variable does not exist here (but I know what you are referring to)
>
> A mechanism that can use
> https://manpages.debian.org/testing/apt/apt_auth.conf.5.en.html is missing
>
your requirement/suggestion could be implemented with Isar moving away
from debootstrap to use mmdebstrap (I believe patches were posted to the
mailing list but not yet merged)
netrc files could indeed be provided to mmdebstrap via --aptopt
'Dir::Etc::netrcparts "/home/john/foo.d"' and files from that directory
copied over to the bootstrap rootfs (and consequently inherited in
sbuild and rootfs directories. I assume you would want netrc files
removed while the image is finalized to avoid leaking auth tokens to the
outside
> A related issue opened in here Add Support for apt_auth.conf for
> PRODUCT_EXTRA_SOURCES · Issue #97 · ilbers/isar · GitHub
> <https://github.com/ilbers/isar/issues/97>
>
> Best Regards
>
prev parent reply other threads:[~2023-09-27 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 9:56 Bilgin, Enes
2023-09-27 11:19 ` cedric.hombourger [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=8ca7622f-ad06-641c-bed2-8ab609dcab0c@siemens.com \
--to=cedric.hombourger@siemens.com \
--cc=enes.bilgin@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=oguzhan.dag@siemens.com \
/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