From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] out of bound access in libsec
Date: Tue, 17 Jan 2017 22:27:42 +0100 [thread overview]
Message-ID: <355339a4ebae631de2783a2d15952250@felloff.net> (raw)
In-Reply-To: <CAHL7psHxJp6wBDpRFr7a48EVsNtT7rFQ=4eLuZ7AdpuMNpRBnQ@mail.gmail.com>
on 2), how is there an out of bounds access? m->u.finished.n gets
initialized to c->finished.n, which is eigther 0 before setVersion()
as emalloc() zeros the TlsConnection struct or SSL3FinishedLen/TLSFinishedLen
after when we got the client/server hello. not 32767.
--
cinap
next prev parent reply other threads:[~2017-01-17 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 20:59 Giacomo Tesio
2017-01-17 21:27 ` cinap_lenrek [this message]
2017-01-17 21:36 ` [9front] " cinap_lenrek
2017-01-17 21:51 ` cinap_lenrek
2017-01-17 22:50 ` Giacomo Tesio
2017-01-17 22:55 ` cinap_lenrek
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=355339a4ebae631de2783a2d15952250@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).