public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Ulrich Teichert <ulrich.teichert@kumkeo.de>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: AW: Re: HTTPs connection during bootstrap
Date: Tue, 28 Apr 2026 08:44:54 +0000	[thread overview]
Message-ID: <46f2271795ae485db5d2a840699875c6@kumkeo.de> (raw)
In-Reply-To: <2b9c7c31-2ff0-41c3-8e66-8f9a86199252@siemens.com>


Hi Jan,

[del]
>> What would be the best way to inject the missing certificates into the
>> bootstrapping
>> process?

>Bootstrapping is done within the environment of your host or kas-isar in
>case you use the build container. So, one way is to enrich the
>appropriate environment with that special certificate prior to starting
>the build.

Right, simple and works perfectly. Good to know that the host environment
is simply passed through.

>Another one is to explore the extension of do_apt_config_prepare of the
>bootstrap class with setting for
>https://manpages.debian.org/trixie/apt/apt-transport-https.1.en.html.

OK, for the moment I'm fine with modifying the host environment, but
I may come back to that later if we have to deal with more than our
own repository.

>There is no convenient way of configuring this via Isar variables
>because that case is too uncommon. Normally, one signs the repo itself,
>and can thus disable/ignore transport security.

I can't rule out that we will have to deal with repositories ouside of our
organisation in the future, so using one security layer more may become
necessary, but agreed: currently this is just overkill (but our IT department loves it...),

thanks,
Uli

Mit freundlichen Grüßen / Best regards


Dipl.-Inform. Ulrich Teichert
Senior Software Engineer



Phone +49 431 375938-0
_____________________________________

e.bs kumkeo GmbH
Am Kiel-Kanal 1
24106 Kiel, Deutschland

kumkeo.de

Rechnungen bitte an e.bs kumkeo GmbH, Heidenkampsweg 82a, 20097 Hamburg

Geschäftsführer Michael Leitner, Günter Hagspiel
Registergericht Amtsgericht Hamburg
Registernummer HRB 187712
USt-Idnr. DE449906070


-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/46f2271795ae485db5d2a840699875c6%40kumkeo.de.

      reply	other threads:[~2026-04-28  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  6:58 Ulrich Teichert
2026-04-28  7:40 ` 'Jan Kiszka' via isar-users
2026-04-28  8:44   ` Ulrich Teichert [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=46f2271795ae485db5d2a840699875c6@kumkeo.de \
    --to=ulrich.teichert@kumkeo.de \
    --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