🇨🇦

  • 9 Posts
  • 503 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle
  • Most of my web services are behind my vpn, but there are a couple I expose publicly for friends/family to use. Things like emby, ombi, and some generic file sharing with file browser.

    One of these has a long custom path setup in nginx which, instead of proxying to the named service, will ask for http basic auth credentials. Use the correct host+path, then provide the correct user+pass, and you’ll be served an openvpn configuration file which includes an encrypted private key. Decrypt that and you’ve got backdoor vpn access.


  • Darkassassin07@lemmy.catoScience Memes@mander.xyzREVENGE
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    11
    ·
    2 days ago

    Maybe, but the homeless crackhead shambling through the lot at 3am like a zombie doesn’t give a fuck and will kick that thing as hard as he can muster.

    Move it anyway; at least it will have a chance instead of painting a massive target on it with those cones.


  • I keep vaultwarden behind a vpn so it’s not exposed directly to the net. You don’t need a constant connection to the server; that’s only needed to add/change vault items.

    This does require some planning though; it’s easy to lock yourself out of your accounts when you’re away, if you don’t incorporate a backdoor of some kind to let yourself in in an emergency. (lost your device while away from home for example)

    My normal vpn connection requires a private key and a password that’s stored in my vault to decrypt it. I’ve setup a method for retrieving a backup set of keys using a series of usernames, emails, passwords, and undocumented paths (these are the only passwords I actually memorize); allowing me to reach vaultwarden where I can retrieve my vault with the data needed to login to everything else properly.


  • Usually that does the trick for me too; but this morning it just would not cooperate no matter what I tried.

    Seems to be playing ball again, for now.

    I have a feeling this is more to do with Android/Google not wanting to give up control more than anything. If googles stuff always works, but third party stuff is mysteriously always glitchy; users are going to gravitate to google and their ever growing monopoly…







  • I’m so tired of seeing this overblown reaction to ancient non-news.

    Yes, there are some minor vulnerabilities in Jellyfin; but they really really aren’t concerning.

    Unauthenticated, a random person could potentially (with some prior knowledge of this specific issue, and some significant effort randomly generating media UUIDS to tryout) retrieve/playback some media unauthorized. THATS IT. That’s the ONLY real concern. And it’s one you could mitigate with a fail2ban filter if you were that worried about it.

    The other ‘issues’ here, are the potential for your already authenticated users to attack each others settings. Who do you share your server with that you’re concerned about them attacking each other???

    Put this to bed and stop fussing over it. It’s genuinely not worth your time or attention. Exposing Jellyfin to the net is fine.

    Dev comment on the situation: (4 days ago) https://github.com/jellyfin/jellyfin/issues/5415#issuecomment-2825240290


  • The three of them are all pretty similar, achieving the same goal; whatever works for you.

    I’ve never had an issue with Ombi, so I’ve stuck with it. I actually use Emby instead of Jellyfin, so Overseerr isn’t an option, and I’ve just not had a reason to try out Jellyseer over what’s already setup and working.

    Prowlarr is definitely a good recommendation. I used Jackett for the longest time; but being able to modify indexers in one place, then have it propagate to the rest of the stack is so much nicer. It lists a ton of indexers to look into too, if you need more.


  • The arrs are pretty light weight; the memory use can add up when you run several of them with really large libraries alongside other projects, but otherwise I hardly notice them running in the background. You don’t need any sort of special hardware; this stuff will run on an old laptop you shove in the corner and ignore.

    The part that really takes processing power is transcoding media between formats when streaming it to clients, but that’s Emby/Jellyfins job.



  • Torrents have two options:

    Ideally you use Hardlinking - This creates a ‘copy’ of the file that’s just a link to the original data, instead of actually duplicating it. This only works when both ‘copies’ are kept on the same drive/filesystem; but gives you two versions so you can leave one available to seed and have one renamed and sorted away.

    Failing that, it can fallback to plain duplicating the files. One copy kept to seed, and one copy sorted away.

    Personally, I’ve switched to usenet for 99% of downloads, so seeding isn’t really a thing. It’s there as a fallback though.


  • My setup is a conglomeration of a quite a few different pieces; but they are not all required. I’d encourage you to explore, start small and expand into new pieces/areas when you feel comfortable. I started this ~8 years ago with basically 0 knowledge of hosting web services; and just built up the knowledge through exploration over time.

    If all you’re looking to do is watch movies, and you’re happy to play the downloaded media directly on your pc (or move the files around manually, just like manual torrenting); the only piece you need is Radarr.

    Once setup; You tell it what movies you want to watch, it searches for those using the indexers you’ve given it (YourBittorrent, TPB, and BadassTorrents for example), choses the best results out of them all based on things like upload date, seeds, quality descriptors in the title, etc. Then passes that to your torrent/usenet client. Finally it will rename and sort the files into nicely organized media folders for you, once the download client has marked it as complete.





  • Darkassassin07@lemmy.catoAsk Lemmy@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    7 days ago

    I’ve had some good ones and bad ones. Most of the thin plastic film ones are a total waste of time, but there are some really nice gorilla glass screen protectors that will stand up to a whole lot of abuse.

    Yeah, the screens are really tough, but they’re still glass. They will still break if you manage to drop/hit them at the right angle with enough force. A screen protector makes sure that force isn’t directly on the screen. A broken screen protector is much easier/cheaper to replace than the screen.

    A really good one, applied properly; you should essentially never even notice is there, but adds an extra layer of protection for when you do inevitably drop the device.

    Poor quality or poorly applied protectors can be a PITA; interfering with touch detection, air bubbles, scratching really easily, crappy glue, sometimes even comming off during use. You get what you pay for.

    I haven’t really noticed scratches on any device with a decent protector in several years, but I don’t keep things like keys in the same pocket either. They aren’t perfect though; I’ve broken at least two phone screens through the glass screen protector without breaking the protector itself…

    Still, better to have that little bit of extra protection.