Bitcoin Core 0.15.01 exe not digitally signed..

[Icon]

Yes about to run the qt and noticed the .exe was not signed.. as far as windows 10 smart screen goes, didn't have that problem with 0.14.1...


Icon

[1715468976]

1715468976

[1715468976]

1715468976

[1715468976]

1715468976

[achow101]

What do you see about it that is not signed? Only the installers are signed and nothing changed in the release process that makes them not signed.

[Icon]

Ah windows defender smartscreen in windows 10.  14.01 doesn't have that problem. Not sure whats happening. i know you can digital sign an .exe that runs in windows but your right its normally in installers..

Probably nothing to worry about..

Icon

[miguelmorales85]

Yes about to run the qt and noticed the .exe was not singed.. as far as windows 10 goes, didn't have that problem with 0.14.1...


Icon

Hello Icon, can you explain how do you check if the .exe is not signed? Maybe is something to report in github.

Could you please change the subject of your post to something more specific about this issue with windows 10 bitcoin core client?
It can be confusing to those looking in the forum about 0.15

Regards,

[Cereberus]

Ah windows defender smartscreen in windows 10.  14.01 doesn't have that problem. Not sure whats happening. i know you can digital sign an .exe that runs in windows but your right its normally in installers..

Probably nothing to worry about..

Icon

If you downloaded it from the official website ,absolutely nothing to worry about. In the defender smart screen, click more Info and Run it is the same and I am sure you already do it this way. Windows 10 does a lot of updates as Microsoft has stated this will be their final operating system and will update it a lot.

[Lauda]

If you downloaded it from the official website ,absolutely nothing to worry about.

An absolutely ignorant and bullshit statement. There are so many attacks that can be executed by space-sponsored attackers while you "download from the official website". If you don't:
1) Verify the hashes, OR
2) Compile from source yourself,

Then there is absolutely no way you can claim that there is "absolutely nothing to worry about". Stop posting about matters in which you clearly lack knowledge.

Ah windows defender smartscreen in windows 10. 

Whilst I'm unsure what your exact issue is, disable this bloatware from MS. All it does is spy on you and doesn't really help.

[mpufatzis]

Is it possible to run the Core in a PC (running Ubundu) having two Hard Disks 100GB each?

[Lauda]

Is it possible to run the Core in a PC (running Ubundu) having two Hard Disks 100GB each?

You can do that in pruned mode, since the blockchain is over 100GB and you won't be able to store it on a single 100GB disk otherwise. This is not the right thread to ask your own questions FYI.

[Icon]

Yes about to run the qt and noticed the .exe was not singed.. as far as windows 10 goes, didn't have that problem with 0.14.1...


Icon

Hello Icon, can you explain how do you check if the .exe is not signed? Maybe is something to report in github.

Could you please change the subject of your post to something more specific about this issue with windows 10 bitcoin core client?
It can be confusing to those looking in the forum about 0.15

Regards,

Done and done, i tried to clarify what i meant

I miss the good old days where you could run the certUtil -hashfile on the file and verify the sig...

https://bitcointalk.org/index.php?topic=1588906.0
 

[Lauda]

I miss the good old days where you could run the certUtil -hashfile on the file and verify the sig... https://bitcointalk.org/index.php?topic=1588906.0

What makes you think that you can't do that anymore? Current SHA sums:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

b1ac0cd472f98040fbce9cea79348da2c6140a452427f9fe56d060413ec67f2d  bitcoin-0.15.0.1-aarch64-linux-gnu.tar.gz
7fb2290464ff056213593878cac1d111422204e81b1ccb93f95b145c309895c5  bitcoin-0.15.0.1-arm-linux-gnueabihf.tar.gz
061bdd552fdc048a98e04ab436165b121346ecd989e1bc91db0246888fcadf7d  bitcoin-0.15.0.1-i686-pc-linux-gnu.tar.gz
23a36e28295ef05faf67d41be0610d5f5f1059d904aa74efca7a6700a82d6dc2  bitcoin-0.15.0.1-osx64.tar.gz
9f90a5b5623287b762e3280fd86fc7adc7180a071513d5d663133f030452b1dd  bitcoin-0.15.0.1-osx.dmg
b57e9e756018e4082f5557a4216195b0cd197c5a62473b6fe0509a0aa71e519b  bitcoin-0.15.0.1.tar.gz
f3e7ef9ac9d510a185efb0f0253dc1f49d627768999a66f13e86de4c38854680  bitcoin-0.15.0.1-win32-setup.exe
49578a464d043f278805b145cd8f59b115e6f41cd56de0a90049da1781df9d59  bitcoin-0.15.0.1-win32.zip
f0aebade2b43e253ad66fd920e00524048f5a9b9933936e735844d316433791a  bitcoin-0.15.0.1-win64-setup.exe
25efad99a4128d9f197d7eb1c175e7597478ae39e3d05805f14e9c01392b41ae  bitcoin-0.15.0.1-win64.zip
ae3efa47bf87a694a5368cd6fea96c9942fe9be7856720b5027c8902e46a88d1  bitcoin-0.15.0.1-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJZwQqFAAoJEJDIAZ42wulkZQ0P/0hkk9rcBenvHjUAQ1mYeSAW
T8mxFosWT24TDR5EO3vgemaNpzmr3W4hs46gIuM7cIqmKHMPcYNdt3PkYUiu7x9A
nFf76AjeHjwDNclOas746I8vMMB6pry6qO4hFF2WuLKRlBYjMKJIMjYrkmm4kur6
8GUwvJX7XnfgzJxMCLkaBPLiTYCAwKqPks4hbGdn6OWEefS1EjrLY8U4Ytkt03ZU
OceP0LYuFIC0NhaOMzv6EPeH83WAeIQgqmx3xZfewqPCCmj/7g/eK8VLp6ouZ6oL
YSSMZerN+n6BNDYVYy42LVwF2wDqTHIyDHQy5MEd038oeVjs9aj4yXv/2snj08FB
H39mum1sx7AW2GfjZPO7XvjkyfEJphB0VWGxAh/Ht01pMA6LzoH87m1MU6GZVJ8w
jPHNqAmEanhINv00OFmfDBWIaY5EUpiA30T7OaH8Z8fiwpBVOoNMWS5aO02TAQtp
OUhSUaY5zorgguhKhZbPjBniP5IcdSLVfIPCYBCYIuoj1hnhtDkJUaajhvSpTbZT
SqPIW402aKSr0T/Dob7CwD5F2DRoq550BvbLQyE6PU0niXbX2SCIeGqRanrtT336
MExaKCnEWXOxhbSQd9tV1Se9IGLfR0ac3pFPINwtVXVum20sTN79B3rBS3OlzC3d
1T7DWnSvkb2o6glQ00SL
=kBtV
-----END PGP SIGNATURE-----

e.g. for your Windows, you'd get:

[Icon]

Yep its right i thought that blob was a PGP signature  not the actual sha256, had to load into Word to sort that mess ..

All good

Icon