I know that the private key needs to be secured but with an ssh key exchange connection the partner needs your public key in their authorized_keys file and the partner's RSA fingerprint needs to be in your known_hosts file.

Given that probably any system is breakable the ssh key exchange offers a pretty good solution.

J

On 11/26/2019 12:44 PM, Patrik Schindler wrote:
Hello Jerry,

Am 26.11.2019 um 21:14 schrieb Jerry Draper <midrangel@xxxxxxxxxxxxx>:

However, the userid/pw is stored in plain text in the FTP script.
True? It is on our system.

Yes, mostly true. See comment from John.

Let's put it this way: If anybody copies the ssh private key, he can also utilize that one for abuse. Ssh-Keys for automation are most often not protected by passwords, so automation doesn't need passwords to be supplied. Thus, the key is unencrypted and ready for use.

In general, it's possible to use ssh-agent. This is a background task to which you can add encrypted (password protected) keys and these will be stored in memory in unencrypted form. (I'm doing that manually after reboots.) Through environment variables, ssh clients (sftp, scp, ssh) and ssh-add (for adding keys) find a local socket for communicating with the ssh-agent. Honestly, I don't know how much of this Linux/Unix specific stuff also applies to PASE, though.

:wq! PoC

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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.