public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Steve Davis <steven.charles.davis@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Script Abuse Potential?
Date: Mon, 2 Jan 2017 15:39:24 -0600	[thread overview]
Message-ID: <400152B9-1838-432A-829E-13E4FC54320C@gmail.com> (raw)
In-Reply-To: <mailman.11263.1483391161.31141.bitcoin-dev@lists.linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 286 bytes --]

Hi all,

Suppose someone were to use the following pk_script:

[op_2dup, op_2dup, op_2dup, op_2dup, op_2dup, ...(to limit)..., op_2dup, op_hash160, <addr_hash>, op_equalverify, op_checksig]

This still seems to be valid AFAICS, and may be a potential attack vector?

Thanks.


[-- Attachment #2: Type: text/html, Size: 1336 bytes --]

       reply	other threads:[~2017-01-02 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11263.1483391161.31141.bitcoin-dev@lists.linuxfoundation.org>
2017-01-02 21:39 ` Steve Davis [this message]
2017-01-03  3:27   ` [bitcoin-dev] Script Abuse Potential? Jeremy
2017-01-03  3:39     ` Johnson Lau
2017-01-03  5:04       ` Russell O'Connor
2017-01-04  0:13       ` Jeremy
2017-01-04  3:13         ` Russell O'Connor
2017-01-04 14:45           ` Jorge Timón
2017-01-05 16:22             ` Jeremy

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=400152B9-1838-432A-829E-13E4FC54320C@gmail.com \
    --to=steven.charles.davis@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.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