View Single Post
Old 13-Sep-2019, 1:59 AM   #12
TheFu
Junior Member
 
Join Date: Aug 2012
Posts: 10
Quote:
Originally Posted by GroundUrMast View Post
TheFu, Thanks for sharing this. Given the hardware transcoding capability of my HDHomeRun EXTEND
(Model: HDTC-2US), I had not considered the need for ffmpeg. Using either the command line or GUI to launch vlc I have had no problem choosing transcoding when I have been at locations that lacked adequate bandwidth for streaming an MPEG2 HD program.

My reason for using a non-standard port to transport SSH across the Internet was based on reducing the security risk of port scans by amateur hackers.
I have HDHR2, HDHR4 and an HDHR-Quad. The 4 and Quad are DLNA "servers". The HDHR2 uses whatever the old-school protocol was that needed special drivers that required compiling and linking. Since SiliconDust changed all the names I can't keep up with what each does. Their overview page is only slightly useful. https://www.silicondust.com/hdhomerun/


For any lurkers, definitely NOT using 22/tcp for ssh is a smart idea. Running fail2ban and only allowing ssh-keys for authentication will effectively block any brute force attempts that happen to find the high port. If your WAN router supports it, having it do the port translation to the LAN system 22/tcp for ssh means just installing fail2ban doesn't need any extra configuration. Setting up ssh-keys and pushing the public key to the remote ssh-server is really easy on Unix these days.
Code:
ssh-keygen -t ed25519
ssh-copy-id -i ~/.ssh/id_ed25519.pub userid@remote
The ed25519 type is about as secure as 3k RSA ssh-keys.
TheFu is offline   Reply With Quote