From: Mauritz Stenek <mstenek@disroot.org>
To: Wojtek Kosior <koszko@koszko.org>
Cc: help-guix@gnu.org
Subject: Re: SSH error guix pull
Date: Thu, 07 Dec 2023 15:02:05 -0600 [thread overview]
Message-ID: <87v8993epb.fsf@disroot.org> (raw)
In-Reply-To: <20231207215715.5a35e906.koszko@koszko.org>
On 2023-12-07 at 14:57, Wojtek Kosior <koszko@koszko.org> wrote:
> [[PGP Signed Part:Undecided]]
>> > Nevertheless, I guess a
>> > hypothetical solution would be to allow Guix to — when
>> > desired —
>> > call
>> > SSH with access to its TTY/PTY :)
>>
>> Would you mind showing me how?
>
> Oh, that'd be hard… I meant modification to some internal code
> that
> spawns an SSH process. So that when certain CLI option is
> passed, Guix
> does this without substituting stdin/stdout/stderr file
> descriptors.
>
> Actually, I'm not even 100% sure the substitution is controlled
> directly by Guix — it might be in libgit which IIRC is used for
> cloning
> here.
I think you might be on to something -- scouring the internet,
libgit2 seems to be the culprit.
>
> Anyway, this improvement would require digging deep into either
> Guix or
> libgit. That's why I called it hypothetical — because it is too
> much
> work to consider here :)
>
> Anyway, if you're inclined to work around the problem, you might
> want
> to experiment with the SSH_ASKPASS and SSH_ASKPASS_REQUIRE
> environment
> variables. So that you're asked to enter the password in a GUI.
> See `man ssh` for more info about these vars
>
> Happy Hacking!
> Wojtek
Thanks for your all your help. What I have now works, which, is
sufficient for now (I hope).
A couple of things more I want to check, and that's it: I'm
migrating to a full Guix system.
>
>
> -- (sig_start)
> website: https://koszko.org/koszko.html
> fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
> follow me on Fediverse:
> https://friendica.me/profile/koszko/profile
>
> ♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷
> c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
> ✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ?
> U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
> -- (sig_end)
>
>
> On Thu, 07 Dec 2023 14:33:18 -0600 Mauritz Stenek
> <mstenek@disroot.org> wrote:
>
>> Nevertheless, I guess
>> > a
>> > hypothetical solution would be to allow Guix to — when
>> > desired —
>> > call
>> > SSH with access to its TTY/PTY :)
>>
>> Would you mind showing me how?
>
> [[End of PGP Signed Part]]
--
Mauritz Stenek <mstenek@disroot.org>
prev parent reply other threads:[~2023-12-07 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 1:47 SSH error guix pull Mauritz Stenek
2023-12-01 13:12 ` Wojtek Kosior via
2023-12-01 18:37 ` Mauritz Stenek
2023-12-01 20:07 ` Wojtek Kosior via
2023-12-05 17:44 ` Mauritz Stenek
2023-12-05 19:28 ` Wojtek Kosior via
2023-12-07 20:33 ` Mauritz Stenek
2023-12-07 20:57 ` Wojtek Kosior via
2023-12-07 21:02 ` Mauritz Stenek [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8993epb.fsf@disroot.org \
--to=mstenek@disroot.org \
--cc=help-guix@gnu.org \
--cc=koszko@koszko.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.