Nextcloud: Open-Source Cloud Apps

Post by sneak » Mon, Sep 23, 2024, 8:13 AM UTC

shwouchk wrote: post #200

sneak wrote: post #177

Earlier quoted context omitted.

I cannot enter into the Apple Developer Program, or I would have released a lot of free builds of f/oss iOS apps already. Sadly Apple requires doxxing yourself to publish apps, which IMO is a human rights violation. You also need to provide a working phone number to be able to install even free apps on a phone or tablet you have already purchased. These policies stand directly in opposition to their stated value that…

You don’t believe in intellectual property? Well, I don’t believe in gravity. Ill be waiting for your public domain repo with ios syncthing build instructions - no need to doxx yourself. ill happily build it for myself - i don’t have a dev account either. FWIW that app works much better than icloud has ever worked for me. eg with icloud you never know when the device decides to remove a file from local cache until yo…

Post by izacus » Mon, Sep 23, 2024, 9:58 AM UTC

hypeatei wrote: post #75

izacus wrote: post #51

Earlier quoted context omitted.

Those cloud specialists aren't configuring your ACLs and firewalls - the most common source of severe security problems in the cloud.

Yes, there is a concept of "shared responsibility" in the cloud. Obviously the provider is going to handle some things and you have to take care of others.

Post by nepthar » Mon, Sep 23, 2024, 1:41 PM UTC

laymansterms wrote: post #95

bravetraveler wrote: post #43

Earlier quoted context omitted.

One doesn't have to expose it to malicious actors. It is most-useful that way, sure. Mine is at 10.27.0.68 . Have fun, hackers! Also, I lol at most CVEs. Butterfly farted outside, oh uh. Take the top one: In Nextcloud Desktop Client 3.13.1 through 3.13.3 on Linux, synchronized files (between the server and client) may become world writable or world readable. This is fixed in 3.13.4. You mean to tell me a few minor po…

Yeah, one CVE is literally "You can use the MacOS variant of LD_PRELOAD on the client to hook libc calls! Oh no!!" This is a bogus CVE; any application can perform arbitrary actions when its system calls are hooked, but it requires such a strong threat model that the adversary realistically gains no ground by doing so. ("A code injection in Nextcloud Desktop Client for macOS allowed to load arbitrary code when starti…

Post by sach1 » Mon, Sep 23, 2024, 2:12 PM UTC

doubled112 wrote: post #158

BrandoElFollito wrote: post #151

Earlier quoted context omitted.

If you use docker + watchtower all this is done automatically

I don’t use Watchtower, but a script that takes a btrfs snapshot before doing a docker compose pull, then docker compose up. Same idea, just safer and fewer surprises.

Post by doubled112 » Mon, Sep 23, 2024, 2:25 PM UTC

sach1 wrote: post #237

doubled112 wrote: post #158

Earlier quoted context omitted.

I don’t use Watchtower, but a script that takes a btrfs snapshot before doing a docker compose pull, then docker compose up. Same idea, just safer and fewer surprises.

That's nice and simple, do you have a shareable version of this script or some advice on btrfs pointers/pitfalls?

    SHOT_TIME="$(date +'%Y-%m-%d_%H-%M')"
          
    for dir in /docker/*
    do
        cd $dir;
        btrfs subvolume snapshot "${dir}" "/docker/.snapshots/$(basename $dir)-${SHOT_TIME}"
        docker compose pull --quiet
        docker compose up -d
    done

    /docker
    |--> .snapshots
         |--> app_one-2024-08-28_12-34
    |--> app_one
         |--> compose.yaml
         |--> volumes
              |--> app_one-config
              |--> app_one-db
    |--> app_two
         |--> compose.yaml
         |--> volumes
              |--> app_two-config
              |--> app_two-db