Git Extensions Putty Key Generator

  • Sponsor New issue

    Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

    By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

    Already on GitHub? Sign in to your account

    Git Extensions Putty Key Generator


    commented Aug 6, 2015

    Git Extensions Putty Key Generator For Windows

    Would like to have the 'Load SSH Key' button for the OpenSSH mode, not only for plink mode.
    I believe the process of setting up the SSH keys could be made much more friendly with that.

    Why not plink: once you set up OpenSSH, you get a stable auth experience across all the possible git tools besides GitExtensions, like command line, bash, IntelliJ IDEA, SourceTree, etc. As far as I understand, won't work this way with plink.

    How it might work.
    The button opens a dialog, which has three sections.

    1. Don't have a key? Generate new. Opens puttygen.exe, tells that you should do 'Conversions OpenSSH key' in it to save in suitable format. (without this, you'd have to close Clone to run it from Tools)
    2. Set key for all servers. Browses for the key file, writes it into %USERPROFILE%.sshid_rsa.
    3. Set key for this server (server name from 'Repository to clone:' here). Browses for the file, adds a record to the %USERPROFILE%.sshconfig file for this server, pointing to the browsed file.
    4. Has some hints on how to assign this key to your git server.

    If labels text is decent enough, then this would not only a GUI configuration path entirely within GitExtensions, but also intuitive enough to be done without any additional instructions.

    commented Aug 6, 2015

    puttygen's much of a black box, so file browsing is inevitable with it. Also choosing for export formats. Maybe should try scripting msysgit's ssh-keygen instead?..

    added the type: feature request label Apr 29, 2016
    Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment