Pika

the last time I burned a disk was probably almost 9 years ago now. It was Ubuntu server because at the time I had the concept of "well I should have a hard install source in case I need to do a full reinstall. I dropped that mentality almost instantly though as I realized that it was better for me to just do backups because there was way too much contents for a DVD and I didn’t wanna have to reconfigure if it messed up.

I would describe windows Office as a combination Spyware Malware. It actively collects data on you using obscure means, in an attempt to prevent you from knowing how it’s collecting it. It will also actively change your settings without your knowledge. With recent updates I would even classify it as potentially adware as well, since they mentioned adding advertisements to the start menu and explorer. since they hard push their office products.

Honestly, with the fact that it also now force installs software against the users will on updates, the argument could be made that it’s slipping into trojan territory as well, it’s just lacking the backdoor access, but since they are hard pushing MS account authorization for login, I guess you don’t really need a backdoor when if you wanted to you could just force a password change and be able to login via the native login system.

edit: I thought this post was based off MAS as in to activate windows, I just now realized it was MAS for office activation. I still think that the same applies, just not the trojan aspect. I have edited it to reflect it.

I’ve never rebuilt a container, but I also don’t have any containers that are deprecated status either. I swap off to alternatives when a project hits deprecation or abandonware status.

My only deprecated container I currently have is filebrowser, I’m still seeking alternatives and have been for awhile now but strangely enough it doesn’t seem there are many web UI file management containers.

As such though ever since I learned that the project was abandoned on life support(the maintainer has said they are doing security patches only, and that while they are doing more on the project currently, that could change), the container remains off, only activating it when i need to use it.

oh for sure, it made sense that they wanted to make sure was fixed. Just was super alarming the speed it was advertised that the relay was there!

reminds me of my first mail server, accidentally set up an open relay and got a lot of abuse reports from mail providers saying they blocked my server due to it. Took forever to get fixed again.

fully agree, mine isnt accessible to the outside world either but, you never know if something gets missed or somehow a path gets made. would rather not open up that risk

Sadly no recommendations, I still use portainer myself

while docker does have a non-root installer, the default installer for docker is docker as root, containers as non-root, but since in order to manage docker as a whole it would need access to the socket, if docker has root the container by extension has root.

Even so, if docker was installed in a root-less environment then a compromised manager container would still compromise everything on that docker system, as a core requirement for these types of containers are access to the docker socket which still isn’t great but is still better than full root access.

To answer the question: No it doesn’t require it to function, but the default configuration is root, and even in rootless environment a compromise of the management container that is meant to control other containers will result in full compromise of the docker environment.

man, arcane looks amazing, I ended up deciding off it though as their pull requests look like they use copilot for a lot of code for new features. Not that I personally have an issue with this but, I’ve seen enough issues where copilot or various AI agents add security vulnerabilities by mistake and they aren’t caught, so I would rather stray away from those types of projects at least until that issue becomes less common/frequent.

For something as detrimental as a management console to a program that runs as root on most systems, and would provide access to potentially high secure locations, I would not want such a program having security vulnerabilities.

it’s “new” with windows 11, but they redesigned it, it no longer is blue, its a black screen with white text saying “your system encountered an issue and needs to restart” and then the stop code is a bit smaller light grey that blends in with the background which makes it hard to see.

It’s not all bad though, like it now gives a little more info about what failed if it is able to know, but i just find tiny text on black a pain and I preferred the frown and clear right to the point text.

For this one it really depends on the context. Many apps are super pushy and don’t give you notice they are even trying to do anything. If I was minding my own business and just happend to open amazon music on my phone to listen to music, I would get super confused about time my watch decided to try and pair itself to the account. Like first off, why are you messaging me, second why are you trying to do something i didn’t ask you to do.

Granted I could tell right off what that message was likely indicating it wanted to do, but thats because I’ve used tech for years now and I understand how code based pairing works. I could defo see someone who wasn’t used to code based account pairing looking at that and saying “what does this mean, why do I need to go to a website and put a code in”

You mean like the “new” BSOD for windows? god that new screen is the worst when troubleshooting.

While I expect this is fake, I don’t know whats worse about it. the fact that copilot got that wrong, or the fact that they used it in the first place instead of one of the 3 built in functions that can summarize cells.

I’m just chiming in to say that while the documentation gives you information on how to do external access, there are multiple issues open on the github about unauthenticated endpoints that if you know what is on the server already, you can confirm that it’s there

So I wouldn’t use a standard naming convention because using that knowledge, someone who cares could use common names that could be on the server, followed by common standards of formats they would be in, and be able to confirm it’s their via the end points.

I threw it into a reverse image search and I do have to agree with the other two. It does look to be in a ademco keypad. I had a lot of hits on Ademco 6139

Not only that, theres also an increasing number of anticheat’s that supports linux, however they have it intentionally disabled so when you run the game it either blocks you or in worse case bans your account as a whole

you arent the only one. I had suck a painful onboarding process with next cloud from the docker setup to the speed of it to the UI that I just gave up and decided to use a combination of immich and syncthing instead.

this entire thing has made me really rethink whether I want to swap to the new repo or not.

Why was there no communication about it. The gplay repo maintainer wasn’t informed of anything, no public notice to anyone was given, just a transfer of the repo and a status issue here explaining it.

Obviously the act is genuine as they were able to keep the original keys but like, this entire system seemed really sketchy.

I’m also not happy with the fact that it seems the first thing they added was removing checksums, but that might be a temp thing.

I also just noticed that it looks like they removed the entire public key for it, which if they had the original private keys using the existing public keys shouldn’t be an issue right?

One of my drives crippled itself a few days back, not sure what caused it. Wasn’t able to be resolved without a host restart which was unfortunate. SMART isn’t failing and has been working fine, so I’m chalking it down to a weird Proxmox bug or something.

For sure expected I was going to need to do a rollback on an entire drive after that restart though. Still may have to if it reoccurs.

Right? I don’t have a framework but, I have a dell inspiron 15, keyboard replacement is a simple flathead screwdriver between the case and the keyboard to pop it out, unhook the keybard wire and then install the new keyboard the same way but reverse.