generated pub / pri key on HCISITEDIR of client
copied pub key to server-cloverleaf in /home/hci/.ssh
verified permissions
configured thread ib_usr_sftp -> fileset-ftp FTP options SFTP
FTP Host Information : server-cloverleaf port 22
we start the ib_usr_sftp on the client-cloverleaf ..it goes to up :-/ and
grabs the file on the server-cloverleaf box ?….
that may sound great….but when we intentionally corrupt the key files on either box…..it continues to work? as though we’re using simple ftp
hcilicstatus on client-cloverleaf:
Add-on Modules
New Feature: no
cl-aom-batch-process: no
cl-aom-caa-direct: no
cl-aom-caa-ws: no
cl-aom-ftps: yes
cl-aom-gmon: yes
cl-aom-ihb: no
cl-aom-master: no
cl-aom-msgwarehouse: no
cl-aom-odbc-mw: no
cl-aom-odbc-tcl: no
cl-aom-screen-scraper: no
cl-aom-sec-advanced: yes
cl-aom-sftp: yes
cl-aom-site-doc: yes
cl-aom-ssl: yes
cl-aom-webservices: yes
hcilicstatus on server-cloverleaf
Add-on Modules
New Feature: no
cl-aom-batch-process: no
cl-aom-caa-direct: no
cl-aom-caa-ws: no
cl-aom-ftps: yes
cl-aom-gmon: yes
cl-aom-ihb: no
cl-aom-master: no
cl-aom-msgwarehouse: no
cl-aom-odbc-mw: no
cl-aom-odbc-tcl: no
cl-aom-screen-scraper: no
cl-aom-sec-advanced: yes
cl-aom-sftp: yes
cl-aom-site-doc: yes
cl-aom-ssl: yes
cl-aom-webservices: yes