• 0 Posts
  • 6 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • I generally do a few things to protect SSH:

    1. Disable password login and use keys only
    2. Install and configure Fail2Ban
    3. Disable root login via ssh altogether. Just change “permit root login” from “no password” to just “no”. You can still become root via sudo or su after you’re connected, but that would trigger an additional password request. I always connect as a normal user and then use sudo if/when I need it. I don’t include NOPASSWD in my sudoers to make certain sudo prompts for a password. Doesn’t do any good to force normal user login if sudo doesn’t require a password.
    4. If connecting via the same network or IPs, restrict the SSH open port to only the IPs you trust.
    5. I don’t have SSH internet visible. I have my own Wireguard server running on a separate raspberry pi and use that to access SSH when I’m away, but SSH itself is not open to the internet or forwarded in the router.



  • I’m not sure. I’ve only noticed it on my TV and have even noticed it with content that I personally ripped from DVDs or Blurays and encoded to x265 or AV1. Since it only affects the TV apps I’m wondering if it isn’t a lack of support for some color space or something by the TV hardware because when I’m encoding I don’t usually change anything about the dimensions, color space, frame-rate, etc., just the codec and quality. If the video is 10 bit, I encode it as 10 bit. If it’s HDR, I pass that thru. I’ve checked with the mobile and desktop app and the web player on content the TVs had issues with and those same files played fine everywhere else, so it’s something specific to the LG and Roku apps for Plex.