By default (on Debian system) Xen uses ttyS0 as serial console, and that causes conflict with kernel module 8250.ko. I personally met this trying to setup ‘nut’ package for UPS handling. The solution was found on XenSource page. Actually you just need to add # xenkopt=xencons=ttyS16 line to /boot/grub/menu.lst, do ‘update-grub’ and reboot.
Now I am on Sun Tech Days at St-Petersburg. Just 10 minutes ago I win the Solaris book authographed by Ian Murdok, creator of Debian Linux, currently Sun employee working on Sloaris), who is one of the speakers of this event. The site of the book is here.
Wifi coverage is everywhere in the building, so I could write it right now. The whole event is very well organized and very interesting, so thanks to Sun Microsystems!
Oftenly network services give away information on what platform thay run. If you look what SSH daemon replies on your telnet request, you’ll see string like this probably:
SSH-1.99-OpenSSH_3.8.1p1 Gentoo-8.2.4
It is obvious that as on of security measures it is good idea to may harder for attacker to gain any information about system we protect; for example, well-known Linux Iptables Tutorial says: “The best thing to do, is to give as little material as possible for the attacker to get a proper fingerprint on.” I could imagine only one reason for such unsecure behaviour of SSH service: to allow collect statistic information. But if you are admin of this host, you know what OS is there. If you are not, it’s not your business, right?
In most OSes and distros there is no command-line or config file option to turn off such verbosity. So, at first, there are the one way to do this: get sshd source, patch it, compile it, and install it. And you should do this after each security update.
But we could apply the simple patch right on the sshd binary executable, because we know exactly what to change. SSH daemon is written in C, so all the text strings are plain text strings, starting at fixed offset fron begin of file are ended by zero-byte. We could easily modyfy such string, if it is unique in binary file an if new text will be no longer than original one. At the and we will put a zero byte, it will be interpreted as the end.
What exactly would we like our SSH to answer? Theoretcally, it should be anything starting with ‘SSH’, but in practice there are some restrictions. There are different ssh server implementations, and many clients use that banner string to recognize specific servers with specific bugs (i.e, if you have Putty (ssh client), look to “Connection”>”SSH”>”Bugs” screen in settings window). This topic on commercial SSH implementation forum states that minimal safe string would be ‘SSH-2.0-0′. My own expirience is limited, but there was no problem with such banner string.
Searching for tool, my first look was at unix utility ’sed’, but it is wrong tool for this job. As sed documentation says:
Specifically, use awk or perl if you need to: (…) handle binary data (control characters). (perl: binmode)
So, I use perl one-liner (look at ‘perlrun’ for more explanation):
PERLIO=':raw'; export PERLIO; perl -pi.bak -e 's{(OpenSSH)_([^\x00]+Debian)}{$1\x00$2}’ /usr/sbin/sshd
.
I’m located in St.Petersburg, Russia; the time here is GMT +3.
Please feel free to contact me.
Some time ago I noted the same problem on Debian hosts having root file system on software RAID. After each kernel upgrade Debian cannot boot, complaining on inaccessible root FS. As I figured, the problem was in generating initrd.img for new kernel. (read more…)
