From: Vamsi Vytla <vamsi.vytla@gmail.com>
To: help-guix@gnu.org
Subject: Cuirass service SSH_AUTH_SOCK
Date: Fri, 1 Oct 2021 15:44:02 -0700 [thread overview]
Message-ID: <CAMruYDSGc0eL9_jGsFYEX8gGy-kKYdRwiXoD1_sa8546LPU6og@mail.gmail.com> (raw)
Hi,
I couldn't find a way to get the guix-cuirass service to successfully
git-checkout from an authenticated git repository. I see this in the log:
2021-10-01T15:26:43 Fetching channels for spec '<reponame>'.
2021-10-01T15:26:43 Git error while fetching inputs of '<reponame>': "error
authenticating: no auth sock variable"
Looks like SSH_AUTH_SOCK is not an environment variable that is defined in
services/cuirass.scm. Would it be possible to make it such a way that the
user can pass an ssh-agent socket as a variable (assuming the keys are
password less), via a service-extension?
I am by no means a security expert, and was wondering if there was any
sense in starting an ssh-agent and adding system keys to it and using that
as a starting point? This could mean that the system keys could be added as
deploy keys to any private git repo?
Cheers!
reply other threads:[~2021-10-01 23:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMruYDSGc0eL9_jGsFYEX8gGy-kKYdRwiXoD1_sa8546LPU6og@mail.gmail.com \
--to=vamsi.vytla@gmail.com \
--cc=help-guix@gnu.org \
/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).