From: Marko <mbencun@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Fwd: BIP 340 updates: even pubkeys, more secure nonce generation
Date: Tue, 3 Mar 2020 12:29:22 +0100 [thread overview]
Message-ID: <ceeb0cd5-e5fe-5c01-df84-bbb761c41f95@gmail.com> (raw)
In-Reply-To:
That is an interesting point. Does the same concern apply to anti nonce
covert channel protocols? In those, the host would mix in a random nonce
of its own. The process is still deterministic and can be checked during
signing, but unless the host persists the nonce contributions it
provides, one can't check how the nonce was computed for past
signatures. I am unsure how desirable this property would be in
practice, though. I am guessing not that desirable, but it would be good
to hear other opinions.
See
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-February/017655.html
and
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-February/017663.html
Best, Marko
next reply other threads:[~2020-03-03 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 11:29 Marko [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-24 4:26 [bitcoin-dev] " Pieter Wuille
[not found] ` <CAMZUoKkAebw6VzSco3F+wnLptNwsCiEw23t2pLj0xitiOSszMQ@mail.gmail.com>
2020-02-26 3:26 ` [bitcoin-dev] Fwd: " Russell O'Connor
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=ceeb0cd5-e5fe-5c01-df84-bbb761c41f95@gmail.com \
--to=mbencun@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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