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.

AI; Didn’t read. It’s the AI version of tl;dr (too long; didn’t read).

Well you can’t sign new certs (with the current date) with an expired root/intermediate cert, but the root/intermediate cert expiring doesn’t strictly invalidate the already signed certs.

But I was more talking about the end-user certificates in the previous comment.

Because these are root certs which are still fine, it’s the intermediate certs that are compromised.

I still disabled eMudhra’s emSign G3 anyway, but that’s probably why Google hasn’t disabled the ones shown.

Yeah, my understanding was they’re not issuing new certificates, but the current ones are still valid until they’ve expired.

FYI, G3 is the only one listed with the issue, the others are fine AFAIK. But if you don’t trust eMudhra at all after that, then that’s fair.

Edit: Actually it’s the intermediate certs that are compromised, the roots are still fine, but many of them come from the G3 root cert (and Sectigo’s AAA Certificate Services)

Source: https://emudhra.we-have-a-problem.com/

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.

GPS doesn’t handle leap seconds. Currently devices have to subtract ~18 seconds to convert from GPS time to UTC, this just means that offset will never need to be updated for a few thousand years. Other GNSS constellations may be different, but I assume they’d also be unaffected.

Cloudflare, Inc., is an American technology company headquartered in San Francisco, California

https://en.wikipedia.org/wiki/Cloudflare

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.

It also stands for Immigration and Customs Enforcement in the US.

Also like the other guy, when you spam all your blog posts within the same hour, it’s annoying and most people will ignore them. At least limit yourself to once a day.

This probably isn’t too useful for you as they only have 24v and 54v models, but Ubiquiti used to make EdgePower UPSes. They have a http management interface that lets you monitor the power usage or power cycle the router if a ping stops responding, and etc. I installed one recently for a POE switch of mine.

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.

the smallest model made by Deepseek is about a 300B param model.

This is not correct. DeepSeek has plenty of smaller models. I just had a scroll through their huggingface, and picked out a few: DeepSeek-V2-Lite (16B), deepseek-moe-16b-chat, deepseek-llm-7b-chat, but there’s quite a few more too.

Though DeepSeek R1 is their flagship model, which is the one people usually think of, and that’s a 684B param model.

Can confirm it does:

OrgAbuseHandle: ABUSE9107-ARIN
OrgAbuseName:   ABUSE
OrgAbusePhone:  +1-313-516-8908
OrgAbuseEmail:  [email protected]
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE9107-ARIN