Recent Posts

Pages: [1] 2 3 ... 10
1
mod_tls / make error on proftpd-1.3.6rc4
« Last post by unnikpr on Today at 04:21:10 pm »
Getting error while compiling with tls on proftpd


parameter: ./configure --prefix=/usr/local/proftpdrc --enable-openssl --with-modules=mod_ratio:mod_readme:mod_rewrite:mod_wrap2:mod_ifsession:mod_sftp:mod_exec:mod_vroot:mod_tls --with-includes=/usr/include/openssl --with-libraries=/usr/include/openssl

make

cd modules/ && make static
make[1]: Entering directory `/usr/local/src/proftpd-1.3.6rc4/modules'
gcc -DHAVE_CONFIG_H  -DLINUX  -I.. -I../include  -g2 -O2 -Wall -fno-omit-frame-pointer -c mod_tls.c
mod_tls.c: In function ‘tls_tlsext_cb’:
mod_tls.c:3169: error: ‘TLSEXT_TYPE_server_name’ undeclared (first use in this function)
mod_tls.c:3169: error: (Each undeclared identifier is reported only once
mod_tls.c:3169: error: for each function it appears in.)
mod_tls.c:3173: error: ‘TLSEXT_TYPE_max_fragment_length’ undeclared (first use in this function)
mod_tls.c:3177: error: ‘TLSEXT_TYPE_client_certificate_url’ undeclared (first use in this function)
mod_tls.c:3181: error: ‘TLSEXT_TYPE_trusted_ca_keys’ undeclared (first use in this function)
mod_tls.c:3185: error: ‘TLSEXT_TYPE_truncated_hmac’ undeclared (first use in this function)
mod_tls.c:3189: error: ‘TLSEXT_TYPE_status_request’ undeclared (first use in this function)
mod_tls.c: In function ‘tls_init_server’:
mod_tls.c:5107: warning: unused variable ‘server_ec_cert’
mod_tls.c: In function ‘tls_accept’:
mod_tls.c:5967: warning: implicit declaration of function ‘SSL_set_tlsext_debug_callback’
make[1]: *** [mod_tls.o] Error 1
make[1]: Leaving directory `/usr/local/src/proftpd-1.3.6rc4/modules'
make: *** [modules] Error 2
2
Not sure. is it with configuration. i have posted above. i am using FileZilla lates version. is any client configuration need to do ?

Regards,
Unni.
3
Thank you!   The detailed logging helps.  From that log, we see:

  mod_sftp/0.9.9[8582]: error reading from client (fd 0): Connection reset by peer
  mod_sftp/0.9.9[8582]: disconnecting client (Connection reset by peer)
  mod_sftp/0.9.9[8582]: aborting 1 unclosed file handle

This is indicating that the client is the one closing the connection abruptly, not mod_sftp.  Do the client logs show anything else about why it might be closing the connection like this?
4
I have enable the trace log and sftp and the log while fail as follows,

