public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jonas Reindl <jonas.reindl@kilobaser.com>
To: isar-users@googlegroups.com
Subject: Re: APT Repo with authentication
Date: Wed, 6 Apr 2022 13:52:31 +0200	[thread overview]
Message-ID: <b8b71880-c66c-4878-d5bc-c28002c6c697@kilobaser.com> (raw)
In-Reply-To: <Yk180zJv0btKrjaD@ilbers.de>

On 4/6/22 13:43, Baurzhan Ismagulov wrote:

> On Wed, Apr 06, 2022 at 01:11:48PM +0200, Jonas Reindl wrote:
>> 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
> Does "apt repo which uses authentication" mean http / https auth? I haven't
> tried this, not even as an apt user. isar-bootstrap might be a good place to
> start depending on what needs to be done; I don't know whether it also ends
> there.

Yeah, I mean authentication with https. Like 
https://manpages.debian.org/testing/apt/apt_auth.conf.5.en.html

Just realized that also an inline http basic auth should probably work. 
Still need to test that.

Furthermore inline secrets are still a bit complicated to deal with in isar.

As far as I could remember at least ubuntu or so had problems with that.

>
> Please note that we are currently developing upfront Debian package fetching
> which touches the related areas:
>
> https://groups.google.com/g/isar-users/c/LGpLwhOfh-M/m/_xV8O-ncBQAJ
Thank you for all the information,
>
> With kind regards,
> Baurzhan.

Best regards,

Jonas


  reply	other threads:[~2022-04-06 11:52 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 [this message]
2022-04-06 12:03 ` Henning Schild
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=b8b71880-c66c-4878-d5bc-c28002c6c697@kilobaser.com \
    --to=jonas.reindl@kilobaser.com \
    --cc=isar-users@googlegroups.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