tuhriel

joined 2 years ago
[–] tuhriel@infosec.pub 3 points 1 day ago

Thanks for the link. It seems they got it somehow working on DSM6, but if I check the thread, it's a lot of ducttape and locktight involved especially to run with DSM7. Might try it out on a rainy sunday

[–] tuhriel@infosec.pub 1 points 1 day ago (2 children)

Give me a package that runs on my ds214play and I'll switch in a heartbeat

[–] tuhriel@infosec.pub 2 points 1 week ago

So...in the future it is "this e-mail could have been a meeting"

[–] tuhriel@infosec.pub 4 points 2 weeks ago

I'm running an airsonic-advanced server and use the tempo app on android https://github.com/CappielloAntonio/tempo

And supersonic on linux & windows: https://github.com/dweymouth/supersonic?tab=readme-ov-file

[–] tuhriel@infosec.pub 3 points 3 weeks ago

The point for me is, that I have an acient synology NAS (ds214play) which acts as my media server. There is a community made plex package which I can install easily. As far as I have seen, there is no way to install jellyfin on this NAS, as it doesn't support docker

[–] tuhriel@infosec.pub 27 points 3 weeks ago

The big issue is that they don't just "do not ask", they also actively ignore if it if someone tells "no" upfront. E.g. in a robots.txt

[–] tuhriel@infosec.pub 43 points 3 weeks ago

If your business modell only works if you don't follow any moral or official laws...it shouldn't exist!

Unfortunately, capitalism doesn't work like that...

[–] tuhriel@infosec.pub 3 points 1 month ago* (last edited 1 month ago)

I have a rpi4 awith an external hdd at my parents house, which I connect via a wireguard vpn, mount and decrypt the external hdd and then it triggers a restic backup to a restic-rest server as append only.

The whole thing is done via a python script

I chose the rest-server because it allows "append only", so the data can't be deleted easily from my side of the vpn.

[–] tuhriel@infosec.pub 4 points 1 month ago

Jep, that's something that bothers me now, every algrorithm or autocomplete is now also branded as "with ai support". I don't need ai to add the 'if name =="main" stuff in my python file IDEs (or even lightly advanced text editors) can add that stuff since long before LLMs where a thing...

[–] tuhriel@infosec.pub 3 points 5 months ago (1 children)

From the article:

Andromeda is seen almost edge-on, tilted by 77 degrees relative to Earth’s view

[–] tuhriel@infosec.pub 9 points 5 months ago (2 children)

But, but the corporations are telling us that they loose so much money from all those people who are pirating and therefore not 'buying' their stuff.

I mean the numbers they showed where huge! Hmm, maybe they forgot to carry the one or swapped some +/- diring their calculations.

 

Hi everyone I'm currently in the process to move one of my RPI4s from RaspberryOS to NixOS and I'm struggling to setup one of the services.

On the RPI I have a python script that is creating offsite backups via a Wireguard tunnel:

  • Open the wg tunnel
  • mount and encrypt the external disk on the offsite RPI
  • mount the source from my nas
  • start the restic-rest server container offsite
  • trigger the restic command to backup to the restic repo

allthough it's a bit overkill it works quite well for a few years now. Since most of the tasks are actually outsourced to systemd units those where quite easy to setup in nixOS. What I'm struggling is, how can I create a virtual python env to run the python script. All the guides I found for managing python dependencies are usually for development and use nix shell

My current workaround is, that I copy the script and requirements.txt from my script repo and create the venv manually. This does work, but I feel there is a better way, maybe the whole setup is already on the wrong pat as I tried to solve each hurdle separately?

Here's my current implementation of the remotebackup module (the wireguard and mount units are in different modules):

{inputs, config, pkgs, lib, ... }:

let configpath = builtins.toString inputs.infra-configs;
in
{
systemd.tmpfiles.settings = {
  "remotebackup" = {
    "/var/lib/remotebackup" = {

      d = {
        group = "root";
        user = "root";
        mode = "755";
      };
    };
    "/var/lib/remotebackup/assets" = {

      d = {
        group = "root";
        user = "root";
        mode = "755";
        };
      };

    };
  };

sops.secrets = {
  "restic/remotebackup/rest" = {};
  "restic/remotebackup/restic" = {};
};

sops.templates."remotebackup" = {
  content = ''
  {
    "rest" : "${config.sops.placeholder."restic/remotebackup/rest"}",
    "restic": "${config.sops.placeholder."restic/remotebackup/restic"}",
  }
  '';
  path = "/var/lib/remotebackup/assets/restic.cred";
  };


system.activationScripts.addPythonScript = lib.stringAfter ["var"] ''
    cp ${configpath}/scripts/remotebackup/script/restic_remotebackup.py /var/lib/remotebackup/restic_remotebackup.py
    cp ${configpath}/scripts/remotebackup/script/requirements.txt /var/lib/remotebackup/requirements.txt
    chmod 733 /var/lib/remotebackup/restic_remotebackup.py
    cp ${configpath}/scripts/remotebackup/script/assets/backup_paths.txt /var/lib/remotebackup/assets/backup_paths.txt
    '';

}

Also, on the RPI I'm triggering the script with cron, according to the wiki cron should be replaced by systemd.timers. Would you also suggest moving to systemd.timers

P.S.: If at all possible, I'd like to keep the script within my script repo...

[–] tuhriel@infosec.pub 2 points 5 months ago

I still love the trackpoint and use it almost exclusively if the notebook is not connected on the docking station.

It is just awesome if you can control the mouse while still keeping the hands on the middle of the keyboard.
It's so much faster than to kove up and down and also more ergonomic, especially in the train when the laptop sits on my lap.
The middle button enables easy scrolling on webpages (although the vim browser extention makes it even easier ther) or documents...

Nothing else I used was able to beat this setup. And I used a lot of different devices over the tome

view more: next ›