openssh-server in any software manager package ?

[Erwin Smout]

I'm trying to have openssh-server on my laptop (I know that sounds slightly odd, for the moment it just allows me to work a bit more comfy that's all).

Software manager doesn't seem to give useful results when searching for openssh-server (description of the package seems to say it's only about the client).

apt-get seems to work as far as installing goes, but when I try to connect from my other desktop it fails with "network error" (perhaps the sshd daemon doesn't start or so - how do I check that ?).

Anyone can give me any hints ?

[Feathers McGraw]

When I search openssh-server in Muon Discover I get "Secure Shell", which is not what you are looking for (it's a graphical alternative to connecting with the ssh command in a terminal), so perhaps you installed the wrong thing?

You can check if you've installed openssh-server using dpkg -s openssh-server

Example output:

sam@samhobbs:~$ dpkg -s openssh-server
Package: openssh-server
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 929
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Multi-Arch: foreign
Source: openssh
Version: 1:6.6p1-2ubuntu2
Replaces: ssh, ssh-krb5
Provides: ssh-server
Depends: libc6 (>= 2.17), libck-connector0 (>= 0.2.1), libcomerr2 (>= 1.01), libdbus-1-3 (>= 1.0.2), libgssapi-krb5-2 (>= 1.10+dfsg~), libkrb5-3 (>= 1.6.dfsg.2), libpam0g (>= 0.99.7.1), libselinux1 (>= 1.32), libssl1.0.0 (>= 1.0.1), libwrap0 (>= 7.6-4~), zlib1g (>= 1:1.1.4), debconf (>= 0.5) | debconf-2.0, init-system-helpers (>= 1.13~), openssh-client (= 1:6.6p1-2ubuntu2), sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), libpam-runtime (>= 0.76-14), libpam-modules (>= 0.72-9), adduser (>= 3.9), dpkg (>= 1.9.0), lsb-base (>= 4.1+Debian3), procps, openssh-sftp-server
Recommends: xauth, ncurses-term, ssh-import-id
Suggests: ssh-askpass, rssh, molly-guard, ufw, monkeysphere
Conflicts: sftp, ssh-socks, ssh2
Conffiles:
 /etc/network/if-up.d/openssh-server 91e764631983aab83a9e08bd9e00a9f9
 /etc/default/ssh 500e3cf069fe9a7b9936108eb9d9c035
 /etc/init/ssh.conf 9e5ed011987e63f8035fb847170dfa3f
 /etc/init.d/ssh aca247a51227a8f8b37a8c2a4a703571
 /etc/pam.d/sshd 91e82cb29c884f06d65db92e90a4e159
 /etc/ufw/applications.d/openssh-server 486b78d54b93cc9fdc950c1d52ff479e
Description: secure shell (SSH) server, for secure access from remote machines
 This is the portable version of OpenSSH, a free implementation of
 the Secure Shell protocol as specified by the IETF secsh working
 group.
 .
 Ssh (Secure Shell) is a program for logging into a remote machine
 and for executing commands on a remote machine.
 It provides secure encrypted communications between two untrusted
 hosts over an insecure network. X11 connections and arbitrary TCP/IP
 ports can also be forwarded over the secure channel.
 It can be used to provide applications with a secure communication
 channel.
 .
 This package provides the sshd server.
 .
 In some countries it may be illegal to use any encryption at all
 without a special permit.
 .
 sshd replaces the insecure rshd program, which is obsolete for most
 purposes.
Original-Maintainer: Debian OpenSSH Maintainers <debian-ssh@lists.debian.org>
Homepage: http://www.openssh.org/

And check if it's running with sudo service ssh status. Example output:

sam@samhobbs:~$ sudo service ssh status
[sudo] password for sam: 
ssh start/running, process 1201

Sam

[claydoh]

Muon Discover (and Ubuntu's Software Center) doesn't show all of the available software, mostly the command line, libraries, and other "invisible" things are not seen from there.
You need to use an "advanced" software management tool such as Muon Package Manager, Synaptic, or command line tools

[Erwin Smout]

When I search openssh-server in Muon Discover I get "Secure Shell", which is not what you are looking for (it's a graphical alternative to connecting with the ssh command in a terminal), so perhaps you installed the wrong thing?

You can check if you've installed openssh-server using dpkg -s openssh-server

Example output:

sam@samhobbs:~$ dpkg -s openssh-server
Package: openssh-server
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 929
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Multi-Arch: foreign
Source: openssh
Version: 1:6.6p1-2ubuntu2
Replaces: ssh, ssh-krb5
Provides: ssh-server
Depends: libc6 (>= 2.17), libck-connector0 (>= 0.2.1), libcomerr2 (>= 1.01), libdbus-1-3 (>= 1.0.2), libgssapi-krb5-2 (>= 1.10+dfsg~), libkrb5-3 (>= 1.6.dfsg.2), libpam0g (>= 0.99.7.1), libselinux1 (>= 1.32), libssl1.0.0 (>= 1.0.1), libwrap0 (>= 7.6-4~), zlib1g (>= 1:1.1.4), debconf (>= 0.5) | debconf-2.0, init-system-helpers (>= 1.13~), openssh-client (= 1:6.6p1-2ubuntu2), sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), libpam-runtime (>= 0.76-14), libpam-modules (>= 0.72-9), adduser (>= 3.9), dpkg (>= 1.9.0), lsb-base (>= 4.1+Debian3), procps, openssh-sftp-server
Recommends: xauth, ncurses-term, ssh-import-id
Suggests: ssh-askpass, rssh, molly-guard, ufw, monkeysphere
Conflicts: sftp, ssh-socks, ssh2
Conffiles:
 /etc/network/if-up.d/openssh-server 91e764631983aab83a9e08bd9e00a9f9
 /etc/default/ssh 500e3cf069fe9a7b9936108eb9d9c035
 /etc/init/ssh.conf 9e5ed011987e63f8035fb847170dfa3f
 /etc/init.d/ssh aca247a51227a8f8b37a8c2a4a703571
 /etc/pam.d/sshd 91e82cb29c884f06d65db92e90a4e159
 /etc/ufw/applications.d/openssh-server 486b78d54b93cc9fdc950c1d52ff479e
Description: secure shell (SSH) server, for secure access from remote machines
 This is the portable version of OpenSSH, a free implementation of
 the Secure Shell protocol as specified by the IETF secsh working
 group.
 .
 Ssh (Secure Shell) is a program for logging into a remote machine
 and for executing commands on a remote machine.
 It provides secure encrypted communications between two untrusted
 hosts over an insecure network. X11 connections and arbitrary TCP/IP
 ports can also be forwarded over the secure channel.
 It can be used to provide applications with a secure communication
 channel.
 .
 This package provides the sshd server.
 .
 In some countries it may be illegal to use any encryption at all
 without a special permit.
 .
 sshd replaces the insecure rshd program, which is obsolete for most
 purposes.
Original-Maintainer: Debian OpenSSH Maintainers <debian-ssh@lists.debian.org>
Homepage: http://www.openssh.org/

And check if it's running with sudo service ssh status. Example output:

sam@samhobbs:~$ sudo service ssh status
[sudo] password for sam: 
ssh start/running, process 1201

Sam

Thx for the help. Got it working. The problem was -presumably- an old authentication code in the client's cache from when I had OpenSuse on the same laptop.

[Erwin Smout]

Thx for the hint. Will consider your suggestions. Is any of these two "more recommended/supported than the other" by the "official Kubuntu authorities" (if any such thing exists) ?

[claydoh]

Muon Package manager is originally a project from a Kubuntu dev, and was the default tool before Discover. So Muon would be considered the preferred one. But use what you like.

Sent from my Verizon HTC Droid DNA smartphone running an early cyanogenmod 12 rom, with Android 5 Lollipop, via Tapatalk, as if phone stats really matter

[Erwin Smout]

Thx for the help. Got it working. The problem was -presumably- an old authentication code in the client's cache from when I had OpenSuse on the same laptop.

Still not quite there yet. After boot, sudo service ssh status gives me "ssh start/running", but NO PID. Connecting to it from the desktop client fails with network error. After sudo service ssh restart, I do get a PID, and connecting to it works. Doable, but still annoying.

[Feathers McGraw]

Still not quite there yet. After boot, sudo service ssh status gives me "ssh start/running", but NO PID. Connecting to it from the desktop client fails with network error. After sudo service ssh restart, I do get a PID, and connecting to it works. Doable, but still annoying.

How long is this after booting? It could just be taking a while to start up. There's an init script at /etc/init.d/ssh that should be starting sshd when you boot (the script is installed automatically)... you haven't changed it have you?

Also, what is the network error you are getting?

[Erwin Smout]

How long is this after booting? It could just be taking a while to start up. There's an init script at /etc/init.d/ssh that should be starting sshd when you boot (the script is installed automatically)... you haven't changed it have you?

Also, what is the network error you are getting?

It doesn't matter how long I wait. Several minutes after the desktop has come up and it's still all the same. Didn't touch any script. I have to manually restart the service before it works. The error message is just "network error - connection refused". (That sounds like firewall, but the problem is iptables is still empty and should just accept everything. And at any rate in that case a sshd restart shouldn't fix the problem.)

[Feathers McGraw]

Strange! You're not logging in as root or anything unusual are you?

[Erwin Smout]

Strange! You're not logging in as root or anything unusual are you?

The problem is the same whether I log into ssh as root or as regular user.

[Feathers McGraw]

I'm out of ideas, sorry. You might try purging and re-installing to see if that solves your problem, since I think what you want is the "out of the box" behaviour.

[SteveRiley]

Still not quite there yet. After boot, sudo service ssh status gives me "ssh start/running", but NO PID.

On the machine you're trying to connect to (running the SSH server), what's the output of

grep -a sshd /proc/*/cmdline

Ignore the possibly very long line that starts with /proc/self/cmdline.

Connecting to it from the desktop client fails with network error. After sudo service ssh restart, I do get a PID, and connecting to it works. Doable, but still annoying.

On the machine you're trying to connect from (running the SSH client), what happens if you try specifying the IP address of the server rather than the hostname?

[Erwin Smout]

On the machine you're trying to connect to (running the SSH server), what's the output of

grep -a sshd /proc/*/cmdline

Ignore the possibly very long line that starts with /proc/self/cmdline.


On the machine you're trying to connect from (running the SSH client), what happens if you try specifying the IP address of the server rather than the hostname?

I am already using the IP addresses not host names, and the /proc/self/cmdline is the only line that comes out of your grep (right after boot).

[SteveRiley]

the /proc/self/cmdline is the only line that comes out of your grep (right after boot).

Then the service definitely isn't running. Have you looked through any logs to see if the system attempts to start the service but is failing for some reason?