• 13 Posts
  • 87 Comments
Joined 1 year ago
cake
Cake day: January 8th, 2024

help-circle






  • Well, it really depends on if you want somebody to trust or not. If you don’t want to trust anybody except yourself, then you can just use Tofu and be good with it. The only reason I brought up using search engines as an index is just to give people a place to look.

    If I want to visit CNBC and I’ve never visited them before, I could just go straight to CNBC and trust their certificate right away. Or, if I wanted to confirm that the CNBC certificate was likely valid, I could ask DuckDuckGo, Google, and Quant. And if they all agreed that they had the same certificate that I was getting, I’d be more likely to think that it’s valid.



  • Tofu stands for Trust on First Use. So basically, you would get an SSL certificate from the website the very first time you connected to it, instead of trusting a certificate authority. Then, if the SSL certificate changed, you would then be warned that the certificate had changed and would have to decide whether to trust the new certificate or not trust the new certificate. That’s why I said perhaps search engines could index certificates and tell you how long the certificate has been active and you could check several engines quickly to determine whether each engine has the same certificate indexed for the same website and if they did not then you would know something might be up.



  • But i2p doesnt have PoW DDOS protection. Trust me, that shit helps a fuckton for limiting ddos. I witnessed firsthand nine onion services that upgraded from not having DDOS protection to having DDOS protection while under attack and the attack completely stopped.

    Edit: RetoSwap, a decentralized Monero exchange, has 9 onion seed nodes and they were being DDOSed to oblivion. As soon as they added PoW the attacks stopped and havent happened since. That was about 9 months ago now.


  • As far as Let’s Encrypt goes, the easy way to solve that is self-signed SSL certificates and Tofu. Just make it stupid obvious if an SSL certificate changes on a site that you go to. Like, turn your browser into a giant red screen that says that the security of the website has changed and may be broken obvious. Maybe you could have search engines also index SSL certificates so you could see if Google and Bing and DuckDuckGo and whoever else all say that this website has the same SSL certificate that it has had for X amount of time and if the search engines start showing different results you get suspicious.

    Edit: Using self-signed certificates and tofu fits better with the decentralized ethos of the original web anyway since you’re not relying on some third-party authority to tell you what’s safe and what’s not.




  • To get the last week view, tap the router short name, tap more details, and then tap device metrics log, then tap 1w. It will give you the device metrics for the past week and then you can add all the channel utilization numbers together and divide by the number of reports you have. As I mentioned before, the routers in my area report every 12 hours and so over a week there are 14 logs so I have to add all the channel utilization numbers up and then divide by 14.