From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] tlssrv and tlsclient
Date: Fri, 20 Feb 2009 21:33:04 +0900 [thread overview]
Message-ID: <CF13DC81-075C-4E42-99CC-330122D6B1F6@ar.aichi-u.ac.jp> (raw)
Hello,
I am hung up! Please any one help me.
io% aux/listen1 'tcp!*!8010' /bin/tlssrv -c/sys/tls/cert /bin/aux/
trampoline 'tcp!io!7'
term% tlsclient tcp!io!8010
tlsclient: tlsclient: devtls expected ver=301, saw (len=28207) type=2f
ver=6269 '/bin/�H\x11��!'
term%
tlssrv and tlsclient fails in negotiation at version confirmation.
what's wrong?
- certificate "/sys/tls/cert" is working for Pegasus.
- tcp!io!7 is working.
- tlsclient can communicate with Pegasus in https protocol.
- tlssrv and tlsclient are the most recent ones:
term% ls -l /bin/tlssrv /bin/tlsclient
--rwxrwxr-x M 9 sys sys 199254 May 10 2008 /bin/tlsclient
--rwxrwxr-x M 9 sys sys 199634 Jun 27 2008 /bin/tlssrv
term%
Kenji Arisawa
reply other threads:[~2009-02-20 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CF13DC81-075C-4E42-99CC-330122D6B1F6@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).