Project

General

Profile

Actions

Bug #3840

closed

Disable (or give the option to disable) the OS addition to the SSH daemon banner

Added by Jim Pingle over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Category:
Operating System
Target version:
Start date:
08/29/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

By default ssh on FreeBSD adds a VersionAddendum of the FreeBSD version in use. It would be best to hide that to avoid broadcasting the OS version to anyone who can connect to the SSH port.

We can add a line with the VersionAddendum directive only (no parameters) to use an empty version

: nc localhost 22
SSH-2.0-OpenSSH_5.4p1_hpn13v11 FreeBSD-20100308
^C
: echo VersionAddendum >> /etc/sshd_config
: killall -HUP sshd
: nc localhost 22
SSH-2.0-OpenSSH_5.4p1_hpn13v11
^C

Actions #1

Updated by Renato Botelho over 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #3

Updated by Jim Thompson over 9 years ago

  • Assignee set to Renato Botelho

JimP, you realize this does nothing, right?

Actions #4

Updated by Jim Pingle over 9 years ago

  • Status changed from Feedback to Resolved

Tested on a current snapshot, FreeBSD version is gone now. Looks good.

Jim Thompson wrote:

JimP, you realize this does nothing, right?

Functionally, yes, it only hides the FreeBSD version string and doesn't fix anything.

But with the OS version present in the banner scanners assume it's FreeBSD 8.3 and whinge about the version being unsupported. Which isn't true in our case since it's not FreeBSD 8.3, but pfSense 2.1.x, where we maintain our own security patches. It's safer to err on the side of caution and not provide anyone who can connect to the SSH port with more information than they need. None of the other commonly-exposed daemons advertise the exact FreeBSD version in the same way.

If nothing else, it will at least stop automated scanners from incorrectly flagging pfSense as "outdated" which has caused users to fail audits. That part will be a non-issue once 2.2 is out but IMO it's still best to not hand out more info than required for clients to safely connect.

Actions #5

Updated by Renato Botelho over 9 years ago

What about add pfSense version instead of FreeBSD's?

Actions #6

Updated by Jim Pingle over 9 years ago

Personally I'd prefer to omit any extra information rather than announcing that willingly.

Actions

Also available in: Atom PDF