> 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?
you can't use an absolute path with -l, since syslog(2) is used. perhaps this ratrace output is incorrect, but the incorrect .pem format looks interesting. 84738 tlssrv Close 4510 0 = 0 "" 1291949790261418380 1291949790261436551 84738 tlssrv Open 44d0 0x5fffde48/"/proc/84738/notepg" 0x1/"" 8192 -1 = -1 incorrect .pem file format: bad header or trailer 1291949788499213362 1291949790256029078 84732 tlssrv Close 4510 0 = 0 "" 1291949790266803159 1291949790267010374 = 0 "" 1291949790274953275 1291949790274972061 - erik
