Ssh – hpn-ssh on Debian 8 (Jessie)

debian-jessiessh

I'm refering this this project: https://www.psc.edu/index.php/hpn-ssh

I'm running Debian 8, with OpenSSH_6.7p1 Debian-5+deb8u1, OpenSSL 1.0.1k 8 Jan 2015 and hpn-ssh doesn't have a patch for this version, does that mean I have to somehow downgrade openSSH and then compile an older version of openSSH?

Doesn't seem like the most secure option.

If so how would I go about doing this. (or is there a better way to copy large files quickly)

Best Answer

Rather than downgrading, you could consider updating to the openSSH packages available in stretch (7.1), as I can see that HPN-SSH has patches available for that version at http://sourceforge.net/projects/hpnssh/files/?source=navbar (I wonder why 6.7 is skipped?) In theory this is a bit risky as you're not using the declared stable packages, but in practice testing is pretty damn stable itself - debian's quite conservative about what goes into the repositories and what's considered stable.

In short - add the stretch repositories to your apt sources, set pinning information in apt preferences so apt will still prefer packages from stable, and then manually get the packages from testing by referring to them as openssh/testing in your apt commands.

Related Solutions

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

SSH – Bad Owner or Permissions on ~/.ssh/config

I needed to have rw for user only permissions on config. This fixed it.

chmod 600 ~/.ssh/config

As others have noted below, it could be the file owner. (upvote them!)

chown $USER ~/.ssh/config

If your whole folder has invalid permissions here's a table of possible permissions:

Path	Permission
.ssh directory (code)	0700 (drwx------)
private keys (ex: `id_rsa`) (code)	0600 (-rw-------)
`config`	0600 (-rw-------)
public keys (*.pub ex: `id_rsa.pub`)	0644 (-rw-r--r--)
`authorized_keys` (code)	0644 (-rw-r--r--)
`known_hosts`	0644 (-rw-r--r--)

Sources:

openssh check-perm.c
openssh readconf.c
openssh ssh_user_config fix_authorized_keys_perms

Best Answer

Related Solutions

Ssh – How to automate SSH login with password

SSH – Bad Owner or Permissions on ~/.ssh/config

Related Topic