KairuByte

I’d stay away from Planka for one major reason: They have started to claw back features that were previously in the community version, and moving them behind a paid tier. OIDC is such a feature, their reasoning being support load, and despite the many calls to just not provide support for OIDC they have assured the community that the consensus is that it’s an enterprise only feature.

tl;dr: Avoid Planka.

On prem is just a fire away from the same fate.

Potentially, assuming they weren’t stolen or sold off to a secondary buyer from a legit first customer. Problem is another one just pops up in its place.

I’m not saying don’t persue them, I’m saying it’s a game of state funded whack’a’mole.

My dude, look into tailscale. Same concept, just as easy to set up, and likely more features. And it’s human made, human tested, and used by a large number of different type of end users.

Eh?

This is if you a) purchase the phone in some way that is associated with your Apple account, b) have cloud backups already in place, and c) opt in to the preload.

If any of those things aren’t in place, it wouldn’t have happened.

Now your likely assuming they can get into that backup, which fair enough would be a concern. But (if you believe them, which I admit is a huge if) according to Apple, they can’t actually get into that backup without your password. Meaning (again, if you believe them) this would be as safe and secure as shipping your own phone cross country after rebooting it.

Yes, it’s also how I run all my services. I checked just this moment, and locally my certs verified by field is Let’s Encrypt, while remotely that field is Google Trust Services

I have never personally provisioned a cert from Google. I have only ever utilized Let’s Encrypt. That leaves just one involved party that could have requested, received and presented this cert: Cloudflare.

My brain is unreasonably stuck on how solar shades on an asteroid could freeze the earth.

Haven’t they been working on this for months? I could have sworn I heard of this well over a year ago.

Tunnels aren’t inherently CDN, you can tunnel UDP info for instance (if you use cloudflared on both sides) and inherently transient things such as websockets.

I’ve had none of my media be cached in their CDN for instance. In fact you’d likely have to do some hoop jumping to make it happen.

No it was definitely removed, they now have essentially “don’t be an ass with the bandwidth.”

Give it a look on dnsdumpster.com or similar. Your dns records are inherently public, so anyone that works out the domain can work out the subdomain. In fact there are plenty of tools that just scan every domain/subdomain they can find.

If that A record isn’t a wildcard, anyone can see it, is what I’m getting at.

They don’t care, that line in the ToS was removed years ago now.

In this case I mean the DNS entry for the random string. The thing pointing that subdomain at your IP/proxy.

How is your DNS set up for that subdomain? Is it on a wildcard DNS record?

I mean, if you put restrictions on the requirement sure. At that point it kinda becomes a loaded question though.

If you remove the restriction, just use a cloudflare tunnel.

Duress profile code?

Have you actually confirmed that is the case? My understanding is that cloudflare pretty much always re-signs with their own SSL cert. and I’m fairly certain that would be absolutely required when using their DNS proxies.

Your ISP likely has multiple datacenters. And even if they don’t, their provider almost certainly does. Your DNS ultimately comes from a datacenter. Your machines clock is likely syncing with a NIST that is, once again, hosted in a datacenter.

A datacenter isn’t some magical thing that only a few companies have, if you’re dealing with a large anything that hosts its own or others data, they more than likely have a datacenter.

Can’t bother to read the article?