SSH RSA Key Project (Linux server)
Budget: $30 – $250 USD
*** ONLY BID if you have experience in SSH/RSA keys and CA certs ***
Specifically, we need someone to provide a list of bash commands to accomplish the following. All you need to do is provide working bash/command line commands. We will integrate the commands into our system.
Goal of Project: We need to provide users the ability to connect to our Linux server via git using SSH (we know how to configure git, and users will have 'git-shell' as their shell, they do not need bash exec abilities).
We do NOT want to save every user (thousands of them) in ~/.ssh/authorized_keys, as this will be unmanageable under our customer count.
Instead, we will use a private CA to generate a signed PEM file and provide them to our users. These users will then use this PEM file to ssh/git onto our server. In theory, this allows us to only have the CA public key on our server, and any user authenticating in with a signed PEM should be allowed in.
We worked out some of the logic but had issues.
1) Generate an RSA private/public key 4096
- Currently, we use: ssh-keygen -f [USER-KEY-FILE] -b 4096 -t rsa
2) Take the keys and sign them with our CA cert
- ssh-keygen -s git_provider_ca -I [USER-EMAIL] -n git -V +365d [USER-KEY-FILE]
The problem with the above two lines is it signs the public key, but I need the private key signed (I think?). Then we need the private key in PEM format.
(https://engineering.fb.com/2016/09/12/security/scalable-and-secure-access-with-ssh/)
Specifically, we need someone to provide a list of bash commands to accomplish the following. All you need to do is provide working bash/command line commands. We will integrate the commands into our system.
Goal of Project: We need to provide users the ability to connect to our Linux server via git using SSH (we know how to configure git, and users will have 'git-shell' as their shell, they do not need bash exec abilities).
We do NOT want to save every user (thousands of them) in ~/.ssh/authorized_keys, as this will be unmanageable under our customer count.
Instead, we will use a private CA to generate a signed PEM file and provide them to our users. These users will then use this PEM file to ssh/git onto our server. In theory, this allows us to only have the CA public key on our server, and any user authenticating in with a signed PEM should be allowed in.
We worked out some of the logic but had issues.
1) Generate an RSA private/public key 4096
- Currently, we use: ssh-keygen -f [USER-KEY-FILE] -b 4096 -t rsa
2) Take the keys and sign them with our CA cert
- ssh-keygen -s git_provider_ca -I [USER-EMAIL] -n git -V +365d [USER-KEY-FILE]
The problem with the above two lines is it signs the public key, but I need the private key signed (I think?). Then we need the private key in PEM format.
(https://engineering.fb.com/2016/09/12/security/scalable-and-secure-access-with-ssh/)