Oh yes, I understand how they go about smoothing everything over.

But, given the details we know, don’t you think:
• one corporate resignation,
• one months-prior bureaucrat firing, and,
• one investigation into a former PM,
is pretty far removed from could be considered a proportional fallout?

This is the theme of almost all of the “toppling”. Mostly they’ve just… resigned. They probably keep all the perks, and then take up a corporate advisor position once there’s less heat.

Headlines like this make it sound like there’s been real impact beyond generating articles about a few of the more public figures. But reading article, it’s really just a few politicians and bureaucrats resigning. Mandelson’s firing was already months ago. The investigation into a former Norwegian PM sounds like that’s as harsh as it’s got so far for politicians this time. And nothing except one law firm board member resigning for private companies?

They’re all getting away with it, and all the victims get is a hundred headlines about Musk being named in the files, and having their lives endangered from the terrible Don-centric redaction.

It’s a wonder people haven’t started throwing water balloons filled with mud and flour at the cameras. Perhaps he should be grateful that’s not a trend?

I took a brief look at one and it seems they may have learnt their lesson from the first time around, unfortunately.

Pick Up That Can

Out of curiosity, what sort of customizations are you doing with it? I’m just a bit surprised that docker rebuild or a non-trivial fork would be needed, so I’m assuming they’re pretty big changes.

I’m not a spice merchant, and most exploits rarely involve a single step. This screenshot is just a system design red flag.

You’re free to examine the repo yourself and find your own spice, my 5 min look tells me that piefed needs to expend a significant amount of effort on infosec to maintain user trust in the longer term.

As others have pointed out, it does still require (with some caveats about the infra setup) the user to be an admin. But if someone manages to get in to the interface, or another person is granted admin access who shouldn’t have been, it makes it more risky than it needs to be. It also for me is a design choice that indicates other parts of the system should be carefully examined for how they’re handling and sanitizing input.

Any webserver you browse is possibly capable of ACE depending on the implementation. When it starts to hold user data is when that starts to be a big concern. The more points of entry, the more that needs to be secured.

I don’t have any experience with piefed admin, or any opinion on piefed itself, just too many years of web admin experience. And as soon as I see intentionally made doors that allow code input, I start to worry about how much experience the devs who made it have with web admin.

Well, just copy and pasted rather than written. I would have hoped that infra read-level permission, infra write-level permission and admin interface permissions were all separate to begin with, even if the person who spun up the instance obviously has all three.

You do need a level of trust in an admin, of course, but wide open text boxes for putting in code are a questionable system design choice, in my opinion. It adds an extra point of possible entry that then relies on the security of the overall admin interface instead of limiting it to what should require highest level infra admin permissions to access. And if it is something that would be limited to someone who has those, then what is the actual utility of having a textarea for it in the first place?

I get that many people are concerned about is scoring systems, but it seems a lot more worrying to me that it allows arbitrary code execution.

Careful of your eyes! I’m pretty sure you need a special filter or telescope for the sun

While the conclusion of it being replaced with an LED is obviously not what happened, I think it’s very possible that the sun was often orange for him when he was growing up, because of air pollution.

30 years ago, depending on where you lived, there were more cars on the road with less efficient fuel consumption, more people using fireplaces, more people burning trash, less regulation of various industries etc. Searching for images with the phrase “smoke pollution sun” will give you a lot of photos of orange suns, and they’re definitely not all altered for effect. I’ve seen red suns in real life too when wildfires are really bad near my area even though that’s thankfully rare.

We know not the sun itself that is orange, but in a polluted environment it certainly looks like it is - and if you don’t get a great education, I can see how you might think that’s the actual color of the sun.

Nah, it’s 24.04 LTS

1. Ubuntu memory allocation and limits (I think). I haven’t dug too much into finding the root cause, but I have a recurring issue where the GUI freezes up, and it looks like it might be related to not handling well how much memory it needs for the task.

Maybe it thinks it has more memory available than it does, or the gc isn’t running efficiently, or it’s allocating to 100% without including a sensible safety gap, something like that. It’s a significantly low-level enough problem that I’m wary of tinkering with values I don’t fully understand even if I wanted to spend the probably large amount of time necessary to find root cause.

2. The fact Ubuntu now withholds package updates unless you’re paying for their “maintenance and compliance subscription”, but that’s probably on me to change distros. I get that Ubuntu employees need money so they can eat, just like I do, but … The idea of paying for core package updates feels like a nightmare waiting to happen, for both Ubuntu developers managing package dependencies and end-user experience.