SFTP log:
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session key exchange: diffie-hellman-group-exchange-sha256
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session server hostkey: ssh-rsa
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session client-to-server encryption: aes256-ctr
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session server-to-client encryption: aes256-ctr
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session client-to-server MAC: hmac-sha2-256
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session server-to-client MAC: hmac-sha2-256
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session client-to-server compression: none
2017-03-23 06:58:00,657 mod_sftp/0.9.9[8582]:  + Session server-to-client compression: none
2017-03-23 06:58:21,686 mod_sftp/0.9.9[8582]: error reading from client (fd 0): Connection reset by peer
2017-03-23 06:58:21,686 mod_sftp/0.9.9[8582]: disconnecting client (Connection reset by peer)
2017-03-23 06:58:21,686 mod_sftp/0.9.9[8582]: aborting 1 unclosed file handle
2017-03-23 07:58:21,897 mod_sftp/0.9.9[8588]: sent server version 'SSH-2.0-mod_sftp/0.9.9'
2017-03-23 07:58:21,897 mod_sftp/0.9.9[8588]: received client version 'SSH-2.0-PuTTY_Local:_Mar_20_2017_16:43:56'
2017-03-23 07:58:21,897 mod_sftp/0.9.9[8588]: handling connection from SSH2 client 'PuTTY_Local:_Mar_20_2017_16:43:56'
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session key exchange: diffie-hellman-group-exchange-sha256
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session server hostkey: ssh-rsa
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session client-to-server encryption: aes256-ctr
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session server-to-client encryption: aes256-ctr
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session client-to-server MAC: hmac-sha2-256
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session server-to-client MAC: hmac-sha2-256
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session client-to-server compression: none
2017-03-23 07:58:21,919 mod_sftp/0.9.9[8588]:  + Session server-to-client compression: none
2017-03-23 07:58:22,388 mod_sftp/0.9.9[8588]: sending acceptable userauth methods: publickey,password
2017-03-23 06:58:22,414 mod_sftp/0.9.9[8588]: sending userauth success
2017-03-23 06:58:22,414 mod_sftp/0.9.9[8588]: user 'crisp1' authenticated via 'password' method
2017-03-23 06:58:22,415 mod_sftp/0.9.9[8588]: client sent SSH_MSG_IGNORE message (35 bytes)
2017-03-23 06:58:22,513 mod_sftp/0.9.9[8588]: unsupported 'simple@putty.projects.tartarus.org' channel requested, ignoring
2017-03-23 06:58:22,514 mod_sftp/0.9.9[8588]: 'subsystem' channel request for 'sftp' subsystem
2017-03-23 06:58:22,537 mod_sftp/0.9.9[8588]: using SFTP protocol version 3 for this session (channel ID 0)


Trace Log:

2017-03-23 08:00:20,567 [8635] <ssh2:9>: loading host key from file '/etc/ssh/ssh_host_rsa_key'
2017-03-23 08:00:20,568 [8635] <ssh2:4>: using '/etc/ssh/ssh_host_rsa_key' as RSA hostkey
2017-03-23 08:00:20,568 [8635] <ssh2:9>: loading host key from file '/etc/ssh/ssh_host_dsa_key'
2017-03-23 08:00:20,568 [8635] <ssh2:4>: using '/etc/ssh/ssh_host_dsa_key' as DSA hostkey
2017-03-23 08:00:20,568 [8635] <ssh2:7>: client alive checks requested after 15 secs, up to 3 times
2017-03-23 08:00:20,568 [8635] <ssh2:3>: unable to use 'none' cipher: Must be explicitly requested via SFTPCiphers
2017-03-23 08:00:20,569 [8635] <ssh2:3>: unable to use 'none' digest: Must be explicitly requested via SFTPDigests
2017-03-23 08:00:20,569 [8635] <ssh2:9>: sending KEXINIT message to client
2017-03-23 08:00:20,569 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 1 using select(2)
2017-03-23 08:00:20,570 [8635] <ssh2:3>: sent SSH_MSG_KEXINIT (20) packet (760 bytes)
2017-03-23 08:00:20,570 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,571 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)

2017-03-23 08:00:20,572 [8635] <ssh2:5>: handling connection from SSH2 client 'PuTTY_Local:_Mar_20_2017_16:43:56'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^OpenSSH-2\.0.*|^OpenSSH-2\.1.*|^OpenSSH_2\.1.*|^OpenSSH_2\.2.*|^OpenSSH_2\.3\.0.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^OpenSSH-2\.0.*|^OpenSSH-2\.1.*|^OpenSSH_2\.1.*|^OpenSSH_2\.2.*|^OpenSSH_2\.3\.0.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^OpenSSH_2\.3\..*|^OpenSSH_2\.5\.0p1.*|^OpenSSH_2\.5\.1p1.*|^OpenSSH_2\.5\.0.*|^OpenSSH_2\.5\.1.*|^OpenSSH_2\.5\.2.*|^OpenSSH_2\.5\.3.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^OpenSSH_2\.3\..*|^OpenSSH_2\.5\.0p1.*|^OpenSSH_2\.5\.1p1.*|^OpenSSH_2\.5\.0.*|^OpenSSH_2\.5\.1.*|^OpenSSH_2\.5\.2.*|^OpenSSH_2\.5\.3.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^OpenSSH.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^OpenSSH.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '.*MindTerm.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '.*MindTerm.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^Sun_SSH_1\.0.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^Sun_SSH_1\.0.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^2\.1\.0.*|^2\.1 .*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^2\.1\.0.*|^2\.1 .*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^2\.0\.13.*|^2\.0\.14.*|^2\.0\.15.*|^2\.0\.16.*|^2\.0\.17.*|^2\.0\.18.*|^2\.0\.19.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^2\.0\.13.*|^2\.0\.14.*|^2\.0\.15.*|^2\.0\.16.*|^2\.0\.17.*|^2\.0\.18.*|^2\.0\.19.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^2\.0\.11.*|^2\.0\.12.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^2\.0\.11.*|^2\.0\.12.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^2\.0\..*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^2\.0\..*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^2\.2\.0.*|^2\.3\.0.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^2\.2\.0.*|^2\.3\.0.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^1\.2\.18.*|^1\.2\.19.*|^1\.2\.20.*|^1\.2\.21.*|^1\.2\.22.*|^1\.3\.2.*|^3\.2\.9.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^1\.2\.18.*|^1\.2\.19.*|^1\.2\.20.*|^1\.2\.21.*|^1\.2\.22.*|^1\.3\.2.*|^3\.2\.9.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '.*SSH_Version_Mapper.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '.*SSH_Version_Mapper.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against regex '^Probe-.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match regex '^Probe-.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against SFTPClientMatch regex '.*SecureBlackbox.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match SFTPClientMatch regex '.*SecureBlackbox.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against SFTPClientMatch regex '.*EldoS.SSHBlackbox.3.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match SFTPClientMatch regex '.*EldoS.SSHBlackbox.3.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against SFTPClientMatch regex '.*IP.Works.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match SFTPClientMatch regex '.*IP.Works.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against SFTPClientMatch regex '.*ClientSftp'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match SFTPClientMatch regex '.*ClientSftp'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against SFTPClientMatch regex '.*WS_FTP.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match SFTPClientMatch regex '.*WS_FTP.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against SFTPClientMatch regex '.*WinSCP.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match SFTPClientMatch regex '.*WinSCP.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: checking client version 'PuTTY_Local:_Mar_20_2017_16:43:56' against SFTPClientMatch regex 'JSCH.*'
2017-03-23 08:00:20,572 [8635] <ssh2:18>: client version 'PuTTY_Local:_Mar_20_2017_16:43:56' did not match SFTPClientMatch regex 'JSCH.*'
2017-03-23 08:00:20,573 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,592 [8635] <ssh2:20>: SSH2 packet len = 1196 bytes
2017-03-23 08:00:20,592 [8635] <ssh2:20>: SSH2 packet padding len = 8 bytes
2017-03-23 08:00:20,592 [8635] <ssh2:20>: SSH2 packet payload len = 1187 bytes
2017-03-23 08:00:20,592 [8635] <ssh2:19>: waiting for max of 600 secs while polling socket 0 using select(2)
2017-03-23 08:00:20,592 [8635] <ssh2:20>: SSH2 packet MAC len = 0 bytes
2017-03-23 08:00:20,592 [8635] <ssh2:3>: received SSH_MSG_KEXINIT (20) packet
2017-03-23 08:00:20,592 [8635] <ssh2:9>: reading KEXINIT message from client
2017-03-23 08:00:20,592 [8635] <ssh2:3>: first kex packet follows = false
2017-03-23 08:00:20,593 [8635] <ssh2:9>: determining shared algorithms for SSH session
2017-03-23 08:00:20,593 [8635] <ssh2:8>: client-sent key exchange algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,rsa2048-sha256,rsa1024-sha1,diffie-hellman-group1-sha1
2017-03-23 08:00:20,593 [8635] <ssh2:8>: server-sent key exchange algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,rsa1024-sha1
2017-03-23 08:00:20,593 [8635] <ssh2:20>: session key exchange algorithm: diffie-hellman-group-exchange-sha256
2017-03-23 08:00:20,593 [8635] <ssh2:8>: client-sent host key algorithms: ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa,ssh-dss
2017-03-23 08:00:20,593 [8635] <ssh2:8>: server-sent host key algorithms: ssh-rsa,ssh-dss
2017-03-23 08:00:20,593 [8635] <ssh2:20>: session server hostkey algorithm: ssh-rsa
2017-03-23 08:00:20,593 [8635] <ssh2:8>: client-sent client encryption algorithms: aes256-gcm@openssh.com,aes256-ctr,aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-ctr,aes192-cbc,aes128-gcm@openssh.com,aes128-ctr,aes128-cbc,chacha20-poly1305@openssh.com,blowfish-ctr,blowfish-cbc,3des-ctr,3des-cbc,arcfour256,arcfour128
2017-03-23 08:00:20,593 [8635] <ssh2
5
mod_tls / Re: Problem with TLS / MLSD directory changing delay
« Last post by tomsoft on March 22, 2017, 08:51:49 pm »
I second that a backport from Debian stretch to Debian jessie would be highly appreciable. With much hassle I did a 'not so quick & dirty' backport on my own machine, which I tried to summarize. Unfortunately I cannot afford the time for the steps to make such a backport into an official debian.org-one.

