Troubleshooting GitHub Enterprise

I don't know why, but I'm always unlucky with Linux...

Two years ago I decided to stop using linux (Ubuntu) when a supposedly safe upgrade broke my graphical interface just before a demo. Since both, my patience and time, are very limited, I decided to switch to Mac and I've been a happy user.

But today, I had to setup an Ubuntu box for testing. For the first time I really liked what I saw. The graphical interface and new HUD were clean and useful...

I installed OpenSSH, the client and the server, I generated the ssh keys and got my personal GitHub account working fine...

$ ssh-keygen -t rsa
...
$ ssh -T git@github.com
Hi bitparagon! You've successfully authenticated, 
but GitHub does not provide shell access.

And everything was going okay... until I had to setup the GitHub Enterprise in our corporate environment... a then

$ ssh -T git@git.corp.bitparagon.com
...
Connection closed by 10.10.203.53
fatal: The remote end hung up unexpectedly

Then inspecting in detail

$ ssh -Tv git@git.corp.bitparagon.com
...
...
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
Credentials cache file '/tmp/krb5cc_1000' not found
debug1: Unspecified GSS failure.  Minor code may provide more information
Credentials cache file '/tmp/krb5cc_1000' not found
debug1: Unspecified GSS failure.  Minor code may provide more information
debug1: Next authentication method: publickey
debug1: Offering public key: /home/bitparagon/.ssh/id_rsa
# authentication by public key then proceeded quickly
...

After googling, regenerating the ssh key several times and cleaning the ~/.ssh/ directory, finally the solution was to generate the ssh key using dsa instead or rsa. So odd... so weird...

$ ssh-keygen -t dsa

This is one of the things I will keep complaining about Linux, in a Mac you never have to dig so deep to solve something that shouldn't be an issue... anyway I'll give my Ubuntu box one more chance...

---