• 1 Post
  • 57 Comments
Joined 8 months ago
cake
Cake day: June 9th, 2024

help-circle




  • I wouldn’t argue with the dude; he’s got a clear case of bad-faith-itis. What you did was bad, so you shouldn’t have done it, but no I won’t tell you how to fix it.

    The absolute best you could have done is cross-posted to a Mastodon/Bluesky/whatever account as well, but you can’t just always go around yanking the rug out underneath communities especially if you’re in a position where it’s not just lazy shitposting and worthless commentary.

    …that said, you have moved anything you can to being posted somewhere in tandem riiiiiiight?







  • As someone with recent platforms from both Intel and AMD, man, I do not like my 7700x’s platform.

    It’s just sporadically unreliable: sometimes it posts, sometimes it doesn’t, sometimes the memory decides it needs to reset back to jedc standards instead of the expo settings, sometimes it doesn’t. Even a successful POST can take upwards of a minute sometimes, and the system may or may not reset in the middle of it, resulting in two extended delays.

    Perfectly stable once the OS gets booted (memtest is fine, prime95 is fine and it boosts like crazy up to about 5.5ghz all-core), but getting there is such a pain on occasion.

    I realize more than a little of this is probably attributable to the motherboard manufacturer/efi settings, but the last few AMD platforms I’ve had are just wonky and less than 100% reliable compared to the last several Intel ones, which have typically just worked, correctly, every time.







  • 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.