Just a regular Joe.

  • 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle


  • Not everything will be open source. For whatever reason, they decided to make this obfuscator open source. It might also just be an interesting side project that someone got permission to release.

    Obfuscation can make it harder to reverse engineer code, even if the method is known. It might also be designed to be pluggable, allowing custom obfuscation. I haven’t checked.

    We also know that obfuscation isn’t real security … but it’s sometimes it is also good enough for a particular use case…


  • Except my crazy relative (just 1, thank dog) also has telegram and feels the urge to forward every damn whackjob conspiracy theory reinterpretation of truth that they find to me and my wife, despite us never replying except to ask them to stop. eg. Cloud seeding, windmills and electric cars are responsible for destroying the atmosphere (not co2 and other greenhouse gases); Bill Gates etc. are spreading microchips through vaccinations; judges ruling that measles doesn’t exist; Ukraine is full of nazis; and yes, even regurgitated feelgood fairy tales and random cat pictures from Facebook. So glad they are in a country far far away from me. They “do their own research”, of course.

    So bloody sad that so many people are in a similar situation of avoiding friends and family for their own sanity (and sometimes safety).


  • But not Fire tablets (kids profile) or Samsung TV or many others that Plex currently supports.

    JellyFin android phone app’s UI is a little weird at times, but does work pretty well for me.

    What I would adore from any app would be an easy way to upload specific content and metadata via SFTP or to blob storage and accessible with auth (basic, token, or cloud) to more easily share it with friends/family/myself without having to host the whole damn library on the Internet or share my home Internet at inconvenient times.

    Client-side encryption would be a great addition to that (eg. password required, that adds a key to the key ring). And of course native support in the JellyFin/other apps for this. It could even be made to work with a JS & WASM player.





  • Encryption will typically be CPU bound, while many servers will be I/O bound (eg. File hosting, rather than computing stuff). So it will probably be fine.

    Encryption can help with the case that someone gets physical access to the machine or hard disk. If they can login to the running system (or dump RAM, which is possible with VMs & containers), it won’t bring much value.

    You will of course need to login and mount the encrypted volume after a restart.

    At my work, we want to make sure that secrets are adequately protected at rest, and we follow good hygiene practices like regularly rotating credentials, time limited certificates, etc. We tend to trust AWS KMS to encrypt our data, except for a few special use cases.

    Do you have a particular risk that you are worried about?


  • Joe@discuss.tchncs.detoSelfhosted@lemmy.worldSecrets Management
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 months ago

    Normally you wouldn’t need a secrets store on the same server as you need the secrets, as they are often stored unencrypted by the service/app that needs it. An encrypted disk might be better in that case.

    That said, Vault has some useful features like issuing temporary credentials (eg. for access to AWS, DBs, servers) or certificate management. If you have these use-cases, it could be useful, even on the same server.

    At my work, we tend to store deployment-time secrets either in protected Gitlab variables or in Vault. Sometimes we use AWS KMS to encrypt values in config files, which we checkin to git repositories.







  • Grey-stubble Gen-X’er here… The 80s and (moreso for me) 90s were a great time to get into tech. Amiga, DOS, Win3.11, OS/2, Linux… BBS’s and the start of the Internet, accompanied by special interest groups and regular in-person social events.

    Everyone was learning at the same time, and the complexity arrived in consumable chunks.

    Nowadays, details are hidden behind touchscreens and custom UXs, and the complexity must seem insurmountable to many. I guess courses have more value now.





  • Welcome to the world of Carrier Grade NAT. 100.64.0.0/10 is reserved for this.

    If you are lucky, you also have an IPv6 address. The catch is you need IPv6 on the client-side too.

    A VPS or similar running wireguard and a proxy might bridge the gap.

    It might also be possible to ask your provider for some port forwarding. Probably not, but check anyway.

    Good luck!