SayCyberOnceMore @ Cyber @feddit.uk

Posts

18

Comments

554

Joined

2 yr. ago

Aha! I was considering moving from proxmox to incus too, but incus seemed quite new and not much documentation (at the time)

How do you find it now?

Skimming through the Qualsys report it seems that the attacker would already need access to the device first, to be able to crash the processes and then collect the hashes, so I'd say this vulnerability appears to need chaining with other(s)?

Appears to be a VM issue, not physical devices.

Happy for them to be developing an app (which already appears to exist), but at ~20‰ with 16 days left... wouldn't it be "better" to collaborate with existing apps like Pipepipe / Newpipe and direct those funds into the platform instead?

Yeah, but it's hard work to make it look easy.

I made a video for work once, it was basically a recorded Teams call, but, good god, I was awful 🤭

Hadn't thought about all the locale, etc.... good point, thanks

Yeah... notes... they started about 50% of the way through building the system.

Now, my notes are great, but some of these devices are ~10 years old.

But, yep, I totally agree, notes are a damn good thing to have.

Not thought about bash history though, interesting point, but I think that only goes back a short duration?

Yeah, at least others are confirming what I had assumed, rather than everyone pointing me to a blindingly obvious tool that did it all for me!

Good point, not thought of that - thanks

Lucky you.

Yep, I'd seen some other videos of his, he does seem genuinely interested in passing on his knowledge

Ok, good point on not writing from scratch - which is what I had been doing for the first few... whixh is rewarding to learn how it works, but it is slow.

Thanks

Hmm, that's not a bad shout actually...

I can fire up VMs to replicate the real system and maybe (depending on space) keep them as a testbed for future mods.

Thanks, good idea.

Well, I'm using the smaller HA client so that it doesn't use google / apple servers, this means no location data via the HA client on my phones.

So, for me there is no location data already in HA. I have to put it there.

"History" - as in long term storage of where I've been? I don't need to keep more than a day (or 2) live on the system... but the webhook is just a sensor with data, so the storage can be longer if required.

For us, there's a lot of noise with us wandering around the house / town / etc. that has no longterm interest. Instead, I'll use OSM to track an interesting journey.

But, integrating straight into HA simplifies my overall system - 1 less server to secure & maintain.

No, that's a fair point. I bought the earlier EmonPi (1), which only has grid + solar CT clamps... looks like EmonPi2 has more by default.

But, my unit has been totally reliable, inc. many harsh powercuts, so it's a long term purchase.

I'm using the traccar client integration in HA and the traccar client on my phones.

So, I don't have traccar server anywhere.

This allows me to use the webhook URL from the traccar client integration on HA and use a web proxy to protect that from the internet.

On the phones, the traccar client connects to the webhook URL I expose through the proxy.

Hope that makes sense as everything is called client here - took me a while to work it out myself.

Late to this one, but check out Open Energy Monitor

They have a main unit which can have multiple clamps on (upto 200A) and also remote units if your power distribution is scattered all over the place.

I've been using their older EmonPi for years, ever since I added in SolarPV and it's now linked into Home Assistant so that I can start turning things on & off when I have excess solar energy... not to mention managing the costs.

Is my maths wrong, or does this not make sense?

The highest concentration came from Brazil, India, Indonesia, and Vietnam. The US ranked 4th among the most affected countries

...so... US is 5th? Anyway, who cares...

As long as everyone logs out and doesn't keep their browser / phone continuously logged into google... ah... there's the problem.

Thanks, from memory I think I have extra already enabled... maybe...

It's good to know that when (not if) I find time to do that update, there's a good chance it'll work

Remember, the 's' in IoT is for 'security'

Gotta admit, it was a bit difficult to get my head around all the different installation types when I was a new user, so simplification is probably well over due