You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mentioned sum in the signed file is: 324a2be5c310f3a403f87b34bb2550f2
The md5sum of the downloaded file is: 73fa7b5831fd59f68925ef5ce7493327
But checking the deb with "dpkg-sig" and checking the "armory_0.86-beta_md5.txt.asc" with gpg leads me to correct signatures. Checking the "armory_0.86-beta_windows_all.msi " everything seems fine.
Could you look into that and correct the md5sum if it is incorrect?
Thank you very much.
The text was updated successfully, but these errors were encountered:
I bet I know exactly what happened -- I bet I computed the MD5 sums before gpg-signing the .deb files. Thus, the act of signing the packages changed the MD5 sum. Whoops!
You can trust the signature on the package. I'll be sure to check my order of operations for my next release. I might be releasing a 0.86.1 bugfix release soon, and I'll do it right, there.
af2da22 Add new tests for invalid Bech32 strings (Clark Moody)
Pull request description:
Similar updates in the vein of etotheipi#27, etotheipi#29, etotheipi#30, etotheipi#31, etotheipi#32
Adds invalid Bech32 string test cases.
Please note: Rust strings are UTF-8, so that the character literal `0xff` [turns into](https://codepoints.net/U+00FF) `0xc3bf` when accessed with the `bytes` function.
Tree-SHA512: 73f85762fc22059acb9c4b382068997fb0341354f1de26ecb2d75ba3c57aee80609fd2839967541c9a9f96ccdc04137140174396f5acfe62a6511fd9f18e703e
The mentioned sum in the signed file is: 324a2be5c310f3a403f87b34bb2550f2
The md5sum of the downloaded file is: 73fa7b5831fd59f68925ef5ce7493327
But checking the deb with "dpkg-sig" and checking the "armory_0.86-beta_md5.txt.asc" with gpg leads me to correct signatures. Checking the "armory_0.86-beta_windows_all.msi " everything seems fine.
Could you look into that and correct the md5sum if it is incorrect?
Thank you very much.
The text was updated successfully, but these errors were encountered: