• 6 Posts
  • 134 Comments
Joined 11 months ago
cake
Cake day: August 10th, 2023

help-circle
rss
  • Yeah, I read that manual but it didn’t answer my question.

    The big problem is that the arch wiki describes a setup with nested subvolumes first (in a subvolume below @ or whatever your root subvolume is), but then suggests in a tip to use a subvolume directly below the top level subvolume. The limitations mentioned in that manual don’t seem to apply to either setup, as they would prevent swap from working, which is not the case. I have tested both setups and they work fine — or so it seems. I’m worried there is some hidden gotcha I’m missing.

    in addition to that, some of those limitations simply don’t apply to my setup, as I only have a single device.











  • The python3 package should contain the entire python standard library

    You are free to use a distro which does not split packages, favorite distro, Arch Linux (btw).

    Or, you can install the recommended dependencies of python3. Testing in a container, the python3 package pulls:

    root@a72bd55a3c1a:/# apt install python3
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    The following additional packages will be installed:
      ca-certificates krb5-locales libexpat1 libgpm2 libgssapi-krb5-2 libk5crypto3
      libkeyutils1 libkrb5-3 libkrb5support0 libncursesw6 libnsl2
      libpython3-stdlib libpython3.11-minimal libpython3.11-stdlib libreadline8
      libsqlite3-0 libssl3 libtirpc-common libtirpc3 media-types openssl
      python3-minimal python3.11 python3.11-minimal readline-common
    Suggested packages:
      gpm krb5-doc krb5-user python3-doc python3-tk python3-venv python3.11-venv
      python3.11-doc binutils binfmt-support readline-doc
    The following NEW packages will be installed:
      ca-certificates krb5-locales libexpat1 libgpm2 libgssapi-krb5-2 libk5crypto3
      libkeyutils1 libkrb5-3 libkrb5support0 libncursesw6 libnsl2
      libpython3-stdlib libpython3.11-minimal libpython3.11-stdlib libreadline8
      libsqlite3-0 libssl3 libtirpc-common libtirpc3 media-types openssl python3
      python3-minimal python3.11 python3.11-minimal readline-common
    0 upgraded, 26 newly installed, 0 to remove and 18 not upgraded.
    

    python3-venv python3.11-venv

    I find it odd, because debian does this by default, actually. They account for usecases like yours, and instead you have to edit a config file or use a command line flag to get it to not install recommended dependencies.






  • https://forgejo.org/compare-to-gitea/

    I dunno, some of these are a pretty big deal, in particular:

    Gitea repeatedly makes choices that leave Gitea admins exposed to known vulnerabilities during extended periods of time. For instance Gitea spent resources to undergo a SOC2 security audit for its SaaS offering while critical vulnerabilities demanded a new release. Advance notice of security releases is for customers only.

    Gitea is developed on github, whereas forgejo is developed on and by codeberg, who use it as their main forge (also mentioned on that page). Someone dogfooding gives me more confidence in the software.


  • The comparison isn’t quite right because you can use git with any provider (Github, gitlab, etc), including multiple at once.

    On the other hand, snap is hardcoded to only be able to use one store at a time, the snap store. To modify this behaviour, you would have to make changes to the snap client source code.

    It’s a crucial difference.



  • sn1per is not open source, according to the OSI’s definition

    The license for sn1per can be found here: https://github.com/1N3/Sn1per/blob/master/LICENSE.md

    It’s more a EULA than an actual license. It prohibits a lot of stuff, and is basically source-available.

    You agree not to create any product or service from any par of the Code from this Project, paid or free

    There is also:

    Sn1perSecurity LLC reserves the right to change the licensing terms at any time, without advance notice. Sn1perSecurity LLC reserves the right to terminate your license at any time.

    So yeah. I decided to test it out anyways… but what I see… is not promising.

    FROM docker.io/blackarchlinux/blackarch:latest
    
    # Upgrade system
    RUN pacman -Syu --noconfirm
    
    # Install sn1per from official repository
    RUN pacman -Sy sn1per --noconfirm
    
    CMD ["sn1per"]
    

    The two pacman commands are redundant. You only need to run pacman -Syu sn1per --noconfirm once. This also goes against docker best practice, as it creates two layers where only one would be necessary. In addition to that, best practice also includes deleting cache files, which isn’t done here. The final docker image is probably significantly larger than it needs to be.

    Their kali image has similar issues:

    RUN set -x \
            && apt -yqq update \
            && apt -yqq full-upgrade \
            && apt clean
    RUN apt install --yes metasploit-framework
    

    https://www.docker.com/blog/intro-guide-to-dockerfile-best-practices/

    It’s still building right now. I might edit this post with more info if it’s worth it. I really just want a command-line vulnerability scanner, and sn1per seems to offer that with greenbone/openvas as a backend.

    I could modify the dockerfiles with something better, but I don’t know if I’m legally allowed to do so outside of their repo, and I don’t feel comfortable contributing to a repo that’s not FOSS.


  • When syncthing is configured to go both ways (the default), it also syncs any deletions. You can somewhat get around this by something like one way sync, but it’s not really a proper “backup” software.

    Personally, I like to treat data synced by syncthing, even between multiple machines, as one copy of the data when I am following the 3-2-1 backup rule*, because syncthing won’t save me from a buggy program deleting all my files or user error, or anything like that.

    *See wikipedia for info about the 3-2-1 backup rule.