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
We recently investigated the Bitcoin issues which are related to privacy protection, vulnerability patches, or security enhancements. We have also checked the repoName source code. Results show that these issues and their PRs are not backported yet. Henceforth, we suggest that repoName should backport the PRs listed below for the considerations of software security and integrity.
Some of these issues and PRs are not severe security-related, but backports can avoid the chaos ecosystem of Bitcoin-forked projects and the potential vulnerabilities in the future.
Reported by de957ad9679f28a38f02f00cc7928bce8fb424882ff060a3c09c32895b1474cc.
The text was updated successfully, but these errors were encountered:
Bitcoin PR#14341 should also be backported from my view. Though I didn't see the completely same functions in Bitcoin-SV (function declaration and its implementations may be different), the way of Bitcoin to handle abnormal Node crash should be referenced.
We recently investigated the Bitcoin issues which are related to privacy protection, vulnerability patches, or security enhancements. We have also checked the
repoName
source code. Results show that these issues and their PRs are not backported yet. Henceforth, we suggest thatrepoName
should backport the PRs listed below for the considerations of software security and integrity.Char
variable used asBool
.nLockTime
fingerprint.InterruptRPC()
.Some of these issues and PRs are not severe security-related, but backports can avoid the chaos ecosystem of Bitcoin-forked projects and the potential vulnerabilities in the future.
Reported by
de957ad9679f28a38f02f00cc7928bce8fb424882ff060a3c09c32895b1474cc
.The text was updated successfully, but these errors were encountered: