• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: February 20th, 2025

help-circle






  • plc@feddit.dktoLinux@lemmy.mlApp Lock under Linux?
    link
    fedilink
    arrow-up
    3
    ·
    4 months ago

    Hm… I struggle to picture what you’re trying to achieve…

    If you are “making an app” as in coding one, you can just have it say ask for a pin in a window as part of starting up.

    You suggest various encryption related solutions… what is your threat model? Do you want to make the identity of the app unknown to others? Normally, autkenticating users is the responsibility of the os/desktop environment, and it would be non-ideomatic for an application to bundle its own auth, except for apps such as a password manager.

    If you want to make an existing system app privileged/secret in some way then that sounds awkward indeed. Normally you’d definitely be using user management facilities (e.g. dedicated users and sudo config) to achieve such a thing.

    If you really do want to make the app “secret” in some sense you could achieve the same thing as with your mac using a combination of loopback block devices (see man losetup) with an encrypted luks volume inside… but depending on the app you might end up in dependency hell if it’s not statically linked.

    ymmv 🙂






  • plc@feddit.dktoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    1
    ·
    5 months ago

    Switched from Windows in 2002, did FreeBSD -> Gentoo -> Ubuntu -> Arch. Finally switched to NixOS in 2012 and never looked back.

    The builtin isolation meant I never actually got properly acquainted with Docker until I switched jobs and had to use it.


  • Selfhoster on NixOS here too.

    Nix (and operating services on a NixOS machine) is a learning curve, and even though tho project is over 10 years old now the semantic differences between the conventional approach to distro design/software development/ops is still a source of friction. But the project has come a long way and lots of popular software is packaged and hostable and just works (when you are aware of said semantic differences)

    But when it works, and it often it does, it’s phenomenal and a very well integrated experience.

    The problem in my exparience with using LLMs to assist is that the declarative nature of Nix makes them prone to hallucination: “Certainly, just go services.fooService.enable = true; in your configuraton.nix and you’re off to the races”. OTOH, because nix builds are hermetic and functional they’re pretty safe to include as a verification tool that something like Claude code can use to iterate on a solution.

    There are some pretty good examples of selfhosting system configurations one can use as inspiration. I just discovered github.com/firecat53/nixos that is an excellent example of a modular system configuration that manages multiple machines, secrets, and self hosted services.