Visitar URL original
Prompt for SSH/HTTPS passphrase in minibuffer · Issue #334 · radian-software/straight.el · GitHub
Skip to content

Prompt for SSH/HTTPS passphrase in minibuffer #334

Closed

Description

@qleguennec
(use-package private-repo
  :straight (:host github :repo "qleguennec/private-repo"))

Results in:

$ cd /home/void/.emacs.d/straight/repos/
$ git clone --origin origin --no-checkout https\://github.com/qleguennec/private-repo.git private-repo

Cloning into 'private-repo'...
fatal: could not read Username for 'https://github.com': No such device or address

[Return code: 128]

Not sure if that's a bug or something that could be implemented.
Either way, that would be pretty useful to have.

Activity

  1. raxod502 commented on Dec 16, 2018

    @raxod502
    Member

    If you

    (setq straight-vc-git-default-protocol 'ssh)

    then you can take advantage of ssh-agent authentication. With HTTPS, you can use git-credential-cache.

    Unfortunately, if the cache has timed out, you still get an error like this. I agree that it's not desirable behavior. Probably the right way to handle this is to do as Magit does and just connect stdin for all Git commands to the terminal. That way the user can provide a passphrase when one is needed.

  2. added this to the 1.0 milestone on Dec 16, 2018
  3. changed the title [-]Support fetching a package from a private github repository[/-] [+]Prompt for SSH/HTTPS passphrase in minibuffer[/+] on Jun 5, 2019
  4. added a commit that references this issue on Sep 13, 2019
  5. raxod502 commented on Sep 13, 2019

    @raxod502
    Member

    Better late than never, right? ✨

  6. added a commit that references this issue on Sep 13, 2019
  7. raxod502 commented on Sep 13, 2019

    @raxod502
    Member

    Unfortunately, I just noticed that this causes a regression in process execution sequencing. More work is required.

  8. added a commit that references this issue on Sep 13, 2019
  9. raxod502 commented on Sep 13, 2019

    @raxod502
    Member

    ✨ ✨ ✨

  10. added a commit that references this issue on Sep 16, 2019
  11. raxod502 commented on Sep 16, 2019

    @raxod502
    Member

    Another regression, this one even more incomprehensible. This makes me extremely sad.

  12. bestlem commented on Jun 18, 2022

    @bestlem

    If you

    (setq straight-vc-git-default-protocol 'ssh)

    then you can take advantage of ssh-agent authentication. With HTTPS, you can use git-credential-cache.

    Unfortunately, if the cache has timed out, you still get an error like this. I agree that it's not desirable behavior. Probably the right way to handle this is to do as Magit does and just connect stdin for all Git commands to the terminal. That way the user can provide a passphrase when one is needed.

    When you do this chnage to straight-vc-git-default-protocol not you have to also change the [remote] entries in the .git/config from https to ssh for those repos you already have.

  13. raxod502 commented on Jun 20, 2022

    @raxod502
    Member

    You can also accomplish this by running M-x straight-normalize-all with straight-vc-git-force-protocol non-nil.

  14. raxod502 commented on Jun 13, 2025

    @raxod502
    Member

    Implemented, finally, in #1207.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions