search for: _ssh_

...-i Warning: the RSA host key for 'box5' differs from the key for the IP address '10.3.1.78' Offending key for IP in /root/.ssh/known_hosts:2 Matching host key in /etc/ssh/ssh_known_hosts:2 Are you sure you want to continue connecting (yes/no)? yes 10.3.1.78 This is same one host I _ssh_ to. Is this purely _ssh_ and way to fix it would be 'configuration' or perhaps (ssh &) something else? I don't quite get what exactly is happening here. many thanks, L.

On 2019-07-15 10:56, Dirk Eddelbuettel wrote: > <snip> > > > Don't write passwords down like this. Your error is likely in expecting _ssh_ > authentication over _https_ -- when it works only over ssh. Use the alternate > form for a remote e.g. one that looks like git at github.com:emacs-ess/ESS.git ????? I'm confused.? I changed that line to: ??? ?? ? ?? url = https://git at github.com:sbgraves237/sbgraves237/Ecdat...

Hello. I once read somewhere that it's possible to limit SSH pubkeys to 'tunnel-only'. I can't seem to find any information about this in any of the usual places. I'm going to be deploying a few servers in a couple of days and I'd like them to log to a central server over an SSH tunnel (using syslog-ng) however I'd like to prevent actual logins (hence

...'box5' differs from the key for the IP > address '10.3.1.78' > Offending key for IP in /root/.ssh/known_hosts:2 > Matching host key in /etc/ssh/ssh_known_hosts:2 > Are you sure you want to continue connecting (yes/no)? yes > 10.3.1.78 > > This is same one host I _ssh_ to. > Is this purely _ssh_ and way to fix it would be 'configuration' or > perhaps (ssh &) something else? > I don't quite get what exactly is happening here. When you create a new ssh host (ie. run sshd) for the first time, a host key is created that uniquely identifies...

...raves237/Ecdat.git > > > On Mon, 2019-07-15 at 11:41 -0500, Spencer Graves wrote: >> On 2019-07-15 10:56, Dirk Eddelbuettel wrote: >>> <snip> >>> >>> >>> Don't write passwords down like this. Your error is likely in >>> expecting _ssh_ >>> authentication over _https_ -- when it works only over ssh. Use the >>> alternate >>> form for a remote e.g. one that looks like git at github.com:emacs- >>> ess/ESS.git >> I'm confused. I changed that line to: >> >> >>...

...h://git at github.com:sbgraves237/Ecdat.git<mailto:ssh://git at github.com:sbgraves237/Ecdat.git> On Mon, 2019-07-15 at 11:41 -0500, Spencer Graves wrote: On 2019-07-15 10:56, Dirk Eddelbuettel wrote: <snip> Don't write passwords down like this. Your error is likely in expecting _ssh_ authentication over _https_ -- when it works only over ssh. Use the alternate form for a remote e.g. one that looks like git at github.com:emacs<mailto:git at github.com:emacs>- ess/ESS.git I'm confused. I changed that line to: url = https://git at github.com:sbgr...

Hi gurus! First time post: Scenario want to talk to daemon locked behind a firewall using encrypted transfer of files. Have daemon setup on port 10001. Do not have NC, do not have root access. Client command : rsync -avzul -e "ssh -vvv -l username" /home/users/blah/ rsync://lrem02:10001::/live As you can see the connection is set to talk to lrem02 on port 10001 however i want to

????? Thanks to Ott and others, I now have separate GitHub repositories, one for each of the packages combined in the Ecdat R-Forge project.? In case it might help others in the future, I will summarize here key things I did to make this transition: ??? ??????? 1.? I first copied the "Ecfun" package into its own directory on my local computer and created a separate GitHub

For systems where the local hostname is obtained as a short name without domain, there should be a ssh_config option "DefaultDomain" as in ssh-3.x from ssh.com. For the server, there might be a corresponding option in order to strip the domain name from the remote client name (if it matches the server's DefaultDomain) for use in auth_rhost2, since netgroups usually contain short