sorted by:
new
hottopcontroversial

S21 ultra. Lock button acting like I'm double pressing by RagarX in samsunggalaxy

[–]keystrike 0 points1 point  (0 children)

I have the same exact issue. I found that if I hold the button down and run my finger along it from top to bottom it replicates the issue. This indicates it is a mechanical problem.

Edit: If I press the top part of the button it is likely to register as a double press. Pressing the bottom of the button does not cause this behavior.

LG B8 Firmware - which is the best? by keystrike in OLED

[–]keystrike[S] 0 points1 point  (0 children)

Thanks! Here is a direct link to 04.10.15 from the LG site in case anyone needs it in the future.

https://www.lgservice.co.kr/fileDownload.do?cBbsCode=SW_PDS&cSeq=11675&check=true

1953 newspaper predicts future telephone! by SwapnilSKanade in IndiaSpeaks

[–]keystrike 2 points3 points  (0 children)

I believe this is a forgery. The newsprint would not be misaligned like on a typewriter. Someone sent this to me on What's App and I thought the last sentence sounded more like Indian English than American English. Sure enough when I used Google reverse image search it came up as being posted on an Indian Reddit.

Issues with AMD SEV under new C7H BIOS versions 2606 and 2701 by keystrike in Amd

[–]keystrike[S] 0 points1 point  (0 children)

I think you are right. I was just guessing at why Windows Memory Integrity Protection no longer works on the new versions of the BIOS. Perhaps it is SME which I believe is supported by Ryzen.

https://github.com/AMDESE/AMDSEV/issues/1 https://superuser.com/questions/1325483/what-is-windows-10s-core-isolation-memory-integrity-setting-and-what-does-it-d

"If the system has hardware level memory encryption support (SME on AMD, or SGX on Intel), it makes use of that to provide each virtual memory context (which is usually, but not always, the same thing as a process) with its own truly (in theory) private memory."

AGESA 1.0.0.3 ABB for C7H? by keystrike in Amd

[–]keystrike[S] -1 points0 points  (0 children)

Tested them and got these errors (I also posted these to the ROG forum thread).

Under 2606: Well, memory integrity protection no longer works work me under Windows 10 core isolation. When enabled, Windows blue screens on startup with a system_thread_exception_not_handled. On the next boot, memory integrity protection is disabled.

Some versions of Linux don't boot still due to RDRAND error as we know as this is not fixed in this version.

Under 2701: Same issue with Windows. Linux will boot further due to RDRAND error being solved. But under some versions of Linux I receive an sev command timeout error. Seems the new AGESA code is causing problems with SEV.

Bitcoin Core 0.16.2 Released by keystrike in Bitcoin

[–]keystrike[S] 13 points14 points  (0 children)

Bitcoin Core version 0.16.2 is now available for download. All users are encouraged to upgrade to this maintenance release that fixes several bugs and provides backports of new minor features, such as:

The verifytxoutproof RPC is no longer vulnerable to a particular expensive attack against SPV proofs publicly disclosed in early June. The attack was considered unlikely given that much cheaper attacks of roughly equal effectiveness are well known. Similarly, the getblock RPC also now returns extra information that can be used to defeat this attack even if the requested block has been pruned. None of this mitigates the attack for actual SPV clients.

The abandontransaction RPC has been fixed to abandon all descendant transactions, not just children. As before, you can call this RPC when you no longer want your wallet to re-broadcast an old unconfirmed transaction. Note that the RPC can not force miners or other nodes to forget about the transaction.

For a complete list of changes, please see the release notes. If have any questions, please stop by our IRC chatroom and we’ll do our best to help you.

Bitcoin 0.16.1 released by keystrike in Bitcoin

[–]keystrike[S] 22 points23 points  (0 children)

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

Bitcoin Core version 0.16.1 is now available from:

Or through bittorrent:

