Dread Now Has an i2p Mirror (DDoS Update)
Dread is now accessible over i2p.
After a period of downtime, Paris—one of the administrators of Dread—published the hostname of Dread’s i2p mirror.
In the announcement post for the March 2022 Dread update (Dread V3), Paris promised an i2p mirror for Dread. The eepsite launch was apparently delayed due to stability issues:
“A new i2p endpoint is online and flood-filling but it hasn’t been as stable as I need it to be. I’ll be holding off posting the address till such time (probably within a couple of days). I can get it more stable for an average user to visit if you want to both prepare and help this process along install i2pd and running it. This network needs to 2X its size with a shit ton more nodes which have ipv6. I’m doing what I can to get it up, but the reach-ability of the address is poor, and connections are unstable. It is better than when I have tried before but more work needs to be done on this. It is far more resistant against DDOS attacks though, and with enough noise Sybil attacks become basically impossible to conduct on anything other than an extremely targeted attack.”
Paris wrote that “someone doesn’t want [Dread] online” on April 12, 2022. The post referenced a distributed denial-of-service attack that rendered Dread inaccessible. As one of the largest and most well-known onion services with a western userbase, the downtime did not go unnoticed. Infosec Twitter users suggested that law enforcement had sponsored the attacks (the FBI once paid CMU to conduct a traffic confirmation attack and a Sybil attack during an investigation into marketplaces).
Darknetlive’s peanut gallery claimed that “asap siezed [sic], dread siezed [sic], abacus siezed [sic]” or, “Dread, cryptostamps, and ASAP were all seized.” Dread, cryptostamps, ASAP, and Abacus are online without apparent seizure signs. Dread’s onion service is only intermittently working though. The commenters apparently have access to secret evidence.
Paris, “Someone doesn’t want us up. April 11 DDOS attack. I2P mirror online?” (signed copy below this post).
And here I was going to just relax a bit, work on the recon update, and not worry too much. BUT NO. We can’t have nice things.
I have been delaying the i2p endpoint announcement simply because my reliability with the i2p network has been… terrible is one word I’ll use. It might because how I’m personally connecting into the i2p network or because of how the i2p network system is designed for dread (layers of i2p nodes to the core). I was figuring it out and also gathering information about how the i2p network handles different things. There is a chicken and an egg problem here with i2p. They need more people using their network. It is, from what I got from the IPs and bandwidth statistics on the distributed floodfill nodes, far smaller and far less resistant to Sybil attacks. They don’t try to hide that fact (in their fantastic documentation) but it is still a problem. With scale there is a lot of promise here with the proper supports.
Dread will NEVER use any addressbook which can transparently MiTM attack you. It is very important to only visit using the base32 hostname. With that being said I’m going forward with the announcement to provide a hopefully more stable as time goes on i2p mirror.
This is Paris from Dread. As promised we now have an i2p mirror:
http://dreadtoobigdsrxg4yfspcyjr3k6675vftyco5pyb7wg4pr4dwjq.b32.i2p
It is the biggest dicked i2p website yet. Guaranteed.
There are people who leave helpful comments on Darknetlive articles, though. One user posted a reminder that HugBunter has been missing for two months. HugBunter’s last comment on Dread was on February 20, 2022—54 days from the time of writing. Additionally, HugBunter’s warrant canary is out of date by 15 days at the time of writing (the canary update was “scheduled for Thursday, March 31, 2022”). This is not the first time HugBunter has let a canary expire.
Paris has a current canary as of April 15, 2022. The canary is due for an update by today (April 15, 2022), but Paris and HugBunter often operate on Dread time (Gregorian date ± three days). Busy onion service operators regularly miss their self-imposed deadline by a day or two.
A sign in a library in Craftsbury, Vermont in 2005 | Jessamyn West
There are certainly some weird things happening behind the scenes.
Paris: i2p mirror
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
And here I was going to just relax a bit, work on the recon update, and not worry too much. BUT NO. We can't have nice things.
I have been delaying the i2p endpoint announcement simply because my reliability with the i2p network has been... terrible is one word I'll use. It might because how I'm personally connecting into the i2p network or because of how the i2p network system is designed for dread (layers of i2p nodes to the core). I was figuring it out and also gathering information about how the i2p network handles different things. There is a chicken and an egg problem here with i2p. They need more people using their network. It is, from what I got from the IPs and bandwidth statistics on the distributed floodfill nodes, far smaller and far less resistant to Sybil attacks. They don't try to hide that fact (in their fantastic documentation) but it is still a problem. With scale there is a lot of promise here with the proper supports.
Dread will NEVER use any addressbook which can transparently MiTM attack you. It is very important to only visit using the base32 hostname. With that being said I'm going forward with the announcement to provide a hopefully more stable as time goes on i2p mirror.
This is Paris from Dread. As promised we now have an i2p mirror:
http://dreadtoobigdsrxg4yfspcyjr3k6675vftyco5pyb7wg4pr4dwjq.b32.i2p
It is the biggest dicked i2p website yet. Guaranteed.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEbfleES3oPdbct1q5DE1JcU+sN9gFAmJU3NQACgkQDE1JcU+s
N9iFcw//R+h7ppmmvpjLh90qOdRmzTxC4x5SjXSThBN3Am/+AWY8XJX+tJ1wSlMj
KxzsOWyfZ/Tr4sOBvvSNK975oMvN4WlxEmYg0cd5Nvz1z/Q0sS3uYQrwociuS4Vk
LspqyL3N+wiTwySwGci2JxzQexPbt9sEIDo9haIFbsVHXsVMD4ZpsvmgGddl07UJ
QxF7YmVshnImNcw4eYVUNtCim+586ldJPYyGdciBUgRRbGLZE0JTTQ3LcGZ3Wk2w
YDXcQ1D6DaYmRHFnntxS2G3Q4TSG+KuJwak7ZAbC31fU2QrG+EmT3KRjhw7jpPDR
Hieyib/2tjwNcpfnigvWdJIN3AW4JMtW9Q/DKtZt3oBeZtBdirInUZadRpsMitCy
dpsYoftAnDW96UC13uTH+RQWVUAtJcuByuCOaJWRrxeD/cQdbYwAf7EtGEVED6HR
vnkicwaJCWGtd5fN8jYUhIA0a93qEcujJnQcvYlJjvXUvdeKNO4BXnOlsqg20WSd
iBVdFQfdVr3lX/+UjkmS9/ZmsDELiNDg/iCGGg4SWgWQC+dNcldRqSp3fZw4R6v5
yk3hfdBMRCNcyPsUVYflSt+aBD+46G6nN5FRfi8Lw/CTdmVgveR+lk+gSdJ5P1+k
OlgM3ppCwjA7wp9vsfam5jgnUz7b6mhtPhnp0kQ+zyC7R3QdKDg=
=FxQf
-----END PGP SIGNATURE-----
Canary: Paris
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I, Paris am alive and free as of April 1st 2022 and in full control of Dread, Recon and all other services related to our network.
Next canary update is scheduled for April 15th 2022
Hug is alive. Two new platforms coming soon.
Main Dread URL: http://dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion
Main Recon URL: http://recon222tttn4ob7ujdhbn3s4gjre7netv14zybuvbq2bcqwltkiqinhad.onion/
Bitcoin Height: 000000000000000000077d011569f26c0ebb6deaad63a7fbbbf256badc61bbf6
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEbfleES3oPdbct1q5DE1JcU+sN9gFAmJHSJgACgkQDE1JcU+s
N9gUoBAA4amh+dk7tcLyFNxXNvFduluhR2mJWH/HVLFBXOziq+2CmY19kjuZVU4d
3UmOlDa5C9/XwKKF2dH+yrMPINhpXozL4HTsm9Lqan8LF0ATGScCuqpwAUUx+bww
btPBwyRLRsFSt97XCBMLgeiL9Q+TMAzoNjohM1hVD/fYQeQP2EuCpClA/tSqtN0T
7DQxJFb6GbYToK08trv7nu3TvQX6GwiZTSc9vHNZxSghKtm6/Y63AoCdsdc2BjrP
BWZOwkLPxoU3924O6GzWJZhEO3xXmOuRCfppAuvi5fq4kxJeXd/V7ahWa67nQMOP
Kom8IjxK99a1QeIkHBsUMKWt9vs0ryXBaD5+IT9OExUyd30xkhM+rFO8TbH4K+kR
Jn4BnFfmssNE+n1ZlzAc9ALtEcNjOxG1S7PFdUgEqzJdTBiZ9WbrVdZB5iY6Xs7u
Ewr4A+kHtDze3OuRVyA8FIM1IM9k9O3fesYUL9llUicMMZfuf6WFo5gqh+uA16MH
XL4c0JWQygqt7s0YhAI8UHEBqDxvFvvHUnrBLj4h66HCtvioWU0gmI0/EWHJGbGg
xB4+UAdkT1Q+0UhMoVOKjiAkrSmhWEgol2QDWERZDG2iOclnp2V4POXWSgPoUESj
HHL5erO8kXiJCs8QGMK1yDwnf23I6InP09SC0C4N1V/Injn32Hc=
=gk3y
-----END PGP SIGNATURE-----
Canary: HugBunter
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I, HugBunter am alive and free as of Tuesday, March 22nd 2022 and in full control of Dread, Recon and all other services related to our network.
Next canary update is scheduled for Thursday, March 31st 2022
0000000000000000000561de6ffa1624cabb82d101c8cea16ffb0079496b8fe8
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEYTOs4fS4fFHb8/6l6GEFEPmm6SIFAmI5rIkACgkQ6GEFEPmm
6SLORRAAg130ufd3X1//RUGK+v9m/kxUieaLCSE5A6xjcuapWsfhOJVKH5AOH03q
VZCf4e79i8U4WphpfHMdM81x+zvtxZh0Q+OgumEC9rQXmHeRUZI/mIsdo3Yq3cHE
H9ljQLKlam+WVadW4mbSWLb0Bu7KJhtnt0530zClzgPQPpOo9wNmT1rSYGXHTySn
55WCmzsEWL4CSGKhqclDnIAaK8mvKEgs0rRK/XauiBBrn9PfzJU8Ldxne01tpLMa
NNyWiTV6WG9rNHNkqeM18cFQF4mCApYEQCY9C7qh59EgkWt2dTtlZZmmzNcYXPwH
UskEog5/NAhFUuOhO+r2rOOqGi7zp+tJ+TAPG0H9uPJwr8ZcArBAJ1wZV/ub7v08
jTCgMi5wSGy2gJjzvhk437JdD1WfNHLkA0SJPxs8VtyUVifR0lwqn4uCMrusY8fi
XTtkaa3lcd3zMaDfj0CSBHSs9MAnB2JKMGYw0lVrWIriI/xFf/SPnP1LMalkWKZu
NzGkHz/BWprCgk3VHkox8XhCou/gXK7AlAQNNmYS5qS0OGwFqWN04e7Gyen5yz/R
s5NsCI5KGgDCkxTFjEuvGS/ZH5IxoIpM2Oa7mv3eHp1jkFjcbEQU921lh/ZDmhs7
7imrhZYV5HfBqeVol4EgiHaSUFpT+DO195sm+h3ndf+rP1+eeDw=
=fs3t
-----END PGP SIGNATURE-----
CannaHome next?