From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] tls 1.2
Date: Tue, 15 Nov 2016 16:22:02 +0000 [thread overview]
Message-ID: <c1a4f0ee84ee7bc0d8c7299e266662ff@quintile.net> (raw)
In-Reply-To: <CANUoZoGp+Ex4CYHx=CrQtSf1n=Lbpq_RqDVuyFemX9YcP=6Rwg@mail.gmail.com>
> The libsec-chacha.diff patch is not useful, since it's not used yet.
I suspected as much but thought it wouldn't hurt.
> Does it works when you connect to https://9p.io/?
> This machine have the same patches applied.
yes, this works fine.
I am trying to connect to davmail - an exchange / imap+smtp gateway, hosted on windows
so I am talking to a windows tls implementation which may well be the cause of my frustration.
There is a very suspicious block of code:
if((tr->handin == 0) && (header[0] & 0x80)){
if(tr->debug)pprint("weird MS header\n");
/* Cope with an SSL3 ClientHello expressed in SSL2 record format.
This is sent by some clients that we must interoperate
with, such as Java's JSSE and Microsoft's Internet Explorer. */
len = (get16(header) & ~0x8000) - 3;
type = header[2];
ver = get16(header + 3);
if(type != SSL2ClientHello || len < 22)
rcvError(tr, EProtocolVersion, "invalid initial SSL2-like message");
}else{ /* normal SSL3 record format */
if(tr->debug)pprint("normal SSL3 header\n");
type = header[0];
ver = get16(header+1);
len = get16(header+3);
}
Though I have tried looking at the contents of this buffer in case it has subtly changed and
it bears no relation to this case so maybe thats a red herring (false lead to non British people).
-Steve
next prev parent reply other threads:[~2016-11-15 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 15:48 Steve Simon
2016-11-15 15:55 ` hiro
2016-11-15 16:23 ` Steve Simon
2016-11-15 16:00 ` David du Colombier
2016-11-15 16:22 ` Steve Simon [this message]
2016-11-16 8:18 ` David du Colombier
2016-11-15 16:03 ` David du Colombier
2016-11-15 16:22 ` Steve Simon
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=c1a4f0ee84ee7bc0d8c7299e266662ff@quintile.net \
--to=steve@quintile.net \
--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).