Your message dated Tue, 24 Mar 2020 03:54:36 +0000 with message-id <e1jgaec-0001il...@fasolo.debian.org> and subject line Bug#954779: Removed package(s) from unstable has caused the Debian Bug report #919703, regarding php7.3: sodium_crypto_pwhash() Causes Error to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: php7.3 Version: 7.3.0-2 Severity: normal Dear Maintainer, Attempting to use sodium_crypto_pwhash is triggering a (non-informative) error from libsodium. The proximate cause appears to be the final argument. I can trigger the error with the following line in an interactive PHP shell: php > echo base64_encode(sodium_crypto_pwhash(32, 'test', random_bytes(SODIUM_CRYPTO_PWHASH_SALTBYTES), SODIUM_CRYPTO_PWHASH_OPSLIMIT_INTERACTIVE, SODIUM_CRYPTO_PWHASH_MEMLIMIT_INTERACTIVE, SODIUM_CRYPTO_PWHASH_ALG_ARGON2I13)); PHP Warning: Uncaught SodiumException: internal error in php shell code:1 Stack trace: #0 php shell code(1): sodium_crypto_pwhash() #1 {main} thrown in php shell code on line 1 What I expect to see is 32 bytes of essentially random data base64-encoded. I am able to get output without an error by executing either of the follwing statements: echo base64_encode(sodium_crypto_pwhash(32, 'test', random_bytes(SODIUM_CRYPTO_PWHASH_SALTBYTES), SODIUM_CRYPTO_PWHASH_OPSLIMIT_INTERACTIVE, SODIUM_CRYPTO_PWHASH_MEMLIMIT_INTERACTIVE)); echo base64_encode(sodium_crypto_pwhash(32, 'test', random_bytes(SODIUM_CRYPTO_PWHASH_SALTBYTES), SODIUM_CRYPTO_PWHASH_OPSLIMIT_INTERACTIVE, SODIUM_CRYPTO_PWHASH_MEMLIMIT_INTERACTIVE, SODIUM_CRYPTO_PWHASH_ALG_DEFAULT)); Curiously, the default algorithm right now is supposed to be SODIUM_CRYPTO_PWHASH_ALG_ARGON2I13, so it must be something in how this is mapped to the algorithm when passed on to libsodium. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php7.3 depends on: pn libapache2-mod-php7.3 | php7.3-fpm | php7.3-cgi <none> pn php7.3-common <none> php7.3 recommends no packages. php7.3 suggests no packages.
--- End Message ---
--- Begin Message ---Version: 7.3.15-3+rm Dear submitter, as the package php7.3 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/954779 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
