Global namespace extremist. Defragment your communities!

  • 2 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle














  • deafboy@lemmy.worldtoLinux@lemmy.mlEncrypt whole system?
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 months ago

    That’s not a slow laptop. I’ve been daily driving worse for years.

    To protect the data from random thief just browsing through the files I still use ecryptfs. It only encrypts the home directory, and the keys are derived from my accounts password, so no extra hassle.

    The encryption is weak by the current standards, and wouldn’t stop a determined attacker, but it’s 100% better than nothing, and I’ve never noticed any performance problems.



  • Gmail offers imap amd smtp access. You have to enable 2FA, and then it will allow you to create account for so called “less secure apps”.

    In your place, I’d either continue using gmail directly, or finish the configuration of the self hosted mail server and just use that with any smtp/imap client. I suggest getting a separate domain for testing first, before moving your primary inbox there.


  • 3d printer is subtracted from revenue for tax purposes

    That makes sense. Since my profits always oscillated around zero, claiming any expenses had no practical effect.

    legitimately running a business, or just trying to save money on their hobby

    That’s actually how it started. We’ve installed linux on some old desktop machine with my classmate back in school, set up some services like webhosting, mail, jabber, and started to give access to people for free. No guarantees, no pressure. As we finished school, trying to turn it into a business was a logical next step. It never went big, but we just kept the thing around, bought newer hardware, moved it to a proper housing, did basic maintenance, and years later, here I am owing to the government thanks to my highschool hobby.




  • Of course security comes with layers, and if you’re not comfortable hosting services publically, use a VPN.

    However, 3 simple rules go a long way:

    1. Treat any machine or service on a local network as if they were publically accesible. That will prevent you from accidentally leaving the auth off, or leaving the weak/default passwords in place.

    2. Install services in a way that they are easy to patch. For example, prefer phpmyadmin from debian repo instead of just copy pasting the latest official release in the www folder. If you absolutely need the latest release, try a container maintained by a reasonable adult. (No offense to the handful of kids I’ve known providing a solid code, knowledge and bugreports for the general public!)

    3. Use unattended-upgrades, or an alternative auto update mechanism on rhel based distros, if you don’t want to become a fulltime sysadmin. The increased security is absolutely worth the very occasional breakage.

    4. You and your hardware are your worst enemies. There are tons of giudes on what a proper backup should look like, but don’t let that discourage you. Some backup is always better than NO backup. Even if it’s just a copy of critical files on an external usb drive. You can always go crazy later, and use snapshotting abilities of your filesystem (btrfs, zfs), build a separate backupserver, move it to a different physical location… sky really is the limit here.