Nah the hash function gives up after 256 bytes and outputs *, matching the ‘hash’.

Edit: it’s unix tradition to put * as the hash for system accounts that should never be able to be logged in, this bug now means you can login (with the right config), using any password longer than 256 characters.

Fluxer are also moving away from LiveKit, so hopefully that means it’ll require less ports soon.

Some servers do publically list their PHP version, and as an example there are currently ~23,000 that list PHP 8.5.11: https://www.shodan.io/search?query=PHP%2F8.5.11

Sure these could be a manually patched version of 8.5.11, but I find that pretty unlikely.

They were proper 384bit certs, just the upper 376 bits were 0 in all the listed certs. So it’s different to setting the key size in OpenSSL, and they were most likely rolling their own crypto.

If you don’t mind using alternative DNS servers, meaning this won’t be accessible to the average person, you could try OpenNIC.

Unless there are vents underneath, you might also want to flip that power supply around, so the fan’s on top.

If you absolutely have to scan a face, apparently this works: nofacescan.app

So it seems I was wrong about Cloudflare having seperate prefixes for WAF and workers. And these are all WAF/workers IPs (but not warp). My guess is that someone’s made themselves a http proxy worker, and are using that to proxy their bot’s requests.

What’s the IPv4? I believe Cloudflare has different prefixes for WAF, warp, and workers.

2a06:98c0:3600::103 is definitely a Cloudflare WAF IP, so my guess is someone using either warp or workers is sending requests and added that IP to X-Forwarded-For as a red herring.

Regarding Google Coral, from the docs: https://docs.frigate.video/frigate/hardware

The Coral is no longer recommended for new Frigate installations, except in deployments with particularly low power requirements or hardware incapable of utilizing alternative AI accelerators for object detection. Instead, we suggest using one of the numerous other supported object detectors. Frigate will continue to provide support for the Coral TPU for as long as practicably possible given its still one of the most power-efficient devices for executing object detection models.

Personally, I’d recommend OpenVINO. It works on iGPUs, and if that’s not possible it’s quite performant on CPUs. I currently run a Google Coral and the Linux driver is no longer officially maintained meaning it breaks every now and then after a kernel update, next time it breaks I’m going with OpenVINO.

Also, I’d install Docker in an LXC for Frigate, it makes passing the iGPU through to it a lot easier.

Can confirm it does:

OrgAbuseHandle: ABUSE9107-ARIN
OrgAbuseName:   ABUSE
OrgAbusePhone:  +1-313-516-8908
OrgAbuseEmail:  abuse@hostodo.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE9107-ARIN

I believe OP would require an authoritative DNS server, which AFAIK Quad9 is not. desec.io would be my recommendation though.

The data included a transcript of all messenger messages.

Not to defend Facebook, but it would be weird if they didn’t, since you can use messenger on any device, and it’s obviously saved on their servers. A transcript of WhatsApp messages would’ve been different though, as they say they can’t read them.

No doubt it’s worse now.

Yeah definitely, and they’re probably hiding some the data too.

I can dig it…but surely the simple option is to have the PC wake up on power restoration, right?

After the PC shuts down, the UPS runtime will increase by a lot. So the power might come back before the UPS turns off, so as far as the PC can see, the power was never lost.

Edit: Also I assumed you meant restore on after AC loss, and not the last state.

The <noscript> messages seem to work for me with uBO.

The Immich app (at least on Android) supports mTLS client certificates, I use that for my instance.

You need the web site to use a certificate from the same root authority as your client certificate.

I’m not sure if I’ve misunderstood you, but I use Lets Encrypt for the server’s TLS, and then my own CA cert (which is only present on the webserver) for the client’s mTLS and everything works fine, since it’s the client that validates the server’s cert and the server that validates the client’s cert.

Only works with the web UI, no apps support it

Yeah that’s true.

you will get warnings when adding your root certificates to any device

It’s not a root certificate, and I’ve never seen any warnings.

Possibly mTLS, which you’d configure in your reverse proxy. You could email them the certificate and instructions on installing it. I believe for Chromium browsers on Windows you basically just double click the cert and click through the wizard. Firefox I know has a thing in the settings for importing the cert. Android you just tap on the cert and make sure it opens with ‘Certificate Installer’ if it gives you the option.

There’s some thinner m.2 to PCIe extensions that might work if there’s no space. Then you just use a normal PCIe sata card.