pbear2k23

7 ms·

1.
Ethereum Devs Unable to Patch Exploits(twitter.com)
1 points by pbear2k23 2y ago|0 comments
2.
by pbear2k23 2y ago
tl;dr https://pastebin.com/raw/qr8XWFkR - you f*cking ping faster than it pongs. this wasn't discovered until recently. sad. i put this together. it also contains a mode for CVE-2023-33297 ('headers') wh
3.
Zero-day Bitcoin OOM crash(pastebin.com)
2 points by pbear2k23 2y ago|1 comments
4.
Bithop spiders the btc mainnet (new, open source)(github.com)
1 points by pbear2k23 2y ago|0 comments
5.
MD5 Blockchain
5 points by pbear2k23 3y ago|0 comments
6.
by pbear2k23 3y ago
that's... not at all a solution. "just use onfido" doesn't solve deepfakes. too much friction isn't true whatsoever it would just take some solid coders. and finally i don't suggest that anyone work with onfido
7.
by pbear2k23 3y ago
i came up with this. it has a lot of moving parts but it's viable. i understand the idea of "why not just publish transcripts in advance on whitehouse.gov" and the answer is because there are too many points of failure, like
8.
New Anti-Deepfake Strategy(twitter.com)
6 points by pbear2k23 3y ago|4 comments
9.
by pbear2k23 3y ago
this is being privately disclosed - but i found it and attest to its authenticity. i'm happy to answer some, but not all, technical questions.
10.
0day Bitcoin P2P Crash (OOM)(twitter.com)
2 points by pbear2k23 3y ago|2 comments
11.
Bitcoin SV Remote Crash(twitter.com)
2 points by pbear2k23 3y ago|0 comments
12.
by pbear2k23 3y ago
if for instance the attack program was routed through tor i don't see why it wouldn't work at damaging capacity with a modified script
13.
New Bitcoin DoS Exploit Code(twitter.com)
3 points by pbear2k23 3y ago|2 comments
14.
by pbear2k23 3y ago
Updated X link https://x.com/123456/status/1736023700057608352
15.
"Patched" Bitcoin DoS Still Vulnerable(twitter.com)
1 points by pbear2k23 3y ago|3 comments
16.
Bitcoin Security Advisory(twitter.com)
1 points by pbear2k23 3y ago|0 comments
17.
When an AOL Coder Sold the Whole Database(g.livejournal.com)
2 points by pbear2k23 3y ago|0 comments
18.
by pbear2k23 3y ago
>right, because so many people are typing in the incorrectly shortened URL instead of clicking on the link it was clickable - and yes they dodged a bullet. the channel could have been perfectly reproduced, made to look real, and then use
19.
by pbear2k23 3y ago
was me if anyone wants details - but it's pretty simple. not a hack. registered an available username so that opposition ic groups couldn't do the same - they could have dressed it up in a visually identical way and intercepted we
20.
CIA's Telegram Hijacked(bbc.com)
43 points by pbear2k23 3y ago|5 comments
21.
by pbear2k23 3y ago
so you didn't read it but are sharing meta-feedback?
22.
by pbear2k23 3y ago
i discovered the issue if anyone would like for me to unpack anything. content snippet + attack code: the takeaway from pad vs bitcoin is that a botnet can remotely charge public listening node operators thousands of dollars. that would sno
23.
Active Critical Bitcoin Exploit: A Financial Attack Swept Under the Rug(twitter.com)
2 points by pbear2k23 3y ago|1 comments
24.
Doxing Has Become Spooky(g.livejournal.com)
2 points by pbear2k23 3y ago|3 comments
25.
The Origins of Doxing(twitter.com)
1 points by pbear2k23 3y ago|0 comments
26.
Edit: Tweet removed, delete me(twitter.com)
1 points by pbear2k23 3y ago|0 comments
27.
by pbear2k23 3y ago
don't mind me - nonchalantly taking credit for various nonsense i did as a kid. way past the statue of limitations - and hopefully found interesting to someone
28.
Tumblr Phishing Attack (2011)(twitter.com)
1 points by pbear2k23 3y ago|1 comments
29.
by pbear2k23 3y ago
> Taking over AOL “int” accounts was actually considered pretty basic at that time. to the skillful it was considered basic - for sure. there was a lot of collaborative intelligence in the aol "hacking" scene, though. and you c
30.
Phishing 2FA 25 years ago(twitter.com)
44 points by pbear2k23 3y ago|14 comments

More ›