loathsome dongeater

he/him

a cool (brr) dude

  • 440 Posts
  • 5.15K Comments
Joined 6 years ago
cake
Cake day: May 14th, 2020

help-circle




  • What I am praying for is that some new renegade Chinese brand swoops in and save photography as a hobby with new and exciting entry-level DSLRs or mirrorless cameras that are reasonably priced. Phone photography improving technologically and brands like Canon, Nikon catering only to rich people has really harmed the mass access to photography as a hobby. I still have the Nikon D3100 I bought about a decade ago and the current cheapest Nikon camera I can find on Amazon right now is twice the price.


  • This is normal because your body will need to first adjust to functioning without alcohol in the system. I’m no expert in the sense that I’ve not researched the problem extensively. But I stopped drinking after a couple years of a quart+ per night. It took a month for the withdrawals to become manageable but I was able to sleep afterwards.





  • I’ll assume you know DNS resolution, which turns a URL like hexbear.net into an IP address. You try to go to hexbear dot net from your browser. But someone has set up a man-in-the-middle-attack. So when your browser tries to resolve the URL into an IP address, instead of the actual IP address you get a different one which could be hosting malware. TLS certificates help the browser (and other clients apart from browsers) make sure that the IP address is the authentic one.

    Certificate Authorities have a process to confirm the real IP address of a domain name. Once they confirm it, they issue certificates which you can then serve to whoever is whoever is trying to visit your URL. If I am a malicious man-in-the-middle attacker, you can assume that I cannot get a certificate authority to give me certificates. This is because I don’t own and control the domain name. You do.

    Certificate authorities use cryptographic fuckery to sign certificates. They use their private keys to sign these certificates. Clients (like browsers) making web requests have their ways of knowing which legitimate certificate authorities exist and what their public keys are. So if a website serves you a certificate, your client will be able to verify that it is authentic.

    But if the private signing key of a legitimate certificate authority is known, this security model falls apart. Because anyone can create a legitimate certificate. So if I am a man-in-the-middle attacker, I can serve forged certificates and your browser will never be able to tell because they look authentic to it.