From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Sorace Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-34-107154204" Content-Transfer-Encoding: 7bit Date: Thu, 9 Dec 2010 21:09:26 -0500 Message-Id: <5D2229A6-AD5A-4B71-A17E-581A15603621@9srv.net> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Mime-Version: 1.0 (Apple Message framework v1082) Subject: [9fans] tls[srv,client] confusion Topicbox-Message-UUID: 8a9e90c6-ead6-11e9-9d60-3106f5b1d025 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-34-107154204 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii After running something like the following on the server: : root; auth/rsagen -b 2048 -t 'service=3Dtls owner=3D*' = >/tmp/keykey : root; auth/rsa2x509 'C=3DUS CN=3D9srv.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? --Apple-Mail-34-107154204 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAk0Bi9YACgkQyrb52b5lrs5tmgCeIok6mcg0g/Uk2oC50WEE8EYl sEwAn2GLbbwPATStgFSu21wrQTxbg0KS =yimp -----END PGP SIGNATURE----- --Apple-Mail-34-107154204--