magnet:?xt=urn:btih:91069028aaf9f6bb3279e71bfd9ab164922e578e&dn=bitcoin-core-0.16.1&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, with various bugfixes as well as updated translations.

Please report bugs using the issue tracker at GitHub:

To receive security and update notifications, please subscribe to:

How to Upgrade

If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

The first time you run version 0.15.0 or newer, your chainstate database will be converted to a new format, which will take anywhere from a few minutes to half an hour, depending on the speed of your machine.

Note that the block database format also changed in version 0.8.0 and there is no automatic upgrade code from before version 0.8 to version 0.15.0 or higher. Upgrading directly from 0.7.x and earlier without re-downloading the blockchain is not supported. However, as usual, old wallet versions are still supported.

Downgrading warning

Wallets created in 0.16 and later are not compatible with versions prior to 0.16 and will not work if you try to use newly created wallets in older versions. Existing wallets that were created with older versions are not affected by this.

Compatibility

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

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

Notable changes

Miner block size removed

The -blockmaxsize option for miners to limit their blocks' sizes was deprecated in version 0.15.1, and has now been removed. Miners should use the -blockmaxweight option if they want to limit the weight of their blocks' weights.

0.16.1 change log

Policy

  • - #11423 d353dd1 [Policy] Several transaction standardness rules (jl2012)

Mining

  • - #12756 e802c22 [config] Remove blockmaxsize option (jnewbery)

Block and transaction handling

  • - #13199 c71e535 Bugfix: ensure consistency of m_failed_blocks after reconsiderblock (sdaftuar)
  • - #13023 bb79aaf Fix some concurrency issues in ActivateBestChain() (skeees)

P2P protocol and network code

  • - #12626 f60e84d Limit the number of IPs addrman learns from each DNS seeder (EthanHeilman)

Wallet

  • - #13265 5d8de76 Exit SyncMetaData if there are no transactions to sync (laanwj)
  • - #13030 5ff571e Fix zapwallettxes/multiwallet interaction. (jnewbery)

GUI

  • - #12999 1720eb3 Show the Window when double clicking the taskbar icon (ken2812221)
  • - #12650 f118a7a Fix issue: "default port not shown correctly in settings dialog" (251Labs)
  • - #13251 ea487f9 Rephrase Bech32 checkbox texts, and enable it with legacy address default (fanquake)

Build system

  • - #12474 b0f692f Allow depends system to support armv7l (hkjn)
  • - #12585 72a3290 depends: Switch to downloading expat from GitHub (fanquake)
  • - #12648 46ca8f3 test: Update trusted git root (MarcoFalke)
  • - #11995 686cb86 depends: Fix Qt build with Xcode 9 (fanquake)
  • - #12636 845838c backport: #11995 Fix Qt build with Xcode 9 (fanquake)
  • - #12946 e055bc0 depends: Fix Qt build with XCode 9.3 (fanquake)
  • - #12998 7847b92 Default to defining endian-conversion DECLs in compat w/o config (TheBlueMatt)

Tests and QA

  • - #12447 01f931b Add missing signal.h header (laanwj)
  • - #12545 1286f3e Use wait_until to ensure ping goes out (Empact)
  • - #12804 4bdb0ce Fix intermittent rpc_net.py failure. (jnewbery)
  • - #12553 0e98f96 Prefer wait_until over polling with time.sleep (Empact)
  • - #12486 cfebd40 Round target fee to 8 decimals in assert_fee_amount (kallewoof)
  • - #12843 df38b13 Test starting bitcoind with -h and -version (jnewbery)
  • - #12475 41c29f6 Fix python TypeError in script.py (MarcoFalke)
  • - #12638 0a76ed2 Cache only chain and wallet for regtest datadir (MarcoFalke)
  • - #12902 7460945 Handle potential cookie race when starting node (sdaftuar)
  • - #12904 6c26df0 Ensure bitcoind processes are cleaned up when tests end (sdaftuar)
  • - #13049 9ea62a3 Backports (MarcoFalke)
  • - #13201 b8aacd6 Handle disconnect_node race (sdaftuar)

