• jonjuan@programming.dev
      link
      fedilink
      English
      arrow-up
      36
      arrow-down
      1
      ·
      1 day ago

      encrypt them with a password if you wish.

      SSH keys without passphrases are just fancy credential files sitting in your .ssh/ directory, basically like writing your passwords on paper and leaving it in your desk drawer.

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 hour ago

        but they require chmod 400 and they’re ideally in on an encrypted disk

        So the desk drawer is locked and the codes are Luks encrypted.

        And for critical stuff, you should also have a password on the key.

        If your ssh keys are like a passwords on paper in a drawer, you’re doing it wrong.

        • LedgeDrop@lemmy.zip
          link
          fedilink
          arrow-up
          32
          ·
          1 day ago

          Take a look at ssh-agent. It’s bundled with ssh-client and designed to solve this problem.

          The quick usage is, create a terminal and run:

          eval `ssh-agent`
          ssh-add /path/to/your/encrypted/key1
          #type in password
          ssh-add /path/to/your/encrypted/key2
          ... 
          
          # all commands in this terminal will use the keys above w/o asking you for a password 
          git clone [email protected]...
          git push... 
          etc
          

          So, basically you type your credentials once during the life cycle of your terminal.

          If you really want to go full power-user, simple run ssh-agent (without the eval) and you’ll see it just sets some env-vars, which can be imported into any terminal/shell you have open.

          So, if you put some logic in your shells rc file, you can effectively share a single ash-agent between all your shells, meaning you just need to type your password for your keys once when you log into your system… and your now passwordless for any future terminals you create (this is my setup).

          Also, if you’re interested take a peek at the man pages for ash-agent. It has a few interesting features (ie: adding a password lock for your agent, removing keys from the agent, etc).

          • bandwidthcrisis@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            2 hours ago

            I have

            if [ -z "$SSH_AUTH_SOCK" ] ; then
                eval $(ssh-agent -s)
            fi
            

            At the end of .bashrc and

            AddKeysToAgent yes
            

            In .ssh/config so that it auto-adds keys I unlock.

      • ThunderQueen@lemmy.world
        link
        fedilink
        arrow-up
        7
        arrow-down
        1
        ·
        1 day ago

        I had mine on paper for years before i learned about Keepass. I trusted it more than a cloud based manager because someone would have to physically be in my room.

        I am a lot more careful these days but that is not beyond the pale for a lot of folks haha