I second the recommendation. You don’t even need to know much about Postman to use it. It’s got a zillion features, but, at least in my experience, it always seems to know what I want to do after minimal fiddling.
Tom Benedict > On Nov 21, 2019, at 13:13, Kirk Brooks via 4D_Tech <[email protected]> > wrote: > > Hey Peter, > I can't give you the specific answer but if you haven't already I'd > recommend installing Postman <https://www.getpostman.com/>. > How that may help you is you can look at exactly what is being sent and > received from the destination. The first thing I'd do is capture the > traffic with FileZilla and compare it to the traffic between 4D. That will > at least show you what's different between the two. > > Hope this helps > > On Thu, Nov 21, 2019 at 12:44 PM Peter Hay via 4D_Tech <[email protected]> > wrote: > >> Hi, >> >> I'm using Miyako's CURL-FTP plugin to try and connect to an SFTP site using >> SSH keys, but I keep getting an error 67. I've tried the same settings >> using CURL from the command line, and get the same error. I've also tried >> the same thing using FileZilla and it works perfectly, so I know the SSH >> Keys files are in good shape. >> >> When I run CURL form the command line in verbose mode, here's what I get; >> >> curl -u THEUSER: --key "C:\SSH_Private.ppk" --pass "ThePassword" --pubkey >> "C:\SSH_Public.key" sftp://ftp.thesite.com/OUT/ -v -k >> * Trying 123.456.789.0 :22... >> * TCP_NODELAY set >> * Connected to ftp.thesite.com (123.456.789.0) port 22 (#0) >> * SSH MD5 fingerprint: 4dc2acee06bdaa70fc67412187362428 >> * SSH authentication methods available: >> publickey,password,keyboard-interactive >> * Using SSH public key file 'C:\SSH_Public.key' >> * Using SSH private key file 'C:\SSH_Private.ppk' >> * SSH public key authentication failed: Invalid key data, not base64 >> encoded >> * Failure connecting to agent >> * Authentication failure >> * Closing connection 0 >> curl: (67) Authentication failure >> >> >> I've obfuscated some of the details, but you get the idea. >> >> The main problem seems to be that CURL thinks the Public Key should be >> Base64 encoded. I'm pretty sure that it is. It looks like this; >> >> ---- BEGIN SSH2 PUBLIC KEY ---- >> AAAAB3NzaC1yc2EAAA ... 4QvuPGkd+ocvyWQ== >> ---- END SSH2 PUBLIC KEY ---- >> >> >> As I said, FileZilla works fine with all of this. >> >> Does anyone have any idea what the issue may be? >> >> -- >> Pete Hay >> Managing Director >> Foreground Software Limited >> New Zealand > > - > Kirk Brooks > San Francisco, CA ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
