• 0 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: August 12th, 2024

help-circle

  • I realy dont think that’s a thing. End-user login security is a tiny footnote on page 729 of the 2000+ page security document of a large company’s cyber security department. Switching that to passkeys will not change anything about how the company handles security. AI will. But not passkeys.

    And as we have seen many times, companies have been bad with security already and many password databases have been breached. Having a tool that limits the impact of bad security is a good thing.


  • groet@feddit.orgtoSelfhosted@lemmy.world•Immich vs Ente ?
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    My experience with ente was that it is horribly slow. It also lacks any feature to upload a large number of photos at once. I just never bothered uploading my 10k pictures I have taken over the last 15 years because it would have had to transfer them to a phone and then have the app open for a few weeks. No rclone or any other reasonable way to upload from a computer other than browser (which just doesn’t work for more than a few images)



    1. is there a reason you don’t use podman instead of rootless docker?
    2. can you run patchmon inside of docker and mount the socket to the original path inside of the container?
    3. the symlink has the file permissions of the file it points to. If the socket is owned by a user, so will the symlink, even if you used root/sudo to create the link. (technically the symlink will be owned by root, but the permissions on a symlink are ignored and the permission of the target are used)
    4. as long as you don’t change any permissions on /var/run or on the docker.sock to be more permissive than they are now, there is functionally no difference in security
    5. If you or someone else on the system tries to run docker with a different user/root, the symlink will likely cause issues



  • groet@feddit.orgtoPrivacy@lemmy.ml•*Permanently Deleted*
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    7 months ago

    I heard the wisdom once that you should self host everything except for email. I’m sure there are great tools to make it manageable but the effort/gain is just very high.

    Just find a email provider that let’s you connect your own domain, use wildcards, etc.

    Of course email is pretty central to most digital identities, as most accounts can be reset through email. So if you absolutely want to be sure you control your identity you must self host email (but you also must own the authoritative DNS for that domain so you must register directly with the TLD and not through a registrar …)


  • Terminology: revoked means the issuer of the certificate has decided that the certificate should not be trusted anymore even though it is still valid.

    If a attacker gets access to a certificates key, they can impersonate the server until the validity period of the cert runs out or it is revoked by the CA. However … revocation doesn’t work. The revocation lists arent checked by most clients so a stolen cert will be accepted potentially for a very long time.

    The second argument for shorter certs is adoption of new technology so certs with bad cryptographic algorithms are circled out quicker.

    And third argument is: if the validity is so short you don’t want to change the certs manually and automate the process, you can never forget and let your certs expire.

    We will probably get to a point of single day certs or even one cert per connection eventually and every step will be saver than before (until we get to single use certs which will probably fuck over privacy)



  • You don’t need something ever. Sometimes you just want something because the alternative is realy bad. I don’t need to eat. I want to eat because I don’t want to starve.

    I want to watch a movie with my partner at the agrees time because otherwise they will be mad. I want to access my digitalized documents to send a letter in time because otherwise I will have to pay late fees. I want to access my gameserver because that’s the one time a week I get to have fun with my friends from my college time.

    There are many situations where I’d rather do the thing I want instead of doing maintenance.




  • That is the smallest scale of self hosting. The server and the client are the same device. It is also the most insecure way as you probably don’t have any backups and very limited storage space.

    Actually self hosting is the next step when you decide you want 5+ TB of data and have it automatically create backups. Digital storage media degrade pretty quickly and if you just have your movies on a hard drive in your computer, after 5-10 years you might start to lose quality or some files completely.


  • That is factually incorrect. Many websites would literally stop working. Not “mildly confuse”, but “be unusable”.

    You ever logged in to a website? That’s a cookie. Ever used an online shopping cart? That’s a cookie. Ever changed a websites language in a dropdown? That’s a cookie.

    All these cookies are first party. There are also essential third party cookies for thing like SSO (“sign in with google/Facebook/github/etc”)

    Tell your browser to reject 100% of cookies and tell me how much fun that is.

    “Legitimate Interest” is the bullshit term. Why does an ad company have a legitimate interest to my data? That should be removed from the law.



  • wg-quick creates a systemd service for each wireguard config you have. So if you set up a tunel called wg0, you should be able to run ‘sudo systemctl enable wg-quick@wg0’ This will make your tunnel connect on every boot. I have the same setup on my proxmox, so i can reach certain services of my homelab proxied through a root server (the other end of the wireguard tunnel)


  • Decryption is not related to root permission.

    If the ENCRYPTED drive is mounted to the container, then the container can decrypt it.

    If the DECRYPTED drive is mounted to the container, then the container never knows it was encrypted in the first place.

    Second case is easier BTW. Just mount the drive on your host, type in the encryption password and you get a new, unencrypted drive. Specify this new drive in your docker compose/docker file.