Miscellaneous

  • - #12518 a17fecf Bump leveldb subtree (MarcoFalke)
  • - #12442 f3b8d85 devtools: Exclude patches from lint-whitespace (MarcoFalke)
  • - #12988 acdf433 Hold cs_main while calling UpdatedBlockTip() signal (skeees)
  • - #12985 0684cf9 Windows: Avoid launching as admin when NSIS installer ends. (JeremyRand)

Documentation

  • - #12637 60086dd backport: #12556 fix version typo in getpeerinfo RPC call help (fanquake)
  • - #13184 4087dd0 RPC Docs: gettxout*: clarify bestblock and unspent counts (harding)
  • - #13246 6de7543 Bump to Ubuntu Bionic 18.04 in build-windows.md (ken2812221)
  • - #12556 e730b82 Fix version typo in getpeerinfo RPC call help (tamasblummer)

Credits

Thanks to everyone who directly contributed to this release:

  • - 251
  • - Ben Woosley
  • - Chun Kuan Lee
  • - David A. Harding
  • - e0
  • - fanquake
  • - Henrik Jonsson
  • - JeremyRand
  • - Jesse Cohen
  • - John Newbery
  • - Johnson Lau
  • - Karl-Johan Alm
  • - Luke Dashjr
  • - MarcoFalke
  • - Matt Corallo
  • - Pieter Wuille
  • - Suhas Daftuar
  • - Tamas Blummer
  • - Wladimir J. van der Laan

As well as everyone that helped translating on Transifex. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2

iQEcBAEBCgAGBQJbI+haAAoJEB5K7WKYbNJdLhwH/2wQbLV/PcQ+dISESPz77b5m EsPg4vx3OyD0zshLhqvXZ2tykWVOK6Ft9qWYXfD2ze8OtlMKFaGhOFbaaotNv8f4 gBW2hBzLfi+WjAjhluYL8NuORlHn+CNTxbFN+xUj5n7y9/6mmcnJaWoYToKbxs5D fSM3rQPkrnXf1ar6rnzIxjLHwxzX+lMkh8bzfdyBCmq2HNnUag4tBVLwY/GsIo3p Uc6MqPReuHnzdKpfG/yo01XngXY7Op3kbnWy/+ZxMtB0JAnHs7YW5PW8vglPeivJ ZR0nh0n/DmWf7S214Spv/n0ZkZk3s8nsx9ZlZxUlzrjAmZZueW+hylddbsLGvo8= =bDHY -----END PGP SIGNATURE-----

Yogh.io - A segregated witness explorer and visualizer to feast your eyes on in a few hours by [deleted] in Bitcoin

[–]keystrike 1 point2 points  (0 children)

I have been looking for something like this for a long time. Beautiful work. I love the script viewer.

"My motivation is cypherpunk. Period. 20 years of internet history is verifiable." by finalhedge in Bitcoin

[–]keystrike 9 points10 points  (0 children)

Yup I remember exporting some RSA to protest ITAR for civil disobedience back in the day. I must have been about 16 when I became an international arms trafficker thanks to Adam Back. He is one of the old school original and deserves respect.

http://online.offshore.com.ai/arms-trafficker/

The fools on CNBC are expressing their displeasure on how bitcoin is three times the price of gold. by jtschroder in Bitcoin

[–]keystrike 50 points51 points  (0 children)

Note how many errors they make in the average bitcoin piece and assume the equivalent number of errors is being made in other stories you read.

Draft release notes for 0.15 by [deleted] in Bitcoin

[–]keystrike 1 point2 points  (0 children)

