From: nigel@9fs.org
To: 9fans@cse.psu.edu
Cc: 9trouble@plan9.bell-labs.com
Subject: Re: [9fans] tlssrv
Date: Fri, 14 Jun 2002 14:45:56 +0100 [thread overview]
Message-ID: <b2231c5c3355235971e005ab1b7891f9@9fs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 146 bytes --]
Oh right. When debugging tlssrv, use two -Ds (to enable dumping).
One -D debugs the handshake, but then messes up the tunnel (don't
know how).
[-- Attachment #2: Type: message/rfc822, Size: 1915 bytes --]
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: [9fans] tlssrv
Date: Fri, 14 Jun 2002 14:34:17 +0100
Message-ID: <d739af4c9f71ed8de5f45ebf70c06d2f@9fs.org>
Trying tlssrv (via tcp993) with Outlook Express I get successful establishment
of the tunnel, but by the look of it no data transfer. This is based on
the log file with tcp993 setting -D for tlssrv and -v for imap4d. I see
cpu Jun 14 13:37:18 192.168.100.111!1104 tls reports tls secrets
cpu Jun 14 13:37:18 192.168.100.111!1104 tls reports recv HFinished
52bdd00117f027d40ebca361
cpu Jun 14 13:37:18 192.168.100.111!1104 tls reports send HFinished
a16de6cbdf068b098317665a
cpu Jun 14 13:37:18 192.168.100.111!1104 tls reports tls finished
cpu Jun 14 13:37:18 192.168.100.111!1104 tls reports open
: imap4d debugging enabled
* ok cpu.9fs.org IMAP4rev1 server ready
and then Outlook Express times out.
Any hints on how to debug this?
next reply other threads:[~2002-06-14 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 13:45 nigel [this message]
2002-06-17 9:14 ` Christopher Nielsen
-- strict thread matches above, loose matches on Subject: below --
2002-06-17 19:47 Russ Cox
2002-06-17 13:47 Russ Cox
2002-06-17 19:02 ` Christopher Nielsen
2002-06-17 11:08 nigel
2002-06-17 18:59 ` Christopher Nielsen
2002-06-14 13:34 nigel
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=b2231c5c3355235971e005ab1b7891f9@9fs.org \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.edu \
--cc=9trouble@plan9.bell-labs.com \
/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).