Re: Using the NSUPDATE command

Hello Rob,

Am 14.01.2020 um 15:22 schrieb Rob Berendt <rob@xxxxxxxxx>:

I am going to try the config file.

OK.

EDTF '/home/ROB/.ssh/config'

Interesting side question: In which charset has the config file as well as the key files (it's just a string of characters, not binary!) to be? ASCII? Or EBCDIC? I don't know. Maybe anyone else can shed a light?

Host gdl57
HostName gdl57.dekko-1
User rob
IdentityFile ~/.ssh/rob_gdisys.pub
Which begs the question: Do I use the private key or the public key?
Well, I tried both. I still get prompted for the password.

Private Key. Always. Please try the rename instead. I'm not sure about the syntax.

So I did some more reading and tried this:
PS C:\WINDOWS\system32> Get-Service ssh-agent

Status Name DisplayName
------ ---- -----------
Stopped ssh-agent OpenSSH Authentication Agent


PS C:\WINDOWS\system32> Start-Service ssh-agent
Start-Service : Service 'OpenSSH Authentication Agent (ssh-agent)' cannot be started due to the following error:

Irrelevant. The ssh-agent is just needed if you store your keys on disk with a passphrase. Ssh-Agent can be started per user and then be fed with ssh-add with privkeys and their passphrases interactively. The keys are then stored in memory unencrypted for easier automation.

As told, irrelevan in this scenario (no passphrase).

Now when I try
CALL QP2TERM
ssh gdl57
I get:
ssh: connect to host gdl57.dekko-1 port 22: Connection refused

Connection refused = no ssh daemon on Port 22. Maybe it died from your tests? Please check, start ssh-daemon or or do a reboot. Don't bother with ssh-agent.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc