Bitcoin Core 0.14.3 released

Bitcoin Core 0.14.3 released
From: Wladimir J. van der Laan @ 2018-09-28 15:37 UTC (permalink / raw)
  To: Bitcoin development mailing list, Bitcoin Core development mailing list
  Cc: Matt Corallo

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Bitcoin Core version *0.14.3* is now available from:

  <https://bitcoincore.org/bin/bitcoin-core-0.14.3/>

or through bitorrent:

  magnet:?xt=urn:btih:171edf5f51820900f24fc72620deaa07ee497dee&dn=bitcoin-core-0.14.3&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fexplodie.org%3A6969

This is a new minor version release, including various bugfixes and
performance improvements.

Please report bugs using the issue tracker at github:

  <https://github.com/bitcoin/bitcoin/issues>

To receive security and update notifications, please subscribe to:

  <https://bitcoincore.org/en/list/announcements/join/>

Compatibility
==============

Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.

Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
No attempt is made to prevent installing or running the software on Windows XP, you
can still do so at your own risk but be aware that there are known instabilities and issues.
Please do not report issues about Windows XP to the issue tracker.

Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.

Notable changes
===============

Denial-of-Service vulnerability CVE-2018-17144
 -------------------------------

A denial-of-service vulnerability exploitable by miners has been discovered in
Bitcoin Core versions 0.14.0 up to 0.16.2. It is recommended to upgrade any of
the vulnerable versions to 0.14.3, 0.15.2 or 0.16.3 as soon as possible.

Known Bugs
==========

Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
control and smart fee estimation does not reflect any change in target from the
smart fee slider. It will only present an approximate fee calculated using the
default target. The fee calculated using the correct target is still applied to
the transaction and shown in the final send confirmation dialog.

0.14.3 Change log
=================

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

### Consensus
- - #14247 `52965fb` Fix crash bug with duplicate inputs within a transaction (TheBlueMatt, sdaftuar)
 
### RPC and other APIs

- - #10445 `87a21d5` Fix: make CCoinsViewDbCursor::Seek work for missing keys (Pieter Wuille, Gregory Maxwell)
- - #9853 Return correct error codes in setban(), fundrawtransaction(), removeprunedfunds(), bumpfee(), blockchain.cpp (John Newbery)


### P2P protocol and network code

- - #10234 `d289b56` [net] listbanned RPC and QT should show correct banned subnets (John Newbery)

### Build system


### Miscellaneous

- - #10451 `3612219` contrib/init/bitcoind.openrcconf: Don't disable wallet by default (Luke Dashjr)
- - #10250 `e23cef0` Fix some empty vector references (Pieter Wuille)
- - #10196 `d28d583` PrioritiseTransaction updates the mempool tx counter (Suhas Daftuar)
- - #9497 `e207342` Fix CCheckQueue IsIdle (potential) race condition and remove dangerous constructors. (Jeremy Rubin)

### GUI

- - #9481 `7abe7bb` Give fallback fee a reasonable indent (Luke Dashjr)
- - #9481 `3e4d7bf` Qt/Send: Figure a decent warning colour from theme (Luke Dashjr)
- - #9481 `e207342` Show more significant warning if we fall back to the default fee (Jonas Schnelli)

### Wallet

- - #10308 `28b8b8b` Securely erase potentially sensitive keys/values (tjps)
- - #10265 `ff13f59` Make sure pindex is non-null before possibly referencing in LogPrintf call. (Karl-Johan Alm)

Credits
=======

Thanks to everyone who directly contributed to this release:

- - Cory Fields
- - CryptAxe
- - fanquake
- - Jeremy Rubin
- - John Newbery
- - Jonas Schnelli
- - Gregory Maxwell
- - Karl-Johan Alm
- - Luke Dashjr
- - MarcoFalke
- - Matt Corallo
- - Mikerah
- - Pieter Wuille
- - practicalswift
- - Suhas Daftuar
- - Thomas Snider
- - Tjps
- - Wladimir J. van der Laan

And to those that reported security issues:

- - awemany (for CVE-2018-17144, previously credited as "anonymous reporter")

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAluuSowACgkQHkrtYphs
0l3XtggArfc/1tCcIunvUIyooq7nb27AwltySOBFCFH/R1v6mcSN6ZHAEKC3uBA6
WkhrGChV8XqNELKau7w1riubPjMHNTj0k4+DBtaDNN41EAF+1bhHWbxQ4006tZHb
WN2coxX+iNPI9uj3m0MnbulZpy+c7w1azO8eULcZjkqkccRBl6p4Y3uePr7CbbKU
/h517ziI7UwYChKsF3tC7CX+3vDi7oyfZd5QCKmtEFicS4j0UADtsLdF2GlMkpyD
yffAq/jpDXrIMWXrseZe60UPTijaA2mokk8/SdGy0hKn9Qx/VB0EIYKVPMD4gDUg
iSFcmsELYzBzk01Jg29GLzCbI7rQYw==
=MOiO
-----END PGP SIGNATURE-----


 permalink raw reply	[|nested]