At least this allowed me to get the new proftpd version running on my server, without having to use unstable 'ncurses' and 'libc' versions from Debian stretch. The other alternative would be to resort to a competitive FTP server, such as vsftpd, for ftps:// traffic. I would not like to do this because I really like the configuration syntax for proftpd.

Do you know who is the maintainer of Debian packages? I think that such a bug should be fixed/backported even in Debian stable.
To my knowledge, Francesco Lovergine <frankie@debian.org> is the Debian proftpd package maintainer.
6
mod_exec / Re: mod_exec only firing for USER events?
« Last post by mintsoft on March 22, 2017, 02:16:09 pm »
Aha! I've just solved my own problem. In-case other people encounter the same problems:

The ExecLog isn't being populated because it won't be written to a directory that's world-readable (i.e. /tmp) switching that to /var/log/proftpd/execlog.log makes it actually populate.

Secondly that then shows that there's a permissions issue writing to the file in /tmp. The scripts are being executed as the SFTP user that's logged in, for my virtual users that's uid 10000, I was assuming it was run as the proftpd user!

 ;D
7
mod_exec / mod_exec only firing for USER events?
« Last post by mintsoft on March 22, 2017, 09:32:41 am »
Hello,

I'm trying to setup an SFTP server with virtual users which when users upload files, a script is executed to do other stuff with the uploaded file. I'm running on Debian Jessie (meaning proftpd-basic                  1.3.5-1.1+deb8u1). The sftp.conf file is in the conf.d directory so is included by the proftpd.

To prove the idea, I was planning to have my script.sh just get executed on every command for now, so I can see it getting executed and that the arguments are working etc before I plough-on and flesh it out at all. So my "script" is :

Code: [Select]
$ cat ../sftp/script.sh
#!/bin/bash
echo `date --iso-8601=seconds`\:\'"$@"\' >> /tmp/log.log


However when I look at /tmp/log.log all I see is:
Code: [Select]
2017-03-22T09:16:02+0000:'BEFORE 'UNKNOWN' '192.168.1.16' '' '' '' '' '' 'desktop.home' 'USER' 'USER robtest' 'robtest' '' 'Debian' '-''
2017-03-22T09:16:02+0000:''UNKNOWN' '192.168.1.16' '' '' '' '' '' 'desktop.home' 'USER' 'USER robtest' 'robtest' '' 'Debian' '-''
2017-03-22T09:16:02+0000:'BEFORE 'UNKNOWN' '192.168.1.16' '' '' '' '' '' 'desktop.home' 'PASS' 'PASS (hidden)' 'robtest' '' 'Debian' '-''

So the script is executable and 'working' however when I upload a file, I see nothing in here at all. The ExecLog that I've defined is also not getting created (it's in /tmp while I'm playing around)

I've attached the configuration in its entirety, it's a stock Debian install. The custom config I've been doing is all in sftp.conf

I can't see what I've done wrong, I'm hoping I've missed something obvious?

Many Thanks
Rob
8
ok, thanks for the clarification!
9
I need to test with 1.3.6 I guess.  I'll see if I can rebuild with 1.3.6 and test.  Any idea when 1.3.6 will be available (not a rc)?
10
mod_tls / Re: Opening ftps connections using lftp
« Last post by biscuit on March 20, 2017, 07:42:42 pm »
That finally worked! Yeah!

I had to issue this 1 command for lftp to accept my certificate.

set ssl:verify-certificate no
Pages: [1] 2 3 ... 10
sighted planning