Quote from: AGD on May 10, 2016, 05:21:01 AM

Quote from: SebastianJu on May 09, 2016, 09:38:39 PM

Quote from: BlueTemplar on May 09, 2016, 09:26:51 PM

Well, in their view it is not a big enough threat to attack and spend millions on gaining a majority of the hashing power. Once it is determined to be a threat it will be too large for them to buy their way in to control. Plus the second they gain control is when all of the money floods out of Bitcoin and in to a different crypto. That is the beauty of it, we are not forced in to using the currency so attacking it results in wasted money as the users move out of Bitcoin and in to a different crypto-currency.

The agencies would have an interest to make bitcoin big. They can use it for their own operations if needed and they can follow the trail of the money. Since everyone know that, for example the nsa, controls the internet traffic of whole countries. So it would be not really hard to fight terrorism and similar things like that.

Well, pushing in bad code that is not found might be another nice gimmick but so far I think it was not successfull. Too many observe things closely.

The idea of inserting "bad code" under the eyes of everyone is not new:

Quote from: AGD on August 21, 2015, 01:54:16 PM

+1 because thanks to Gavn, we have a scenario, where exacty this reverse exploit could be implemented. Please core devs: Don't let it happen!

http://blogs.msdn.com/b/vcblog/archive/2014/02/04/challenge-vulnerable-code.aspx
http://www.underhanded-c.org/_p_26.html

Quote

This challenge appeared on an internal alias dedicated to C++. It was issued by Mike Vine, a developer here at Microsoft who agreed to let us share it with the mighty Visual C++ blog readers:

This challenge came from me thinking about a simple bug which could be turned into a security vulnerability, so I thought Id give it a go and try to code a plausibly deniable piece of code which looks innocent but is actually dangerous. I managed to actually go further than that, and produced something, that whilst unlikely, could possibly have come from non-malicious but sloppy coding.

So your challenge is if you choose to accept it analyze the sample code file main.c (attached) and try to find the (fairly obvious) security faux pas and accidental bug which causes the security faux pas to be exploitable.

Quote

The 7th Underhanded C Contest is now open.

The goal of the contest is to write code that is as readable, clear, innocent and straightforward as possible, and yet it must fail to perform at its apparent function. To be more specific, it should do something subtly evil. Every year, we will propose a challenge to coders to solve a simple data processing problem, but with covert malicious behavior. Examples include miscounting votes, shaving money from financial transactions, or leaking information to an eavesdropper. The main goal, however, is to write source code that easily passes visual inspection by other programmers.

Your posts and questions you pose to the community here are invaluable and hope to see more in the future. Unless if you are me, are you me? Then I guess I would need to post...Or are you Satoshi?

Wink

anyways thank you for finding my post and commenting, good to know old-timers are paying attention in the forums.
(re my post: "Hacks Puppets and Forks: How to destory bitcoin") https://bitcointalk.org/index.php?topic=1834310.0