One of my fav instructors has a free YouTube course on Linux. Jumping around and watching it as a refresher (and to learn some new stuff)
Copped a few more Udemy courses (I'm addicted smh). Got one on Bash Scripting. Not sure I'll be able to use it regularly, but if I can automate some work stuff, it will pay off pretty quickly
Bash Mastery: The Complete Guide to Bash Shell Scripting
Master Bash Shell Scripting to Automate Tasks, Save Time, and Boost Your Career. Practical Projects + All Code Included.www.udemy.com
So Chromebooks run Debian in a container & I configured that to SSH into my W10 Desktop.
The plan now is to automate Debian backups & push them to an external hard drive on my W10 desktop to save space.
The issue is I can't get the damn ssh to stop prompting me for a password, so I can't automate the steps. I followed instructions online and created an authorized_keys file, but no dice
My desktop has two ssh locations, one is buried inside WSL2 (ie /home/macallik/.ssh/authorized_keys), and the other is in Windows (C/Users/macallik/.ssh/authorized_keys). I duplicated the key info in both but no dice.
Might just have to settle for running chron monthly and then just manually pushing the files via rsync
What is the purpose of SSH authorized_keys file
ssh authorized_keys file is private. The ssh authorized_keys file should be placed in a directory which is only accessible by the user. For example, the ~/.ssh directory.
ssh authorized_keys file permissions should be set to 600 which means that only the user who owns the file can read and write to it.
ssh server daemon usually looks into ssh authorized_keys file for ssh key fingerprint. ssh authentication protocol uses ssh keys to verify that the user is authorized to login.
Figured it out. Upgrading from WSL -> WSL2 breaks SSH abilities. Reverted today and it is working as expectedSo Chromebooks run Debian in a container & I configured that to SSH into my W10 Desktop.
The plan now is to automate Debian backups & push them to an external hard drive on my W10 desktop to save space.
The issue is I can't get the damn ssh to stop prompting me for a password, so I can't automate the steps. I followed instructions online and created an authorized_keys file, but no dice
My desktop has two ssh locations, one is buried inside WSL2 (ie /home/macallik/.ssh/authorized_keys), and the other is in Windows (C/Users/macallik/.ssh/authorized_keys). I duplicated the key info in both but no dice.
Might just have to settle for running chron monthly and then just manually pushing the files via rsync
For some reason, I only figured out in the past week that many front-end Linux OS are built w/ Debian in the backend. I was thinking it was a standalone CLI-only tool this whole timeAnybody tried out Debian Bookworm yet?
i need to learn this docker shyt too. i just been letting the leads set up the dockerfiles and i just build/up and down/exec when i need to. yeah im a lazy fukkNow I'm lowkey itching to try Debian. Gonna play around w/ it once I get the hang of this Docker Course I'm taking.
Docker is probably one of the most straightforward tools I've used. The biggest roadblock was figuring out permissions issues when copying files in - files lose execution privileges on copy so you gotta remember to add them back.i need to learn this docker shyt too. i just been letting the leads set up the dockerfiles and i just build/up and down/exec when i need to. yeah im a lazy fukk