From: Wojtek Kosior via <help-guix@gnu.org>
To: Mauritz Stenek <mstenek@disroot.org>, help-guix@gnu.org
Subject: Re: SSH error guix pull
Date: Thu, 7 Dec 2023 21:57:15 +0100 [thread overview]
Message-ID: <20231207215715.5a35e906.koszko@koszko.org> (raw)
In-Reply-To: <87zfyl3g55.fsf@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
> > 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.
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
-- (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?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-07 20:57 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 [this message]
2023-12-07 21:02 ` Mauritz Stenek
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=20231207215715.5a35e906.koszko@koszko.org \
--to=help-guix@gnu.org \
--cc=koszko@koszko.org \
--cc=mstenek@disroot.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).