![]() ![]() It'll ask if you want a passphrase that has to be entered each time you use the key. (Sidebar: Never ever, ever, ever give anybody your private key.) Just run: ssh-keygen This comprises of a public key and a private key. It's fairly powerful stuff and quite simple to get started.įirst you need to generate a key for your user. # and ChallengeResponseAuthentication to 'no'.Are you just bothered about punching in your details each time you can use SSH key authentication so your user can log into other computers without a password. # PAM authentication, then enable this but set PasswordAuthentication # If you just want the PAM account and session checks to run without # the setting of "PermitRootLogin without-password". ![]() ![]() # PAM authentication via ChallengeResponseAuthentication may bypass # be allowed through the ChallengeResponseAuthentication and If this is enabled, PAM authentication will # Set this to 'yes' to enable PAM authentication, account processing, # Change to yes to enable challenge-response passwords (beware issues with # To disable tunneled clear text passwords, change to no here! # Don't read the user's ~/.rhosts and ~/.shosts files # Change to yes if you don't trust ~/.ssh/known_hosts for # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts ssh/authorized_keys2 to be disregarded by default in future. # OpenSSH is to specify options with their default value where # The strategy used for options in the default sshd_config shipped with # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin # This is the sshd server system-wide configuration file. Home computer sshd_config: # $OpenBSD: sshd_config,v 1.101 4 07:19:07 djm Exp $ # list of available options, their meanings and defaults, please see the # Site-wide defaults for some commonly used options. # configuration file, and defaults at the end. ![]() # Thus, host-specific definitions should be at the beginning of the # Any configuration value is only changed the first time it is set. # Configuration data is parsed as follows: # users, and the values can be changed in per-user configuration files Work computer ssh_config: # This is the ssh client system-wide configuration file. Apologies in advance if I've missed something obvious. So maybe somebody can point out an obvious error I am making? Any advice would be appreciated. I also searched all the forums for some tips for an hour or so but no luck. I tried a number of things in the /etc/ssh/sshd_config file on the home computer and the /etc/ssh/ssh_config on the work computer. I know that it is not a password problem, because the direct ssh connection worked. So then I do the following from my work computer: ssh -R 44455:localhost:22 then following occurs: password: So I know that the two computers can communicate with each other. the following works from my work computer: ssh -p 44455 I have successfully set up the port forwarding (of port 44455 in this case) on my home router, such that I can log in to my home computer from work via ssh, so I know that there is a valid connection, i.e. (Unfortunately I can't ssh to my work computer directly, due to their policy). I am trying to set up a tunnel between port 22 on my work computer (Ubuntu 19.10) to port 44455 on my computer at home (Ubuntu 18.04), so that I can ssh to my work computer from home. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |