Your message dated Fri, 5 Jul 2019 15:17:44 -0400
with message-id <[email protected]>
and subject line confirmed fixed in 0.25
has caused the Debian Bug report #892855,
regarding Blake2bp_512 produces all zeros or segfaults
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 [email protected]
immediately.)
--
892855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892855
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libghc-cryptonite-dev
Version: 0.23-2+b3
Severity: normal
{-# LANGUAGE OverloadedStrings, PackageImports #-}
import "cryptonite" Crypto.Hash
import Data.ByteString.Lazy
main = print $ blake foo
where
blake :: ByteString -> Digest Blake2bp_512
blake = hashlazy
foo :: ByteString
foo = "foo"
When run in ghci, this program segfaults. When compiled with ghc and
run, it prints out a bunch of zeros which is not the correct hash.
I tried installing cryptonite-0.25 with cabal, and did not have the
problem with that build of the library.
Reproduced the problem on my Lenovo Yoga 710 laptop, and on a Linode
VPS, both running Debian unstable amd64.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-1-amd64 (SMP w/4 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 libghc-cryptonite-dev depends on:
ii ghc [libghc-integer-gmp-dev-1.0.0.1-b34f3] 8.0.2-11
ii libc6 2.27-1
pn libghc-base-dev-4.9.1.0-d28d6 <none>
pn libghc-bytestring-dev-0.10.8.1-45b2c <none>
pn libghc-deepseq-dev-1.4.2.0-fb727 <none>
ii libghc-foundation-dev [libghc-foundation-dev-0.0.17-14e77] 0.0.17-1
pn libghc-ghc-prim-dev-0.5.0.0-a46b8 <none>
ii libghc-memory-dev [libghc-memory-dev-0.14.11-1fadd] 0.14.11-1
ii libgmp10 2:6.1.2+dfsg-2
libghc-cryptonite-dev recommends no packages.
Versions of packages libghc-cryptonite-dev suggests:
pn libghc-cryptonite-doc <none>
pn libghc-cryptonite-prof <none>
-- no debconf information
--
see shy jo
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
I've tested libghc-cryptonite-dev 0.25-5+b1 and it no longer has the
bug, so it appears to have been fixed in upstream version 0.25.
--
see shy jo
signature.asc
Description: PGP signature
--- End Message ---
