From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <525330fea6c45dbd3b6f536586068661@proxima.alt.za>
To: 9fans@9fans.net
From: Lucio De Re <lucio@proxima.alt.za>
Date: Fri, 10 Dec 2010 05:19:42 +0200
In-Reply-To: <5D2229A6-AD5A-4B71-A17E-581A15603621@9srv.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] tls[srv,client] confusion
Topicbox-Message-UUID: 8aa4d2ba-ead6-11e9-9d60-3106f5b1d025

> After running something like the following on the server:
> 	: root; auth/rsagen -b 2048 -t 'service=tls owner=*' >/tmp/keykey
> 	: root; auth/rsa2x509 'C=US CN=9srv.net' /tmp/key | auth/pemencode CERTIFICATE > /tmp/cert
> 	: root; cat /tmp/key > /mnt/factotum/ctl
> 	: root; aux/listen1 -tv 'tcp!*!21234' /bin/tlssrv -c /tmp/cert -Dl /tmp/out /bin/date
> I'd expect "tlsclient tcp!9srv.net!21234" elsewhere on the network to print the date. It's not; instead, it exits with no output (and with $status unset). The connection's getting to listen1 and some sort of binary data is returned (tested with con), but tlsclient seems not to like it. Are my expectations right?

Have you tried " echo debug >/mnt/factotum/ctl"?

The /tmp/keykey vs /tmp/key above is a bit worrying, but you would
have picked it up interactively.

Lucio.