The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
So probably best dispense with all these "educated guesses" because the real take away here is that nobody seems to know who the Jia Tan person (or their ally Kumar) is beyond a name and an email address floating around the ether.
Shame that we aren't the doxxing geniuses that out enemies claim we are.

Incidentally, the person who happened to find this because they were micro-tuning the performance of something, is a Microsoft engineer who was tweaking things to work better on MS's Azure platform.
This here proves the worth of the Azure Linux project. Microsoft has been actively working to make a very fast and secure Linux distro for cloud services, stripping it down to the bare minimum needed to run in order to reduce its attack profile. If anyone was going to detect deep malicious code like this it would've been this project.

The Azure Linux Container Host only includes the necessary set of packages needed to run container workloads. As a result, it consumes limited disk and memory resources and produces faster cluster operations (create, upgrade, delete, scale, node creation, and pod creation) on AKS.

If I ever figure out containers I might be interested in switching my home server from Debian to Azure Linux if I can make it work for home use. I think Hyper-V server is is free so that would be something interesting to play with
 
Last edited:
Here goes my third arch install in a 30 minute timespan because I keep forgetting my root password. I should just set it to “Buttholez” next time
 
  • Feels
Reactions: Battlefield42
There's no conflict here. Init is the right place to use (relatively simple and trivial to audit) shell scripts.
One major thing is shell scripts are easily human readable unless deliberately obfuscated. They're also easily human writeable to create custom runlevels and know what they're doing. I only ever did this once (a really simple Solaris system to control a couple racks of modems remotely) and it took me less than a day even having to figure it out with a book next to me.

(By comparison I knew people who could do that kind of thing in a half-hour.)

Now I couldn't do that now and I doubt I could do it on systemd at all.
 
I was only a novice sysadmin. I loved systemd so much, I had all the unit files and bootloader configs. I'd pray to Lennart Poettering every night before I go to bed, thanking him for the init system I've been given. "systemd is love", I would say, "systemd is life". My senior sysadmin overhears me and calls me a faggot. I knew he was just jealous of my devotion to systemd. I called him a Luddite. He slaps me and sends me to debug a legacy SysV init script. I'm crying now and my face hurts. I SSH into the server and it's really unstable. A warmth is moving towards me. I feel something touch me. It's systemd. I'm so happy. It whispers in my ear, "This is my PID 1". It grabs me with its powerful dependency resolution, and puts me in a predictable state. I spread my unit files for systemd. It mounts my root directory. It hurts so much, but I do it for systemd. I can feel my backwards compatibility tearing as my eyes start to water. I push against its force. I want to please systemd. It journals a mighty log entry, as it fills my system with its love. The senior sysadmin walks in. systemd looks him straight in the eye, and says, "It's all containerized now". systemd leaves through my UNIX socket. systemd is love. systemd is life.
 
Here goes my third arch install in a 30 minute timespan because I keep forgetting my root password. I should just set it to “Buttholez” next time
If it'll let you do it, add init=/bin/bash to the end of your kernel command line in GRUB. It'll boot to a root bash prompt, and you can use passwd to reset your password.
 
I saw something that said he's also worked on Loongson code, which makes it 100% he's Chinese.
1000003838.jpg
Didn't know I needed an excuse :smug:
 

most if the top posts on r/linux is about xz. i dont want to check the bulletin boards but there must be a major shitstorm there too
i think my server on debian 11 should be safe from the other malware found

heres a video that explains it https://www.youtube.com/watch?v=jqjtNDtbDNI basically the OG maintainer of liblzma, xz-utils etc... started the project as a hobby, a fuck ton of corporations, open source projects, every linux distro used it as a dependency. He was the only maintainer and was under a ton of pressure, he had no help maintaining, no financial help etc and was having mental health issues.

You can read the mailing list, its sad. A person there was brutally rude telling him to give the project up because he wasn't moving fast enough (which is just insanely out of touch and rude) so he passed it off to the only other person who was committing to the project, and that person slowly introduced commits that very intentionally added a backdoor.

but anyways the new person used a few inconspicuous commits using tests and a couple of test archives that contained a binary object file and some dormant code that he cut out and used to add a hook into the build pipeline that injected this object into the main library. Its likely imo that the code is just a hardcoded RSA key, potentially allowing this person to SSH into any machine that exists with that library (which is a metric fuck ton).

This could have easily been avoided by following the bus rule and if the people who relied on open source libraries like this had provided code or money so that people like this don't get driven into the ground. Its only a matter of time for this to happen with libraries like these and it would be very easy for malicious actors to exploit that by gaining trust and then slipping backdoors into core OSS libraries over time by targeting undervalued, overlooked and down right abused developers of vital libs. Something needs to change.
 
Last edited:
This reeks of government.(and yes, not necessarily chinese government, guy could have also named himself John McAmericanson)
I doubt it 'cause it seems pretty amateurish.

State-level actors would've been smart enough to wait to activate the exploit until it had already been pushed to stable repos and installed on running systems.
 
I doubt it 'cause it seems pretty amateurish.

State-level actors would've been smart enough to wait to activate the exploit until it had already been pushed to stable repos and installed on running systems.
it might not have been fully activated, but they didn't anticipate someone noticing the slowdown.
 
it might not have been fully activated, but they didn't anticipate someone noticing the slowdown.
sshd thrashing your CPU whenever someone tries to log in would've been noticed very quickly once the exploit started showing up on cloud servers where you have instances on little CPU resources that get a lot of login attempts from script kiddies
 
  • Thunk-Provoking
Reactions: Betonhaus
The code was incorporated downstream by a Lasse Collins.
I'm sure all the names associated with the xz supply chain attack are mere personas, probably rotational assignments for junior intelligence officers. So we can't draw any conclusions from the names themselves. But whoever came up with Lasse Collins/Lassie Collie, you got a chuckle out of me.
 
I decided it made very little sense to run a rolling release distro on a laptop I barely use except for traveling, so I ultimately decided to go with Devuan. I chose it because it is debian based and also because I didn't want systemd (even though my desktop is still running a distro that has systemd). While the netinstall image didn't work with Ventoy, the live desktop one did. The installer for devuan is a bit weird but it mostly works. The only part that didn't work was GRUB installation but thankfully the boot-repair-disk ISO was able to fix it. I also added the Mozilla repo to use the current firefox instead of the esr version just for consistency as I targzip'd my home folder before installing devuan and the firefox profile is for the current version. I seem to have some trouble opening the file, but maybe it is because I tar'd it first then used the gzip command. I did that because trying to do both in one command wasn't working (probably should've used a gui to archive it in the first place to be honest). Hopefully if I reverse my steps in the command line everything will be fine.
 
I seem to have some trouble opening the file, but maybe it is because I tar'd it first then used the gzip command. I did that because trying to do both in one command wasn't working (probably should've used a gui to archive it in the first place to be honest). Hopefully if I reverse my steps in the command line everything will be fine.
"tar sperging"

Create
tar cvzf file.tar.gz thing

tar cvf file.tar thing
gzip file.tar

tar cv thing | gzip >file.tar.gz

All functionally identical

Uncompress.
cd to the same spot

gunzip file.tar.gz
tar xvf file.tar

tar xvf file.tar.gz (auto detects compressed files)

tar xvzf file.tar.gz

Replace "x" with "t" to list the contents

For a personal home directory I recommend:
cd /home
tar cvzf /somewhere.tar.gz username/
Then when you uncompress you cd to /home
(username directory must exist first, or you must be root, never uncompress untrusted files as root)

If you want to archive/compress your home directory while being in /home/username then use tar cvzf thing.tgz . and not "*" as "*" won't get all your dot (.) files and directories.

Realize that sometimes your old dot files and cofigurations may break your new OS in some strange cases. Often I'll uncompress to a subdirectory and move fies in as I need/want them.

Also, some things (like fucking podman) tends to put root owned files in your home directory so those may not be backed up and give permission errors unless you do the tar and untar as root. Use extreme caution.
 
Back