public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Jonas Reindl <jonas.reindl@kilobaser.com>
Cc: isar-users@googlegroups.com
Subject: Re: APT Repo with authentication
Date: Wed, 6 Apr 2022 14:03:01 +0200	[thread overview]
Message-ID: <20220406140301.7a576213@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <eadcd47f-98b9-4128-51e3-291429f86502@kilobaser.com>

Hi Jonas,

that is indeed something i never came across. It should not be too hard
but might indeed require some changes to Isar.

In case it is simple plain http auth you can put the credentials into
your sources.list URI. "deb http://<user>:<passwd>@super.secret/crap"

That should work for DISTRO_APT_SOURCES_append files without a problem.
I kind of doubt you could easily bootstrap from such a repo, but if it
is just "additional packages" it should be fine.

If you want to store credentials in a separate file in
/etc/apt/auth.conf.d/*.conf, you will have to patch Isar to support
that.

And of cause you can always have a proxy somewhere in the middle, which
abstracts the auth away. And DISTRO_APT_PREMIRRORS could be used to
toggle that.

regards,
Henning

Am Wed, 6 Apr 2022 13:11:48 +0200
schrieb Jonas Reindl <jonas.reindl@kilobaser.com>:

> Hi everyone,
> 
> I now have the usecase that I have a apt repo, which uses
> authentication.
> 
> I couldn't find anything, that would make this possible. Are there
> any examples or do I need to add that functionality to 
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> 
> Best regards,
> 
> Jonas
> 


  parent reply	other threads:[~2022-04-06 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 11:11 Jonas Reindl
2022-04-06 11:43 ` Baurzhan Ismagulov
2022-04-06 11:52   ` Jonas Reindl
2022-04-06 12:03 ` Henning Schild [this message]
2022-04-07 11:16   ` Raphael Lisicki

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=20220406140301.7a576213@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jonas.reindl@kilobaser.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