Configuring Zebedee with keys for security

I'm having difficulty getting this to work.

I've narrowed it down to the uncommenting of the line

#  checkidfile ’./clients.id’

The contents of the clients.id file was generated using the example in the
documentation and the file is identical in format to the one supplied.

I'm using Zebedee 2.4.1 and the SSH port 22 instead of the default port
because my clients are behind a restrictive firewall with limited outside
access.  With the checkidfile line commented, the clients can connect
successfully.

I'm hoping its something stupid on my part but any help would be
appreciated.

The error I get on the server side is:

zebedee(4224/4228):  accepted connection from 20x.1y7.z35.115
zebedee(4224/4228):     spawning handler function thread
zebedee(4224/4228):     handler thread created
zebedee(4224/4208):    server routine entered
zebedee(4224/4228):  waiting for connection on port 22
zebedee(4224/4208):    validating client IP address
zebedee(4224/4208):     peer address from connection is 20x.1y7.z35.115
zebedee(4224/4208):    reading protocol version
zebedee(4224/4208):      readData: receiving 2 of 2
zebedee(4224/4208):      readData: EOF or error
zebedee(4224/4208): ERROR: failed reading protocol version

and the client side:

zebedee(3268/1824):      select returned 1
zebedee(3268/1824):      searching for handler for address 127.0.0.1:1260
zebedee(3268/1824):      found handler, id = 168, socket = 164
zebedee(3268/1824):      waiting for client data
zebedee(3268/2396): ERROR: can't connect to horizonint.com port 22
zebedee(3268/1824):      select returned 1
zebedee(3268/1824):      searching for handler for address 127.0.0.1:1283
zebedee(3268/1824):      listening on 127.0.0.1
zebedee(3268/1824):     spawning handler function thread
zebedee(3268/1824):     handler thread created
zebedee(3268/1824):      waiting for client data
zebedee(3268/3072):    client routine entered
zebedee(3268/3072):    client on local port 1557 tunnels to target
192.168.1.23:1557
zebedee(3268/3072):     target address is c0a80117
zebedee(3268/3072):    making connection to horizonint.com:22
zebedee(3268/1824):      select returned 1
zebedee(3268/1824):      searching for handler for address 127.0.0.1:1283
zebedee(3268/1824):      found handler, id = 172, socket = 180
zebedee(3268/1824):      waiting for client data
zebedee(3268/1824):      select returned 1
zebedee(3268/1824):      searching for handler for address 127.0.0.1:1283
zebedee(3268/1824):      found handler, id = 172, socket = 180
zebedee(3268/1824):      waiting for client data
zebedee(3268/3072): ERROR: can't connect to horizonint.com port 22

The server.zbd file is:

#
# Sample Zebedee server configuration file
#
# This shows the use of many, but not all, of the configuration file
# options available for use by a server.
#
# $Id: server.zbd,v 1.4 2002/04/16 16:49:42 ndwinton Exp $

verbosity 5	# Slightly more than basic messages

# Comment out the following line once you have read the comments
# in this file and enabled or disabled the appropriate options!

detached false	# You will probably want this 'true' for normal
		# use but I want to make sure that you see the
		# preceding message if you haven't edited this.

server true	# Yes, it's a server!
serverport 22
ipmode both	# Operate in mixed TCP/UDP mode

compression zlib:9	# Allow maximum zlib compression
keylength 256		# Allow keys up to 256 bits
keylifetime 36000	# Shared keys last 10 hours
maxbufsize 16383	# Allow maximum possible buffer size

# Uncomment the following line to log messages to a local file.
#
#logfile './server.log'
#
# Or to log to the system logging facility uncomment this:
#
#  logfile SYSLOG

keygenlevel 2	# Generate maximum strength private keys

# Uncomment the following line if you want to use a fixed private
# key stored in a static file. The file should contain a line of
# the form "privatekey hexadecimal-key-string". This file should
# be readable by the user running Zebedee but no-one else.
#
#  include './server.key'

# To validate the identity of clients use a line something like
# the following:
#
checkidfile './clients.id'

# The "redirect" expression can be use to set the default ports
# allowed when a target specification consists of a hostname but
# no other ports. The "redirect none" statement prohibits
# tunnelling anywhere by default.

redirect none

# Set up allowed targets. Note that there are NO targets allowed
# by this file by default. You must explicitly edit it to enable
# them.

# The following are good for testing purposes. Either TCP or UDP
# are allowed.
#
#  target localhost:daytime,echo,chargen

# Basic interactive services, TCP only.
#
#  target localhost:telnet/tcp,ftp/tcp

# VNC traffic -- usually you will only need a subset of this
# range, perhaps 5900 or 5901.
#
#  target localhost:5900-5999/tcp

# X Window System -- again, usually you will only need
# a subset of this range.
#
#  target localhost:6000-6010/tcp

# Here is an example of specifying targets using a subnet. In
# this case allowing tunnels to be established to VNC servers
# on the 10.1.1.xx subnet.
#
#  target 10.1.1.0/24:5900/tcp

#
# Here's the real targets
#

target 192.168.1.23:1557/udp

# The following line ensures that the default target host
# is the local machine. The last named host becomes the
# default so leaving this here ensures that "localhost" is,
# the default unless overridden on the command line.

target localhost

and the clients.id file is (a few characters changed to protect the
innocent):

#
# Authorized Clients
#
f587796ef0e0d8a14ghijklmnopqrstuvwxyz01a co-aa2
a98c352eb296066e9ghijklmnopqrstuvwxyz67f co-jz


Brad Morgan
IT Manager
Horizon Interactive Inc.



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl