https://gitlab.gnome.org/chergert/ptyxis

Ptyxis is my current go-to. It can detect available pods or toolboxes (maybe docker too haven’t tested it) and you can open terminals directly into them. It also highlights ssh terms and root shells differently.

There are a huge number of built-in color schemes as well and I’ve had no trouble finding any configuration option I’ve found myself wanting to look for.

It’s also available on flathub so it’s easily installed in most distros.

That’s not bad at all gonna have to check it out. I host my site on digital ocean it’s on the smallest single core 1gb ram droplet. I run crowdsec and nginx and a couple other little things and it sits around 40% ram usage. Costs 6$ a month and I added 4 weeks worth of automatic weekly backups for $1.50 a month.

I can deal with $7.50 for a little static web server.

They do offer a free $200/60 day credit if you get in with one of the free Linux Foundation cloud classes which is plenty to play with.

Thanks that’s good to learn!

My main OS (debian) ssd started throwing Io errors this Friday night and I had to work Saturday, only image I had laying around was Fedora Kinoite. So that’s what I’m running until I order a new drive. I’m getting my wife a new laptop soon and was considered silverblue (she’s a Mac user but very quick with tech in general).

Anyway after using it a few days, I think when I get my new drive I might just go ahead and put Kinoite on it. I’m used to running my dev stuff in containers anyway and toolbox makes it super easy. Rpm-ostree is a breeze (though it takes a minute to build on this ancient USB hdd, I’m replacing my dieing SSD with an nvme so I don’t foresee the ostree builds as being an issue).

I think immutable is absolutely the way forward, especially for less computer literate folks. It will keep them more protected and if they do mess up something the rollback is a breeze.

I saw it put really well the other day. Any software has in general a set number of bugs per lines of code. Something like Debian the number of bugs goes down after release as only bugfixes occur, while anything constantly moving like a rolling release, is certain to grow in number of bugs as the less tested newer software (which generally includes more loc) is pushed. There are tradeoffs to both methods, and edge cases of course.

I’d suggest one of the fedora atomic installs, maybe even get a couple renewed Thinkpads all set up, one with kde and one with gnome and let them play with them for a few days. I was the only engineer in my company that ran Linux and the bosses only concession was that I carry a windows PC too when he was onsite with me so he’d understand what I was doing, but he provided a nice one for me so I never complained.

I second the people that said lineage OS. I am using it right now. I got this Nord phone because I knew they were easy to tinker with. I used it a bit and ended up with a newer galaxy. Well after I put lineage on the Nord every problem it had went away. Excellent battery life, runs smoothly, weekly security patches if I want etc. One thing that helped a lot was the “Aurora” app store. Let’s you install apps anonymously from the play store without requiring google services. Many of them won’t work due to the no google services, but a surprising amount of stuff does just fine even if it complains about it.

I had no idea it was standard. I had heard they had issues with it not being able to handle certain constructs so they were working on getting it to a place it would perform better. Has this changed? I’m not a rust person, but I intend to be. I’ve barely made it 1/4th way into the book (just started in the past month and I’ve been busy), but I have a good background in programming and so far it’s been super easy. I’m really enjoying how specific the compiler is, and the binary sizes vs Go.

No offense taken we all have different knowledge and background. I have a general understanding of podman, but now I’m going to go play with it a bit at some point and get more familiar with it.

Docker is Apache 2.0 licensed. It is open source. Or at least all of the important parts. I’m not sure about docker desktop. It’s partly that I just have a lot of experience with docker, and partly just that it’s what is supported in most projects’ documentation. The fact that a lot of the Linux foundation training uses docker is another reason I’ve got more experience with it.

As far as what you are talking about people have been trying for years. The Pirate Bay wanted to develop a new method of being entirely decentralized. Odysee is working on something like blockchain/torrents combined that is very interesting. We have I2P and TOR which have some of the features you mention. I’d love to see it happen where the big companies didn’t control things.

There is progress though. https://letsencrypt.org/ is non-profit, and there are a variety of open source projects using this to automate TLS certificate signing.

Check out https://www.sigstore.dev/how-it-works and pay special attention to Fulcio and Rekor. It’s not for web certs, but it’s still a very interesting take on a certificate authority.

There’s no technical reason what you are saying couldn’t work. It just comes down to how do you trust it, and if you can’t at all, it doesn’t do much good anyway. That’s the problem to be solved. You could compromise somewhere in the middle but then you have to work out what is acceptable. I suppose the level of trust could be configurable, with different nodes earning a different level of trust, and you could configure your accepted levels for DNS or CA. It’s an interesting idea.

gofumpt and gofmt are the best. One of the reasons if I have a choice I’ll code in go. I heard rumblings that rust was working towards having rustfmt be a standard crate.

I’m on bookworm now myself. Check this out https://forum.greenbone.net/t/external-access-to-gsa-web-interface-ip/1671/4 and thanks I’ll let you know if I run into trouble!

I think my issue was I was building it on a debian 11 bullseye. I managed to get all the individual pieces built and running, there was just one piece missing and I can’t remember which now. I’ll certainly give it a go. Someone just sent me a kvm build of debian sid just for that reason in fact! I believe they are working on the gvm debian package.

Thanks :) Exactly. I do a lot of development and testing in an alpine linux container, simply because it has much newer versions of libraries and musl c. If I can get it to compile there, and on debian, I’m in good shape as far as compatibility goes. I used to really enjoy Arch and the rolling updates when I was younger, but I’ve gotten to where I don’t want to mess with things constantly changing.

I use python venv for nearly everything I do python, and the way go is setup does make it extremely easy since it uses a per user environment anyway.

I knew that worked for a lot of stuff. That used to be what I’d try first but I honestly just use a venv for pretty much anything that uses pip nowadays. Still helpful to know there is a package though thanks! I intend to test it out.

Yes you can! I’ve attempted on debian before but it’s something like 12 components you have to build and configure and I ran into some issues. It’s been a while though and I don’t remember exactly what gave me trouble. I know I had issues at one point due to the host not having enough ram. If you don’t have at least 8 gigs it’s not going to be happy. At least in my experience.

Let me know how it goes though and what distro you use.

They have pretty good documentation.

😱 I had no idea. I just went and read through that wow. I hope they don’t sell to someone scummy.

I could have swore I tried it. facepalm I’ll check that out then I might edit that part.

Nice. I might have to clone that setup for fun. What do you use for CI? I’ve got jenkins running but I’ve been wanting to play with gitlab CI/CD too.

I do a lot of my dev work in docker containers, simply so I’m in a clean environment. Doesn’t hurt in ease of backup either. No particular reason not to use docker, I also wanted to keep it kind of brief and simple. The guide I originally read that inspired me had a lot of things that were very outdated, and as I worked through getting it working on debian 12 I generally stuck with the source providers instructions when things weren’t already packaged for dpkg, or alternatives were more complex.

I am currently mulling around doing extensions on this guide and adding links at the bottom, or just extending this one a bit. Also just thinking about writing a guide for other stuff too. I’ve been helping people on discord and irc a bit recently and some of what I know might be useful to someone.

I don’t know everything by any means far from it, but I’ve been around since my first beOS and slackware installs a long time ago and I’ve picked up a lot. I worked developing and deploying pfsense images for a company years ago and have just had a lot of random experience in linux and bsds over the years.

Awesome it is good to see the bearblog getting some love. Just to keep it short mostly. I was debating adding another article continuing this one using nginx for that part. I could add a section to this one though. Or would you use something other than nginx, I’m open to suggestions. I checked yours out, it’s a bit snappier than mine :) . What are you running?

I know you said preferably no docker, but greenbone community edition is nice. It’s a fork from nessus back in the day. They don’t really put any restrictions on the community version. If you want to see it in action I have a test server up and running.