public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Boris Unckel <bu.cygwin@mail.unckel.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Cygwin quiet-mode setup against local Repository authentication issue
Date: Thu, 21 Jul 2022 16:41:21 +0200 (CEST)	[thread overview]
Message-ID: <918341508.1574163.1658414481397@email.ionos.de> (raw)

Dear Cygwin community,

we plan to have Cygwin distributed with our Softwarecenter package distribution. The process shall not require any user interaction. Due to security policies we don’t grant users direct access to the internet. The mandatory proxy blocks binary downloads. For this reason we have established a JFrog Artifactory remote repository for the whole Cygwin distribution. Accessing this repository by browser works without any issues, both with and without login.

Our command is like this (hostname with blanks obfuscated)

setup-x86_64.exe --only-site --site "https:// artifactory .local/ artifactory/cygwin/" --no-shortcuts --no-desktop --quiet-mode --root "C:\customfolder\cygwinx64\cygwin" --arch x86_64 --local-package-dir "C:\ customfolder \cygwinx64\cygwin-packages" --verbose --upgrade-also --categories Base --packages bash-completion,vim,vim-common,vim-doc

It might be due to an artifactory bug but anonymous access to the local repo is not working at the moment. When setup-x86_64.exe downloads the packages it receives a http code 401 and a popup to enter user/password shows up.

What can we do pass user / password for the –site destination without UI and without user interaction?


Kind regards
Boris

             reply	other threads:[~2022-07-21 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 14:41 Boris Unckel [this message]
2022-07-21 16:55 ` Achim Gratz
2022-07-22  4:48   ` Boris Unckel

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=918341508.1574163.1658414481397@email.ionos.de \
    --to=bu.cygwin@mail.unckel.net \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).