pbear2k21

13 ms·

1.
by pbear2k21 4y ago
you may be correct. the issue has been closed for further review. a scaled attack might only prevent new nodes from entering the network as existing connections would be spared even when the maximum limit of peers is reached. however - and
2.
by pbear2k21 4y ago
i don't guard my reputation. this isn't 48 laws of power. i'd never become a blockchain socialite to the extent of social climbing to become blockstream's cto. i answer to no one and don't try to mold how others per
3.
by pbear2k21 4y ago
>Do your homework! You're not the first person who ever thought of attacking a bitcoin node. While I'm sure there are areas for improvement, you're not likely to be able to make useful suggestions from a position of almost
4.
by pbear2k21 4y ago
i've popped 25 - 30+ blockchains. from anecdotal experience i suspect that there could be something here and need to see it through with a sync'd node and more firepower. you seem overconfident.
5.
by pbear2k21 4y ago
inaccessible to external machines that are not participating in the attack. it's yet to be seen what happens to a node that's sync'd with active peers and whether a node under attack is kicked out of the network for timeouts
6.
by pbear2k21 4y ago
i considered this and needed clarification. i didn't know whether the p2p connections remained open or made frequent disconnect/reconnects. what happens to sync'd nodes with active peers is yet to be seen. it's too early
7.
by pbear2k21 4y ago
node operators can implement their own throttling - sure - but how many bitcoin node operators are doing that to deflect a p2p ddos attack? even if some are, most aren't - and finality in the network could potentially suffer as a resul
8.
by pbear2k21 4y ago
bitcoind not having ip associated throttling edit: BUILT IN* is questionable. this attack shouldn't work on out-of-the-box installs of bitcoin. as i mentioned earlier - there is no rationale behind a single machine making 1k handshake
9.
by pbear2k21 4y ago
it is
10.
by pbear2k21 4y ago
50k sockets looping requests make the p2p port entirely inaccessible at times. with more attacking machines it is reasonable to suspect that the target node(s) could be held down in perpetuity. edit: re: child comment / syn flood; sure
11.
by pbear2k21 4y ago
yes - testing his own node. that is how pen testing blockchain nodes works. from there you can make projections of scaled attacks. it's not an rpc port - and the computer in the screen shot using telnet is an external machine that isn&
12.
New Bitcoin DDoS Technique(github.com)
49 points by pbear2k21 4y ago|35 comments
13.
Martin Shkreli just released a crypto for drug discovery(apnews.com)
4 points by pbear2k21 4y ago|2 comments
14.
Bypassing Google search rate limits and captcha(g.livejournal.com)
2 points by pbear2k21 4y ago|0 comments
15.
“Toxic Hackers” Argue About C(youtube.com)
1 points by pbear2k21 4y ago|0 comments
16.
Connecting to AOL 3.0 in 2022 [video](youtube.com)
1 points by pbear2k21 4y ago|0 comments
17.
Using AOL 3.0 in 2022(g.livejournal.com)
1 points by pbear2k21 4y ago|0 comments
18.
by pbear2k21 4y ago
Oops - The title was meant to say 2007. However GoDaddy still suffers from social engineering attacks, e.g. https://www.zdnet.com/article/godaddy-staff-fall-prey-to-soc...
19.
Social engineering GoDaddy (2021)(g.livejournal.com)
76 points by pbear2k21 4y ago|17 comments
20.
Reversing AOL 3.0 (1996) – A Deeper Dive(g.livejournal.com)
3 points by pbear2k21 4y ago|0 comments
21.
by pbear2k21 4y ago
No it isn't? That was RE'd in Python - this was a RE of an RE in TempleOS. Plead read before commenting.
22.
AOL 3.0 Reverse Engineered in TempleOS(g.livejournal.com)
3 points by pbear2k21 4y ago|1 comments
23.
AOL Keyword Hacks (1990s – 2001)(g.livejournal.com)
1 points by pbear2k21 4y ago|0 comments
24.
by pbear2k21 4y ago
That's planned. Would be blasphemy not to.
25.
by pbear2k21 4y ago
Yes. That was done with an internal test build.
26.
by pbear2k21 4y ago
Yeah livejournal is pretty bad. I only use it because of the 1 character username "g" I cracked 20+ years ago. It's an ad trap.
27.
by pbear2k21 4y ago
If anyone wants to check it out or take a deeper technical dive our discord is https://discord.gg/reaol
28.
AOL 3.0 reverse engineered(g.livejournal.com)
294 points by pbear2k21 4y ago|130 comments
29.
by pbear2k21 5y ago
dear admins, this guy is baiting me dear readers, that is what gaslighting looks like this guy wasn't even around yet when whaops was hacked by dime. that's how new he is. i've been chatting with dime and he confirmed his fri
30.
by pbear2k21 5y ago
Disclaimer: The person I am replying to is an unhinged, imaginative drug addict and confidence man. He crafted his post to look like he didn't already know I wrote the blog post. Let's clarify everything since you are a liar. &gt

More ›