From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@9fans.net
Subject: Re: [9fans] tls[srv,client] confusion
Date: Fri, 10 Dec 2010 05:19:42 +0200 [thread overview]
Message-ID: <525330fea6c45dbd3b6f536586068661@proxima.alt.za> (raw)
In-Reply-To: <5D2229A6-AD5A-4B71-A17E-581A15603621@9srv.net>
> 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.
next prev parent reply other threads:[~2010-12-10 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 2:09 Anthony Sorace
2010-12-10 3:19 ` Lucio De Re [this message]
2010-12-10 13:20 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525330fea6c45dbd3b6f536586068661@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).