unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ashvith Shetty <ashvithshetty10@gmail.com>
To: guix-devel@gnu.org
Subject: Demystifying SSH configuration for remote software forges on Guix System
Date: Fri, 10 May 2024 07:57:33 +0000	[thread overview]
Message-ID: <CA+n6Bx8H7j11s_i1WGGVLLBY8wmLMVdL6CqcAheSzzYLW+G6iA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

I would like to understand the process for configuring SSH for software
forges, like Forgejo, GitLab or GitHub. So far, what I've noticed is that
by itself, SSH does not work properly, and that after opening a new
terminal session (window or tab, it does not matter), I am forced to repeat
the following step every time, before any pull or push:

```console
$ eval $(ssh-agent -s)
$ ssh-add <path-to-private-key>
```

Before I continue any further, I wanted to let you folks know that
presently, I am on XFCE4. I don't remember clearly if GNOME Desktop did
some magic behind the back, or if I had to repeat similar steps over there,
because I've not touched Git for some time.

I've tried adding GNOME Keyring as a service in the latest system
configuration (of course, with XFCE4), assuming that this missing service
was what I should have probably added, but that does not seem to be the
case. What am I missing over here?

And finally, I've come across `home-openssh-service-type` - which I've yet
to try, but reading from the docs, am I supposed to put my private and
public keys in the repository? How do I go about this? Isn't that a
security risk?

Thanks,
Ashvith

[-- Attachment #2: Type: text/html, Size: 1336 bytes --]

             reply	other threads:[~2024-05-10  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  7:57 Ashvith Shetty [this message]
2024-05-14  9:59 ` Demystifying SSH configuration for remote software forges on Guix System Ludovic Courtès
2024-05-16 18:29   ` Ashvith Shetty

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=CA+n6Bx8H7j11s_i1WGGVLLBY8wmLMVdL6CqcAheSzzYLW+G6iA@mail.gmail.com \
    --to=ashvithshetty10@gmail.com \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).