Pages:
Author

Topic: This message was too old and has been purged (Read 9279 times)

legendary
Activity: 1512
Merit: 1012
Was this bug (if it was a bug) fixed in 0.10.1?

EDIT: apparently yes https://bitcointalksearch.org/topic/bitcoin-core-0101-has-been-released-1039713
sr. member
Activity: 311
Merit: 250
Graphics Design Guru
I third that notion, would very much like to see the outcome of this whole situation.
legendary
Activity: 1512
Merit: 1012
I'm also curious about the outcome on this. I see OP doesn't have negative trust anymore, so this bug was most likely real and important.
sr. member
Activity: 329
Merit: 250
Bump.

Was this really a DoS bug in the client?  Did it get fixed?
legendary
Activity: 1628
Merit: 1012
February 20, 2015, 04:16:37 PM
#96
Lighthouse approved the posting this afternoon, so fundraising should be possible.

Wow, you guys are such a great community. Do you have a link to the project file?

Evil

The file is on my desktop - the link it created is a few posts up. I'm away from my computer but as soon as I get back I will post the link to it.

Should be about an hour or so.

EDIT:

https://vinumeris.com/_lighthouse/crowdfund/project/bug-bounty-requested-10-btc-for-dos-bug-in-current-clients
legendary
Activity: 1260
Merit: 1168
February 20, 2015, 03:50:17 PM
#95
This message was too old and has been purged
legendary
Activity: 1628
Merit: 1012
February 20, 2015, 03:20:57 PM
#94
Lighthouse approved the posting this afternoon, so fundraising should be possible.
hero member
Activity: 714
Merit: 500
February 20, 2015, 02:09:06 PM
#93
Has he received any bounty for discovering this bug? If the reply is yes, how much he has received?
legendary
Activity: 1470
Merit: 1004
February 20, 2015, 12:28:20 PM
#92
Doesn't look like it's the DOS bug but here is gmaxwell crediting Evil with finding a bug https://github.com/bitcoin/bitcoin/pull/5770

This is a completely different topic, but thanks to Gmaxwell for the credits. I really appreciate that.

I would assume their silence means they are actively working on a solution.  Great to see these bugs addressed and credited in the proper way.  Smiley
legendary
Activity: 1260
Merit: 1168
February 20, 2015, 05:31:41 AM
#91
This message was too old and has been purged
hero member
Activity: 764
Merit: 500
I'm a cynic, I'm a quaint
February 20, 2015, 04:45:18 AM
#90
Doesn't look like it's the DOS bug but here is gmaxwell crediting Evil with finding a bug https://github.com/bitcoin/bitcoin/pull/5770

Actually being able to get a third party to process control characters would be a vector for some shenanigans. Nice catch by Evil Knievel there.

Thanks for linking to that pull request.
legendary
Activity: 2087
Merit: 1015
February 20, 2015, 03:39:38 AM
#89
Doesn't look like it's the DOS bug but here is gmaxwell crediting Evil with finding a bug https://github.com/bitcoin/bitcoin/pull/5770
hero member
Activity: 764
Merit: 500
I'm a cynic, I'm a quaint
February 19, 2015, 07:52:06 PM
#88
The silence is becoming slightly awkward. It seems that there is indeed an issue. Is this issue being addressed at the moment? Is there a discussion about it elsewhere that I'm not aware of?

What gives?
hero member
Activity: 910
Merit: 1003
February 19, 2015, 05:54:45 PM
#87
Do we have six confirmations yet?  Wink
copper member
Activity: 2926
Merit: 2348
February 17, 2015, 08:44:37 PM
#85
EvilKnievel has a negative rep for a similar thing from gmaxwell back in 2014. Not sure if he would take him seriously on this now.

Please check again.
Evil-Knievel, I wanted to follow up with you. I previously said that I thought you were lying about this exploit, however you were able to show a "real world" demonstration with redsn0w's full node (with his permission) and it appears the gamaxwell has evaluated your claim and apparently your claim checked out
legendary
Activity: 1260
Merit: 1168
February 17, 2015, 07:56:38 PM
#84
This message was too old and has been purged
hero member
Activity: 574
Merit: 500
February 17, 2015, 07:16:27 PM
#83
Just for the record: The bitcoind node, that redsn0w has set up on a VPS Server was shotdown within less than 10 seconds; the bitcoind node consumed so much CPU and memory that the entire server stopped working. Even a login via SSH was not possible anymore.

I can "confirm" but it was only a small droplet with the basic specifics. These were the ghraps:





I don't know what he did, I've suggested him to try with other linux machine (not vps) and maybe someone here can help him.

How do you explain this? ^
full member
Activity: 154
Merit: 100
February 17, 2015, 07:13:44 PM
#82
No comments from @gmaxwell yet?

Doesn't look like it

Maybe he is busy and he can't reply I do not know. Is this bug real or not ? Because now a lot of people (various nodes) have updated their client.

EvilKnievel has a negative rep for a similar thing from gmaxwell back in 2014. Not sure if he would take him seriously on this now.
hero member
Activity: 714
Merit: 500
February 17, 2015, 07:11:31 PM
#81
No comments from @gmaxwell yet?

Doesn't look like it

Maybe he is busy and he can't reply I do not know. Is this bug real or not ? Because now a lot of people (various nodes) have updated their client.
Pages:
Jump to: