A1kmm

joined 2 years ago
[–] A1kmm@lemmy.amxl.com 26 points 1 day ago (1 children)

So back in 1994 my neighbours and I agreed that I'd give them my anti-theft fog cannons, as long as they promise not to steal my stuff.

Then in 2014 they sent some buddies in to burgle my place, and got away with a chunk of my stuff - and I know it was said neighbour behind it, because they now openly claim what was taken is theirs (of course, I never agreed with them on that).

Then since February 2022 they've started regularly burgling my place - in the first few weeks, they tried to take literally everything, but fortunately I hired good security guards and they only got away with about 20% of my stuff (including what they stole in 2014).

I've been trying to make arrangements for a monitored alarm system that will bring in a large external response if more burglaries happen, but the security company doesn't want to take it on the contract while a burglary is in progress - but they did sell me some gear. I'm still working on getting the contract.

They say they'll stop trying to burgle my place as long as I promise not to ever get a monitored burglar alarm, to officially sign over the property they've already stolen and to stop trying to get it back, stop buying stuff to protect my property from the monitored security company, and that I fire most of my security guards.

Do you think this is really their end game, or if I agree, do you think they'll just be back burgling more as soon as I make those promises, with fewer security guards and stuff to protect my house? After all, I did have an agreement with them back in 1994 and they didn't follow that.

[–] A1kmm@lemmy.amxl.com 2 points 2 weeks ago

That doesn't work as a defence in common-law jurisdictions (at least), because all participants who deliberately participate in a crime are considered equally guilty of it.

I'd say this is not a strategy to avoid prosecution, but more the brazen acts of individuals who don't fear prosecution.

[–] A1kmm@lemmy.amxl.com 1 points 3 weeks ago

I suspect anything about heaven was likely to manipulate religious voters into voting for him.

Most likely, he is envious of other US presidents like Obama who were given a Nobel Peace Prize. For the whole 'Board of Peace' thing, he likely also sees it as a way to manipulate into becoming something of a world dictator who sits above world leaders.

There is a thing called the 'Dark Triad' of personality traits, consisting of Psychopathy (lack of empathy for others / celebration of others suffering / impulsive), Narcissism (thinking of oneself as superior) and Machiavellianism (manipulating others, seeking revenge etc...) - and they often occur together in the same person. The dark triad is correlated positively with jealousy - and dark triad people consider themselves superior to peers (even when evidence points the other way) and deserving of recognition. They are vindictive towards people who get in the way of what they think they deserve.

[–] A1kmm@lemmy.amxl.com 5 points 1 month ago

Unfortunately, scams are incredibly common with both fake recruiters (often using the name of a legitimate well known company, obviously without permission from said company) and fake candidates (sometimes using someone's real identity).

No or very few legitimate recruiters will ask you to install something or run code they provide on your hardware with root privileges, but practically every scammer will. Once installed, they often act as rootkits or other malware, and monitor for credentials, crypto private keys, Internet banking passwords, confidential data belonging to other employers, VPN access that will allow them to install ransomware, and so on.

If we apply Bayesian statistics here with some made up by credible numbers - let's call S the event that you were actually talking to a scam interviewer, and R the event that they ask you to install something which requires root equivalent access to your device. Call ¬S the event they are a legitimate interviewer, and ¬R the event they don't ask you to install such a thing.

Let's start with a prior: Pr(S) = 0.1 - maybe 10% of all outreach is from scam interviewers (if anything, that might be low). Pr(¬S) = 1 - Pr(S) = 0.9.

Maybe estimate Pr(R | S) = 0.99 - almost all real scam interviewers will ask you to run something as root. Pr(R | ¬S) = 0.01 - it would be incredibly rare for a non-scam interviewer to ask this.

Now by Bayes' law, Pr(S | R) = Pr(R | S) * Pr(S) / Pr(R) = Pr(R | S) * Pr(S) / (Pr(R | S) * Pr(S) + Pr(R | ¬S) * Pr(¬S)) = 0.99 * 0.1 / (0.99 * 0.1 + 0.01 * 0.9) = 0.917

So even if we assume there was a 10% chance they were a scammer before they asked this, there is a 92% chance they are given they ask for you to run the thing.

[–] A1kmm@lemmy.amxl.com 8 points 1 month ago (1 children)

Maybe they figure if you can't fix the form to make it submit, you wouldn't be up to their standard :-)

[–] A1kmm@lemmy.amxl.com 4 points 2 months ago (2 children)

I think the DNC-ignoring callers are likely scammers imitating the real installers trying to get card numbers. If you paid one, you'd lose your money and not get the system.

[–] A1kmm@lemmy.amxl.com 18 points 2 months ago

The US for years kept the screwworm from spreading back into Panama by maintaining a virtual wall of sterile flies across the Darién Gap, which was a cheap way to protect all of North America.

But then stupid MAGA politics came along, put idiots in charge, and they decided that they'd rather try to protect the Mexico-US border and not give Mexico and Panama the incidental benefit, rather than protecting a smaller border that happened to help other countries. https://www.msn.com/en-us/news/world/we-once-rid-the-us-of-this-nasty-parasite-now-it-could-be-coming-back/ar-AA1DKRSV has some information about how it became a problem again.

[–] A1kmm@lemmy.amxl.com 1 points 2 months ago

The terminology in Aus / NZ is pet (owned by people) vs stray (socialised around people but not owned) vs feral (not socialised to people).

Generally speaking, pets & strays like people - they've been handled as a kittens. Pets can become strays and vice versa. But feral cats (past being a kitten) will never become stray / pet (and vice versa) - it is only the next generation that can be raised differently.

While the article is defining feral cats as any cat that isn't a pet, in reality the vast majority of what it is talking about are truly feral cats - nothing like a house cat.

[–] A1kmm@lemmy.amxl.com 5 points 2 months ago (1 children)

With the added complication that it's unlikely that Mangione actually killed anyone - someone killed someone in favour with the Magats, so by their logic, someone has to be killed to send a message.

Like how likely is the story that someone (who looked nothing like the surveillance photos released at the time) was called in by restaurant staff, and despite having allegedly travelled a long distance from the scene of the crime, and many opportunities to destroy everything, had a manifesto confessing to the crime, and the murder weapon still on him? Despite him having no prior inclination towards that sort of thing even?

Hopefully any jury has good critical thinking skills and can see through an obvious set up.

[–] A1kmm@lemmy.amxl.com 11 points 3 months ago (2 children)

That's a false dichotomy though. There are ways to prevent cheating that don't rely on the security of the client against the owner of the device on which the client runs (which is what both of what your 'ways' are).

For one thing, it has long been a principle of good security to validate things on the server in a client-server application (which most multi-player games are). If they followed the principle of not sending data to a client that the user is not allowed to see, and not trusting the client (for example, by doing server-side validation, even after the fact, for things which are not allowed according to the rules of the game), they could make it so it is impossible to cheat by modifying the client, even if the client was F/L/OSS.

If they really can't do that (because their game design relies on low latency revelation of information, and their content distribution strategy doesn't cut it), they can also use statistical server-side cheat detection. For example, suppose that a player shoots within less than the realistic human reaction time of turning the corner when an enemy is present X out of Y times, but only A out of B times when no enemy is present. It is possible to calculate a p-value for X/Y - A/B (i.e. the probability of such an extreme difference given the player is not cheating). After correcting for multiple comparisons (due to multiple tests over time), it is possible to block cheaters without an unacceptable chance of false positives.

[–] A1kmm@lemmy.amxl.com 13 points 3 months ago

Amazon spokesperson Margaret Callahan described it as “obsolete” and said it “completely misrepresents Amazon’s current water usage strategy”.

Interesting that they don't say in which direction it misrepresents (is it saying it is too high or too low). Maybe they are hoping the reader will infer from what they are saying that they're using less now, without them having to say that.

 

spoilerHe was the instar pupa.

 

Today, lemmy.amxl.com suffered an outage because the rootful Lemmy podman container crashed out, and wouldn't restart.

Fixing it turned out to be more complicated than I expected, so I'm documenting the steps here in case anyone else has a similar issue with a podman container.

I tried restarting it, but got an unexpected error the internal IP address (which I hand assign to containers) was already in use, despite the fact it wasn't running.

I create my Lemmy services with podman-compose, so I deleted the Lemmy services with podman-compose down, and then re-created them with podman-compose up - that usually fixes things when they are really broken. But this time, I got a message like:

level=error msg=""IPAM error: requested ip address 172.19.10.11 is already allocated to container ID 36e1a622f261862d592b7ceb05db776051003a4422d6502ea483f275b5c390f2""

The only problem is that the referenced container actually didn't exist at all in the output of podman ps -a - in other words, podman thought the IP address was in use by a container that it didn't know anything about! The IP address has effectively been 'leaked'.

After digging into the internals, and a few false starts trying to track down where the leaked info was kept, I found it was kept in a BoltDB file at /run/containers/networks/ipam.db - that's apparently the 'IP allocation' database. Now, the good thing about /run is it is wiped on system restart - although I didn't really want to restart all my containers just to fix Lemmy.

BoltDB doesn't come with a lot of tools, but you can install a TUI editor like this: go install github.com/br0xen/boltbrowser@latest.

I made a backup of /run/containers/networks/ipam.db just in case I screwed it up.

Then I ran sudo ~/go/bin/boltbrowser /run/containers/networks/ipam.db to open the DB (this will lock the DB and stop any containers starting or otherwise changing IP statuses until you exit).

I found the networks that were impacted, and expanded the bucket (BoltDB has a hierarchy of buckets, and eventually you get key/value pairs) for those networks, and then for the CIDR ranges the leaked IP was in. In that list, I found a record with a value equal to the container that didn't actually exist. I used D to tell boltbrowser to delete that key/value pair. I also cleaned up under ids - where this time the key was the container ID that no longer existed - and repeated for both networks my container was in.

I then exited out of boltbrowser with q.

After that, I brought my Lemmy containers back up with podman-compose up -d - and everything then worked cleanly.

 

I'm logging my idea across a series of posts with essays on different sub-parts of it in a Lemmy community created for it.

What do you think - does anyone see any obvious problems that might come up as it is implemented? Is there anything you'd do differently?

There are still some big decisions (e.g. how to do the ZKP part, including what type of ZKPs to use), and some big unknowns (I'm still not certain implementing TLS 1.3 on TPM 2.0 primitives is going to stand up and/or create a valid audit hash attestation to go into the proof, and the proofs might test the limits of what's possible).

 

Looks like it is also flowing into huge numbers of people using the trams.

 

Stallman was right - non-Free JavaScript does hostile things like this to the user on who's computer it is running.

view more: next ›