• 1 Post
  • 59 Comments
Joined 23 days ago
cake
Cake day: June 9th, 2024

help-circle
  • That’s a fair assessment. I’ll admit to having a severe case of doomerism when it comes to tech lately, and the levels of shit tech bros will go to to monetize shit has me skeptical there’s any sort of protocol or technology that could be made bro-resistant for more than a short period of time.

    EEE is pretty prevalent and has been a very standard practice with these tech companies for a long time. See: Meta and Threads for a recent example.











  • I think it’s less that it’s “impossible” but rather that it’s expensive.

    Honestly we’ve in general shoved too much shit into the browser that’s not strictly related to just browsing web sites.

    And you “have to” support all the layers and layers and layers of added stuff, or you can’t “compete”.

    But, at the same time, the goals of making a good-enough browser that mostly works and isn’t completely enshittified and captured by corpo big tech interests is a very worthy project and 100% support what they’re doing.






  • Nope, that curl command says ‘connect to the public ip of the server, and ask for this specific site by name, and ignore SSL errors’.

    So it’ll make a request to the public IP for any site configured with that server name even if the DNS resolution for that name isn’t a public IP, and ignore the SSL error that happens when you try to do that.

    If there’s a private site configured with that name on nginx and it’s configured without any ACLs, nginx will happily return the content of whatever is at the server name requested.

    Like I said, it’s certainly an edge case that requires you to have knowledge of your target, but at the same time, how many people will just name their, as an example, vaultwarden install as vaultwarden.private.domain.com?

    You could write a script that’ll recon through various permuatations of high-value targets and have it make a couple hundred curl attempts to come up with a nice clean list of reconned and possibly vulnerable targets.




  • That’s the gotcha that can bite you: if you’re sharing internal and external sites via a split horizon nginx config, and it’s accessible over the public internet, then the actual IP defined in DNS doesn’t actually matter.

    If the attacker can determine that secret.local.mydomain.com is a valid server name, they can request it from nginx even if it’s got internal-only dns by including the header of that domain in their request, as an example, in curl like thus:

    curl --header 'Host: secret.local.mydomain.com' https://your.public.ip.here -k

    Admittedly this requires some recon which means 99.999% of attackers are never even going to get remotely close to doing this, but it’s an edge case that’s easy to work against by ACLs, and you probably should when doing split horizon configurations.