mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] doc: user_manual: mention download prevention during non-get stages
Date: Wed, 25 May 2022 11:45:43 +0200	[thread overview]
Message-ID: <20220525094543.2847917-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220520153210.7158-2-bst@pengutronix.de>

Thanks, applied as 6d4a7426324b7f9ed7603ab56ae2ca0eb02b7f80.

Michael

[sent from post-receive hook]

On Wed, 25 May 2022 11:45:43 +0200, Bastian Krause <bst@pengutronix.de> wrote:
> Signed-off-by: Bastian Krause <bst@pengutronix.de>
> Message-Id: <20220520153210.7158-2-bst@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/doc/user_manual.inc b/doc/user_manual.inc
> index 2adcd964cddc..6bd534f3d8a1 100644
> --- a/doc/user_manual.inc
> +++ b/doc/user_manual.inc
> @@ -125,6 +125,10 @@ download an archive currently not existing on the development host. But
>  there are ways to prevent PTXdist from doing so (refer to section
>  :ref:`source-arch-loc`).
>  
> +.. note:: PTXdist tries to prevent downloads outside of the *get* stage
> +  by setting certain widespread proxy environment variables to an
> +  inexistent host name.
> +
>  First steps with PTXdist
>  ------------------------
>  



  reply	other threads:[~2022-05-25  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 15:32 [ptxdist] [PATCH 1/2] ptxd_make_world_init: set invalid proxy value for download prevention to greppable value Bastian Krause
2022-05-20 15:32 ` [ptxdist] [PATCH 2/2] doc: user_manual: mention download prevention during non-get stages Bastian Krause
2022-05-25  9:45   ` Michael Olbrich [this message]
2022-05-25  9:45 ` [ptxdist] [APPLIED] ptxd_make_world_init: set invalid proxy value for download prevention to greppable value 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=20220525094543.2847917-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=bst@pengutronix.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