unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ashvith Shetty <ashvithshetty10@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Demystifying SSH configuration for remote software forges on Guix System
Date: Thu, 16 May 2024 18:29:22 +0000	[thread overview]
Message-ID: <CA+n6Bx-zYR0eD7YL9pVOswV4qbxRMomMM+bsfgPE7kUmEG_8bw@mail.gmail.com> (raw)
In-Reply-To: <87a5ks4sui.fsf@gnu.org>

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

Hello Ludovic,
Thank you for your reply. I was able to resolve this by adding `openssh` to
the system configuration, and `home-openssh` as well as `home-ssh-agent` to
the home configuration respectively.

On Tue, May 14, 2024 at 9:59 AM Ludovic Courtès <ludo@gnu.org> wrote:

> Hi,
>
> Ashvith Shetty <ashvithshetty10@gmail.com> skribis:
>
> > 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?
>
> Never ever put private keys in a repo.
>
> I use ‘home-gpg-agent-service-type’ as my SSH agent:
>
>   https://guix.gnu.org/manual/devel/en/html_node/GNU-Privacy-Guard.html
>
> If you already use Guix Home, you can set it up by adding a few lines to
> your Home config, along the lines of the example in the manual above.
>
> If you don’t, you could start ‘gpg-agent --ssh-support’ or ‘ssh-agent’
> manually, for example from ~/.xsession or similar startup file.
>
> HTH!
>
> Ludo’.
>

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

      reply	other threads:[~2024-05-16 18:31 UTC|newest]

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

  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+n6Bx-zYR0eD7YL9pVOswV4qbxRMomMM+bsfgPE7kUmEG_8bw@mail.gmail.com \
    --to=ashvithshetty10@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).