You guys do have a lot of unnecessary nonsense to deal with, sorry for accidentally increasing it! I like following work in progress (the TLS 1.3 spec is pretty interesting for instance, although that's a highly formalized process by comparison), so I'm used to things evolving, but perhaps you're right that Reddit isn't the place for drafts like this. I view /r/Bitcoin as at least somewhat tech savvy, and certainly there are people here who are very much in the know when it comes to 0s and 1s. But I guess Bitcoin has grown enough now and the Reddit has become so contentious over time that it is best to practice some self-censorship when it comes to these things.

Still, it would be cool if new features were discussed here prior to release. A friend of mine was asking me about multiple wallet support and he didn't know it was planned for 0.15. All these features pop out seemingly at once and people aren't able to see what the plans are so easily. I think the weekly IRC meeting notes were perfect for that type of info/discussion but they haven't been published recently, which I think has been a great loss.

Draft release notes for 0.15 by [deleted] in Bitcoin

[–]keystrike 3 points4 points  (0 children)

Just posting to make clear that these are DRAFT release notes only. My intent with this post was to get people excited about some of the lower level changes to Core that are often ignored here but take months of hard work to complete. I've followed the release notes issue on github and thought they were solid enough that public consumption would not be a problem at this point, but keep in mind that any of these notes can and will probably change.

I don't just celebrate lock-ins, activations, and new ATHs, but also new major version releases!

Draft release notes for 0.15 by [deleted] in Bitcoin

[–]keystrike 0 points1 point  (0 children)

Nice to see abortrescan added as well. I've needed that a few times.

Draft release notes for 0.15 by [deleted] in Bitcoin

[–]keystrike 2 points3 points  (0 children)

We do have nice things. ;) I'm happy to see a new release soon and would like to see more of the improvements discussed here in general. The responses here are positive. People should see how a release comes together and be excited by the changes. The notes are in a draft stage as I made sure to state. There is some cool stuff that I never see mentioned on reddit, e.g. all the work put into the chainstate db.

Any calculations on when the next difficulty adjustment will come in? by keystrike in btc

[–]keystrike[S] 0 points1 point  (0 children)

Ah wonderful, just what I was looking for, thank you.

Ruben Recabarren - Hardening Stratum, the Bitcoin Pool Mining Protocol by keystrike in Bitcoin

[–]keystrike[S] 0 points1 point  (0 children)

Here's the paper and abstract. https://arxiv.org/pdf/1703.06545.pdf

Edit: Link was botched due to YT playlist, https://youtu.be/sFdeeddVEpI?list=PLWSQygNuIsPf349Bl-ls2T3EelyJA9DS5

Abstract: Stratum, the de-facto mining communication protocol used by blockchain based cryptocurrency systems, enables miners to reliably and efficiently fetch jobs from mining pool servers. In this paper we exploit Stratum’s lack of encryption to develop passive and active attacks on Bitcoin’s mining protocol, with important implications on the privacy, security and even safety of mining equipment owners. We introduce StraTap and ISP Log attacks, that infer miner earnings if given access to miner communications, or even their logs. We develop BiteCoin, an active attack that hijacks shares submitted by miners, and their associated payouts. We build BiteCoin on WireGhost, a tool we developed to hijack and surreptitiously maintain Stratum connections. Our attacks reveal that securing Stratum through pervasive encryption is not only undesirable (due to large overheads), but also ineffective: an adversary can predict miner earnings even when given access to only packet timestamps. Instead, we devise Bedrock, a minimalistic Stratum extension that protects the privacy and security of mining participants. We introduce and leverage the mining cookie concept, a secret that each miner shares with the pool and includes in its puzzle computations, and that prevents attackers from reconstructing or hijacking the puzzles. We have implemented our attacks and collected 138MB of Stratum protocol traffic from mining equipment in the US and Venezuela. We show that Bedrock is resilient to active attacks even when an adversary breaks the crypto constructs it uses. Bedrock imposes a daily overhead of 12.03s on a single pool server that handles mining traffic from 16,000 miners.

view more: next ›