• 0 Posts
  • 34 Comments
Joined 2 years ago
cake
Cake day: June 26th, 2023

help-circle


  • Once you’re inside a car that’s on, there really isn’t any security*. The OBD2 port that every remotely modern car has is perfectly capable of accessing all the diagnostics and data streams the car has, and can also control/reconfigure the various computers.

    IMO that doesn’t really matter, since the system isn’t powered until the key is in the ignition and the car turned on. You can’t do anything with the key off, and if your passenger wanted to sabotage the car, they’d just yank the wheel as you drive down the highway.

    That said, yes OTA updates are a travesty. Specifically because cars have so little security, having any access to their computers from the outside is a massive risk… And if there’s a potential that the country the manufacturer is in turns hostile, that risk certainly isn’t reduced.

    * A handful of manufacturers have “added” security to their systems by… (drumroll pls) restricting access to the systems and requiring a subscription for full access. That’s fucking evil and doesn’t even do anything (at least for a mechanic or tinkerer like me) since you can just google “FCA bypass cable” and skip right past the firewall.




  • Clearwater@lemmy.worldtoSelfhosted@lemmy.worldGoogle Drive alternative?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    6 months ago

    I use Nextcloud, but as you said it’s a bit big, and with each update it’s slowly turning into more of the entire G-Suite.

    I’ve used filebrowser, but be aware that until just a few days ago, it gave out access to a shell. Even with that turned off, I’d be very weary of allowing access from out of the VPN. I had a server pwned with filebrowser appearing to be the vector, and to my memory console access was disabled for the account most likely breached.




  • I wouldn’t mind if online textbooks had a button on the side that is just a looser search (like what Google was a few years ago).

    It’d be handy if I could type in “gravity problem with the bunny” instead of having to either search for “bunny” and flip through all the results, or try to remember/guess the exact wording of the problem.

    You probably could still call it AI too, since there’s likely some small machine learning model involved in that search.





  • First of all, I actually do prefer Forgejo Actions over Woodpecker. Once set up, my only problem with it (so far) is almost certainly caused by my infrastructure and isn’t inherent to FA itself. Pecker, on the other hand, is quite a bit easier to set up and better documented, but I had that issue where it would disconnect from Forgejo and need a few buttons pressed to fix.

    This one is just FA being weird:

    If you want to deploy the Runner using Docker, the documentation is poor at best. From both a security and documentation standpoint, having it in its own VM is better, but you can do Docker. You just have to read and figure out more on your own. Reading through the example deployments from the documentation will eventually lead you to something along the lines of this (which I copy-pasted from my deployment rather than search for again):

    forgejo-runner:
      image: code.forgejo.org/forgejo/runner:6.3.1
      restart: always
      user: 1000:1000
      environment:
        - DOCKER_HOST=tcp://dind:2376
      volumes:
        - runner_cache:/data
      depends_on:
        - dind
      command: >-
        bash -ec '
        forgejo-runner create-runner-file --name runner --instance https://${DOMAIN} --secret ${RUNNER_SECRET};
        sed -i -e "s|\"labels\": null|\"labels\": [\"docker:docker://docker.io/node:22-bookworm\", \"ubuntu-latest:docker://ghcr.io/catthehacker/ubuntu:act-latest\"]|" .runner ;
        forgejo-runner generate-config > config.yml;
        sed -i -e "s|^  network: \"\"$|  network: host|" config.yml ;
        sed -i -e "s|^  envs:$$|  envs:\n    DOCKER_HOST: tcp://dind:2376\n    CONTAINER_HOST: tcp://dind:2376|" config.yml ;
        forgejo-runner --config config.yml daemon
        '
    

    You don’t actually need to do this since you could edit the two config files yourself and bind them to the container. This is just how you automatically generate those files… And it’s dumb, but it works and it means you don’t have to keep track of those files.

    This one is probably just my infrastructure: https://lemmy.world/comment/16093731

    If you do go for FA in Docker (or Podman) and need some help, just ask. I’ll post more of my compose and explain my decisions.



  • While I do not make heavy use of these two, I like having my contacts and calendar synced and accessible on both my PCs and phone.

    I actually use the notes app, and have a yubikey. For notes, I could just use the regular markdown editor, but I like way the app lays everything out. For the yubikey, NC by default uses yubikeys for passwordless login. I use an app which uses them for 2FA instead. I also use apps which allow me to view hashes and metadata from the files tab.

    All that makes me not want to switch yet. We’ll get there eventually since none of the features I want are ultra complex or super uncommon.

    OCIS, last I tested it (a while ago), also lacked the ability to right click files, requiring you to select it with the checkbox and then select the operation at the top of the screen. I sure hope that they’ve added that feature by now.



  • Nextcloud is more featureful (more apps like notes and hardware 2fa support). That is currently holding me to NC.

    OpenCloud (fork of OCIS not original OC) is very similar when it comes to core functionality, but is missing those few apps I do not want to let go of.

    Also note that nextcloud stores files in a very natural manner, where your file names and directories are stored the exact same on disk as on the interface. Opencloud does not do that. This is particularly handy if one day the app just explodes and refuses to run. With NC, you can just copy the files off the disk. Not so easy with OC.



  • Clearwater@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    9 months ago

    I agree that it is quite possibly related to the version of Podman moreso than an inherent issue. I am currently satisfied, however, and have no desire to fiddle with it any more… Or at least until Debian 13 gets released.

    My use of PinP is almost entirely for cleanliness. It allows me to more easily wipe the build environment (clear out space, troubleshooting). It also mildly improves security as the ‘untrusted’ actions containers run on a separate environment from the important Forgejo container.

    The workaround I use for the premade Docker actions not functioning is to simply install Podman as one of the build steps and use that instead, lol. (Some configuration required, but that’s the gist.)


  • Clearwater@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    9 months ago

    Forgejo Actions is definitely not a turnkey idential-to-GitHub solution, but it’s quite similar and for most not-super-complicated setups it’s basically the same (for better or worse, depending on if you like GH’s Actions).

    As far as I remember, everything that I need works out of the box, except for Docker. In fact, just about everything Docker is somewhat quirky in Forgejo Actions.

    1. One mildly annoying quirk of Forgejo is that as of current, the token generated for each Actions run is not quite the same as GitHub’s token. For my specific use case, if you want to upload a Docker Image to the package repository, you can not use the standard auto-generated token, which GitHub does allow you to use. Forgejo instead currently requires you generate your own app token and use that instead, as the auto-generated one lacks permissions over packages. (https://codeberg.org/forgejo/forgejo/issues/3571)

    2. Depending on your infrastructure, it might just be impossible to make the various Docker-related actions (such as https://code.forgejo.org/docker/build-push-action) work. As an example, my infrastructure outlined below is one such case where those actions simply do not work.

    Bare Metal (Debian 12) /
    ├─ Rootless Podman/
       ├─ Forgejo
       ├─ Forgejo Runner
       ├─ Podman-in-Podman (Inner Podman also Rootless)/
          ├─ <Actions Containers Run Here>
    
    * If you use rootful Docker with Docker-in-Docker, those actions will then work as expected. It is just that attempting to make them work with Rootless Podman (at least the version that ships with Debain 12) currently seems to be impossible.