• 0 Posts
  • 46 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle










  • In the last I had very little success rate of those uninstall tools to actually do their job in full. A lot of time they delete some data but almost always they leave some trash behind.

    And in the first place, I stopped trusting those external uninstall binaries, they could be designed to remove not only app data but remove your personal data, steal data from your PC or infect it (even if just to investigate why you are uninstalling).


  • One of the reason is that apps can place their files in any place they want so the app manager is not aware of those locations.

    Even if it would know then the user still would need a way to remove the app without deleting data, imagine installing Developer IDE or chat app and uninstall process would remove your chats or projects. Imagine app dev accidentally set the “directory that store app data” to /home, it would be bad.

    I not once uninstalled app to install different (for example older) version due to bugs in new one.

    Having the logic allowing to optionally delete data would introduce additional complexity so most old package managers never introduced that feature.

    But I agree that we should slowly introduce a way to to that. Some app managers that manage flatpaks now allow to delete user data after uninstalling app, this now could be done universally because apps installed using flatpak store their data in their own separated/dedicated directory that flatpak engine know about so (unless you give permissions to access other location) thw manager know where the app store data so can offer easy way to remove it.


  • kolorafa@lemmy.worldtoLinux@lemmy.mlRunning Arch in chroot
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    4 months ago

    Container is just a term for a set of isolation solutions bundled together.

    Like file system isolation (chroot), network isolation, process isolation, device isolation…

    One of them is ofc chroot, yes container use exactly the same chroot functionality.

    So to answer your question, no, you don’t need full isolated container. You can use only chroot.

    You just need to pass all required devices ( and match the driver version running in kernel with your files in container and (avoid) more than one app having full unrestricted access to GPU as that would result in issues (but dont know the details so can’t help you with that)).



  • The only reason ssh client would “hang” without any output is when it’s waiting for external key storage to allow access. It’s designed that way to give user some time to approve access to key storage.

    It sometimes happen that the installed key storage is broken in a way that it fails to show user modal, for any reason (showing on wrong screen, wrong desktop, wrong activity, wrong framebuffer, …)

    One solution (that you already did) is to change the SSH agent env variable to point to different key storage.

    Another would be (if possible) to uninstall the broken key storage if you don’t use it. But it is sometimes needed/used by other apps.

    It’s overall good to notify/open bug on your distro issue tracker to notify that some packages are missconfigured (maybe have missing dependencies) or conflicts with other ones.




  • Totally agreed, but there are pros and cons.

    File - harder to steal but once stolen hacker can bruteforce it as much as it wants. Web service - with proper rate limits (and additional IP whitelist so you can only sync on VPN/local network) - its harder to bruteforce. (But yes, you (sometimes) have also full copy locally in the local client, but …)

    If it was only for me I probably would also go with KeePass as you will not update the same db at the same time, but with with multiple users it’s getting unmanageable.

    I just got triggered as those CVEs are not that bad due to the nature that the app encrypts stuff on the client side so web server is more like shared file storage, while your answer suggested to switch to a solution that doesn’t work for a lot of people (as we already tried that).