A hack to make dbclient to tcp forwarding netcat style. eg ./dbclient -i testkey -L 1234:remotehost:remoteport tunnelhost will ssh to tunnelhost (using testkey, there's no way to ask for a password) and then tcpfwd to remotehost:remoteport on stdin/stdout. There's no way to give a cmdline password, so -i for a keyfile will have to do. Yet another reason for agent forwarding. The 1234 is a dummy var, I think it has to be a valid portnumber though.

CFLAGS += -I../src/headers -I./ 
CC=icc

OBJECTS = base64_test.o cipher_hash_test.o der_tests.o dh_tests.o                        \
dsa_test.o ecc_test.o mac_test.o modes_test.o pkcs_1_test.o rsa_test.o                   \
store_test.o test.o x86_prof.o

default: libtomcrypt_prof.a

libtomcrypt_prof.a: $(OBJECTS)
	$(AR) $(ARFLAGS) libtomcrypt_prof.a $(OBJECTS)

clean:
	rm -f *.o *.a