From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] dp9ik draft
Date: Tue, 20 Oct 2015 05:33:47 +0200 [thread overview]
Message-ID: <db50f7773765f1c4a9e2523da7d01d2f@felloff.net> (raw)
In-Reply-To: <fb8a700b70058ecd92627bcaa3a9b3aa@felloff.net>
Robert Ransom pointed out offlist that the pak crypto is flawed in this
draft so its back to the drawing board. please consider this version
of the draft retracted :-)
> If an attacker can find scalars s1 and s2 such that s1*H(p1) =
> s2*H(p2), then he can send s1*H(p1) as his public key, receive the
> other party's public key P and a message encrypted using the resulting
> shared secret key, then compute both possible shared secrets s1*P and
> s2*P and try each of them to decrypt the message.
>
> If H(p) = p*G, then s1*H(p1) = s1*p1*G = s1*(p1/p2)*p2*G =
> s1*(p1/p2)*H(p2) (with the divisions and multiplications computed in
> the ring of scalars).
--
cinap
prev parent reply other threads:[~2015-10-20 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 19:25 cinap_lenrek
2015-10-19 19:55 ` cinap_lenrek
2015-10-20 3:33 ` cinap_lenrek [this message]
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=db50f7773765f1c4a9e2523da7d01d2f@felloff.net \
--to=cinap_lenrek@felloff.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).