Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89800
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain paragonie.com from 209.85.215.45 cause and error)
MIME-Version: 1.0
Date: Thu, 10 Dec 2015 16:37:25 -0500
Message-ID: <CAKws9z1VJW9zTb3sp-9OGetA1k1NsMg8nV8YGQuL0pFmV6a7Ew@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113f239e44e6f5052692037f
Subject: Phar stubs and signatures
From: scott@paragonie.com (Scott Arciszewski)

--001a113f239e44e6f5052692037f
Content-Type: text/plain; charset=UTF-8

Hi,

Is there any reason why we can't use Phar::setSignatureAlgorithm() after
Phar::setStub()?

https://github.com/defuse/php-encryption/pull/139

PHP Fatal error:  Uncaught exception 'PharException' with message
'unable to copy stub of old phar to new phar
"/var/www/defuse/php-encryption/dist/defuse-crypto.phar"' in
/var/www/defuse/php-encryption/other/build_phar.php:37
Stack trace:
#0 /var/www/defuse/php-encryption/other/build_phar.php(37):
Phar->setSignatureAlgorithm(16, '-----BEGIN PRIV...')
#1 {main}
  thrown in /var/www/defuse/php-encryption/other/build_phar.php on line 37


If there's a reason this shouldn't allowed, could the documentation please
be updated to reflect this decision?

If this is a bug, it's breaking our ability to publish signed a .phar for
defuse/php-encryption

(And if I somehow overlooked something, please let me know.)

Thanks,

Scott Arciszewski
Chief Development Officer
Paragon Initiative Enterprises <https://paragonie.com>

--001a113f239e44e6f5052692037f--