HOBLink Terminal Edition Quick guide Installation: To install, we will need to download the HOBLink Terminal Edition 5.3.1 link that you were sent from the HOB Support team. Once downloaded, let us run the install.exe After the installation Window has opened follow these steps. 1. Click next 2. Accept the terms of the license agreement and click next 3. If we want to run an x11 session we will want to select HOBLink x11 and click continue 4. You can select full version and enter your product key and click continue 5. Select the installation path you would like to use Click continue 6. Select Yes to create the path 7. After the installation have finished, We will need to select the Program Group for Icons, Select either Common user or Personal user and click continue 8. Select the folder to add the program icons to and click continue The HOB Enterprise Access Connection Configuration window is where we can connect our HOB Terminal Edition to a HOB EA Server which is used to configure users. However, In this quick guide we will not go over this yet. 1. Select Save Locally 2. For ease of use, we are going to store everything in AppData, Select the checkbox, Save user settings in folder <Windows APPDATA> and Select Save & Exit
And lastly for the installation, select yes, to create a registry path which is required for HLLAPI application and HOB Enterprise Access. Select Save and Exit, and Return to Windows on the next screen. If you choose not to select Save user Settings in folder then the local DB path will be C:\program files\hob\terminaledition\portal.db\u1019 For SSH connections, this is where we will store the hobe file which we will configure later in this section. In the next section we will configure an X11 session over SSH. We will be using a SUN Solaris 11 machine as our target servers. 1. Open the installation path, By default C:\Program File\HOB\Terminal Edition 2. Then run HLauncher.exe so we can configure our session 3. Once inside of the HOBLink Terminal Edition Session Manager, select New to configure a new session
4. We will want to create an X Session since we want to do X11 over SSH 5. Click OK Let us configure the connection now 1. On the Connection section, select New 2. Enter the Scheme Name 3. Starting Method will be REXEC/RSH/RLOGIN/SSH 4. Under Multiple IP s we can configure what network adapter our computer should use for the connection. If you have multiple adapters you can mark Select Now, and enter the ip of the local network adapter. Otherwise, if we just have one, we can select Automatic 5. When All X client close, we can restart X server, Close the X server or do nothing 6. Line tracer can be configured if we are having issues with the connection to help us troubleshoot. You can send this tracefile to support@hobsoft.com for us to take a look and help troubleshoot and diagnose the issue
Next, open the REXEC/RSH/RLOGIN/SSH tab 1. Since we want to do an SSH connection, Under Type, Select SSH 2. In the Login section we can enter the IP or Hostname of the target server 3. We can also enter the username and password for a single sign-on experience 4. We can create a logfile if need be. 5. We can set a timeout if there is no connection 6. We can also choose not to run X-Sever 7. Hide X-Startup is useful to select for the client experience, as it will automatically run the Remote Command Line command at startup. Otherwise, not selecting this option, will allow the user or admin to run commands and see the output of those commands for troubleshooting purposes. 8. Select Close 9. We now have the option to create a short cut. If you select No, then you will have to launch this configured session from the HOBLink Terminal Edition Session Manager. Or if you select yes it will take us to another prompt were we can select the localtion of this short cut. I will select my desktop.
Next we will need to select the Remote Command Line section. This will preconfigure a command to run to start the terminal session. 1. Select New 2. Select the Command type you want For Solaris we will choose Sun. For linux we will choose Xterm. It might be necessary to edit the edit the command for the linux users. You will need to determine the path of the xterm program. Typicall it is under /usr/bin/x11/xterm (by default) or /usr/bin/xterm. The rest of the command parameters can be removed for the Xterm Scheme.
For the SUN scheme, we can leave the command as it appears to the default values: Next we will need to configure a Display setting: 1. Click the display section 2. Select New 3. Let us first choose a Name 4. Then select Single Window for now. Multiple Windows will open another session window for each x11 item that is launched. 5. We can then choose the screen size and select the screen assignment. 6. The default settings will work for a test connection You can also go to the Extra Settings tab. The important settings here is GLX Extension. This is to provide and interface between OpenGL and X Window System as well as for extensions to OpenGL. Under the Fonts tab, we can Choose to use Pseudo Fonts and select the font DPI. Under the Color Depth Tab we can choose which the bit rate for the display colors. These can be reduced to help with bandwidth issues.
Clipboard is the last tab for Display settings. We can specify if we want to enable clipboard sharing and a few settings to go along with this. Last we will need to configure an Input Device 1. Open the Input Devices section 2. Select New 3. For the most part the default settings will work just fine However you can specify the language. If you uncheck, Use Default Keyboard you then have the option to Customize the keyboard keys for this session. You can choose the emulate a 3 button mouse if necessary, as well as enable scroll lock, and unlatched scroll lock. You can allow Modifiers for remapping. Enable local number lock and enable unlatched number lock. Lastly, you can configure Alt-Tab and Alt-Esc combination keys. SSH Configuration Next we will need to configure the parameters for SSH. HOB can provide a file called hobe. This is just a file that contains a few parameters for the SSH connection. You can edit this file with a text editor like note pad. Let us go ahead and open it.
Here we can allow or deny kbd interactive authentication which is the Keyboard-interactive Password login method. Next we can select the SSH port we want to use, by default port 22 is used. Next we have password authentication set to yes, this will allow us to use a password instead of a public / private key pair for authentication of our SSH session. Following that we have our Cryptography standards. For Message Authentication Codes, we can specify a list of HMACS we want to use. The order determines which one will be tried first when the client and server negotiate which ones to use. Following that we have Cipher suites. Like the MACs, the list order determines which cipher suit that will be tried first during negotiation of the session. Following that we have strict host key checking which will check the host keys during the connection and authentication process. If strict host checking is enabled then the SSH client connects only to the known hosts with valid SSH host keys that are stored in the known hosts list. Otherwise the connection is rejected. Then we have compression of SSH that can be enabled if you choose. The last option is pub key authentication, which will let us use private and public keys for authentication instead of username and password. I intentionally skipped over preferred authentications. He we have a list of password, keyboard-interactive, and public key. This order determines which method is attempted first. If we are wanting to do password authentication, then password needs to be at the front of the list. Similarly, if we want to do public key authentication, that publickey needs to be specified at the front of this parameter. You can configure this file only once and place it onto any system you want. You will need to store this in the database path you specified during installation. This was selected in the HOB Enterprise Access Connection Configuration Windows. I selected Windows APPDATA, so in my case I will navigate to: C:\users\administrator\appdata\Roaming\hob\te\5.1 And paste the hobe file in this directory. If you choose to not store the items in APPDATA then you will need to select the proper path. For ssh connection, by default this is in C:\program files\hob\terminal Edition\portal.db\u1019 Finally we can double click our shortcut on the desktop or run the session from the Session Manager.
Using Public Key Authentication In this section we will build upon the topics we covered above. The first thing we will need to do is edit the hobe file. Open this in a text editor such as notepad.exe. We must have the option pubkeyauthentication=yes, and we will want to make sure that publickey, is at the beginning of the list for preferredauthentications. Save the file or place it in the database which you have configured during installation. I have chosen to store everything in AppData of the user s profile. Next we will need to generate our Public and Private key and then store the public and private key in the proper location which is the same location as where you stored the hobe file. To do this, we will need to navigate to the Terminal Edition folder in our installation directory. By default this is in C:\program files\hob\terminal Edition and then run sshkeygen.exe. 1. Click Next when the dialog box opens for HOBLink SSH 2. Select Create new key pair files then next 3. Choose between RSA and DSA 4. Choose your key size 5. Then Select next 6. Enter a password 7. The path this needs to be saved to is either the AppData path for the user settings or the database path you specified. Then select next. 8. Select next to start the key generation process
9. Click Finished 10. Click exit to finish the setup Next we will need to open public key file with a text editor and this will need to be added to the SSH configuration file. In linux typically this will be in /etc/ssh/authorizedkeys. For Solaris you can follow this guide: https://docs.oracle.com/cd/e19683-01/817-0365/sshuser-1/index.html Troubleshooting: If you try to run a session, but you are not seeing the command window like you see in the video, enable the following settings. In the connection settings, under the connection tab, When All X clients Close select do nothing. This completes the HOBLink Terminal Edition 5.3.1 Quick guide.