John - I was familiar with the encryption command, we used it to generate a key for securing a website hosted by a copy of 4D, however the documentation talks about browsers. We would want to be sending files to another website via SFTP. Now we send similar files via regular 4D FTP commands in the Internet Commands component. Would we need a new private/public key pair for this? We also use a client certificate supplied to us for encrypting payments via LAUNCH EXTERNAL PROCESS using PHP cURL. Would that be the same type of thing we need for SHTP?
Again, any help/clues welcome. JJ > On Sep 13, 2017, at 1:18 PM, Janet Jonas <[email protected]> wrote: > > Thanks, John for the link to the key creation information. > > What do you launch with LEP? > > JJ > >> On Sep 13, 2017, at 12:00 PM, [email protected] >> <mailto:[email protected]> wrote: >> >> Message: 7 >> Date: Wed, 13 Sep 2017 12:17:07 -0500 >> From: John DeSoi <[email protected] <mailto:[email protected]>> >> To: 4D iNug Technical <[email protected] <mailto:[email protected]>> >> Subject: Re: SFTP - Native to 4D? >> Message-ID: <[email protected] >> <mailto:[email protected]>> >> Content-Type: text/plain; charset=us-ascii >> >> >>> On Sep 13, 2017, at 10:27 AM, Janet Jonas via 4D_Tech <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Does 4D have any native capability to do SFTP file transfers and/or >>> generate a SSH-2 RSA public and private key pair? >> >> 4D does not have any native capability to SFTP. For the Mac I ended up using >> curl via LAUNCH EXTERNAL PROCESS. >> >> 4D can generate RSA key pairs. >> >> http://doc.4d.com/4Dv16/4D/16.2/GENERATE-ENCRYPTION-KEYPAIR.301-3434177.en.html >> >> <http://doc.4d.com/4Dv16/4D/16.2/GENERATE-ENCRYPTION-KEYPAIR.301-3434177.en.html> >> >> John DeSoi, Ph.D. > ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
