You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(356) |
Nov
(380) |
Dec
(318) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(439) |
Feb
(396) |
Mar
(326) |
Apr
(364) |
May
(331) |
Jun
(300) |
Jul
(345) |
Aug
(367) |
Sep
(567) |
Oct
(690) |
Nov
(454) |
Dec
(328) |
2003 |
Jan
(507) |
Feb
(507) |
Mar
(556) |
Apr
(482) |
May
(529) |
Jun
(528) |
Jul
(534) |
Aug
(271) |
Sep
(333) |
Oct
(348) |
Nov
(340) |
Dec
(241) |
2004 |
Jan
(319) |
Feb
(331) |
Mar
(283) |
Apr
(259) |
May
(172) |
Jun
(212) |
Jul
(186) |
Aug
(264) |
Sep
(201) |
Oct
(138) |
Nov
(136) |
Dec
(107) |
2005 |
Jan
(130) |
Feb
(154) |
Mar
(116) |
Apr
(79) |
May
(123) |
Jun
(151) |
Jul
(65) |
Aug
(121) |
Sep
(113) |
Oct
(109) |
Nov
(134) |
Dec
(78) |
2006 |
Jan
(26) |
Feb
(83) |
Mar
(150) |
Apr
(83) |
May
(145) |
Jun
(80) |
Jul
(102) |
Aug
(99) |
Sep
(93) |
Oct
(26) |
Nov
(39) |
Dec
(46) |
2007 |
Jan
(78) |
Feb
(65) |
Mar
(77) |
Apr
(39) |
May
(63) |
Jun
(59) |
Jul
(53) |
Aug
(50) |
Sep
(93) |
Oct
(85) |
Nov
(35) |
Dec
(22) |
2008 |
Jan
(56) |
Feb
(26) |
Mar
(58) |
Apr
(45) |
May
(52) |
Jun
(52) |
Jul
(41) |
Aug
(34) |
Sep
(27) |
Oct
(75) |
Nov
(31) |
Dec
(69) |
2009 |
Jan
(54) |
Feb
(55) |
Mar
(57) |
Apr
(39) |
May
(40) |
Jun
(79) |
Jul
(49) |
Aug
(30) |
Sep
(46) |
Oct
(72) |
Nov
(89) |
Dec
(71) |
2010 |
Jan
(48) |
Feb
(73) |
Mar
(52) |
Apr
(28) |
May
(32) |
Jun
(48) |
Jul
(29) |
Aug
(38) |
Sep
(14) |
Oct
(32) |
Nov
(70) |
Dec
(46) |
2011 |
Jan
(33) |
Feb
(30) |
Mar
(79) |
Apr
(24) |
May
(29) |
Jun
(63) |
Jul
(22) |
Aug
(38) |
Sep
(27) |
Oct
(49) |
Nov
(41) |
Dec
(69) |
2012 |
Jan
(28) |
Feb
(21) |
Mar
(18) |
Apr
(50) |
May
(30) |
Jun
(16) |
Jul
(22) |
Aug
(15) |
Sep
(35) |
Oct
(37) |
Nov
(23) |
Dec
(19) |
2013 |
Jan
(40) |
Feb
(76) |
Mar
(18) |
Apr
(17) |
May
(27) |
Jun
(17) |
Jul
(67) |
Aug
(30) |
Sep
(27) |
Oct
(43) |
Nov
(13) |
Dec
(13) |
2014 |
Jan
(37) |
Feb
(36) |
Mar
(31) |
Apr
(3) |
May
(40) |
Jun
(20) |
Jul
(18) |
Aug
(23) |
Sep
(15) |
Oct
(28) |
Nov
(26) |
Dec
(20) |
2015 |
Jan
(10) |
Feb
(16) |
Mar
(8) |
Apr
(11) |
May
(6) |
Jun
(8) |
Jul
(6) |
Aug
(12) |
Sep
(4) |
Oct
(26) |
Nov
(13) |
Dec
(6) |
2016 |
Jan
(30) |
Feb
(19) |
Mar
(12) |
Apr
(15) |
May
(3) |
Jun
(20) |
Jul
|
Aug
(19) |
Sep
(17) |
Oct
(7) |
Nov
(15) |
Dec
(33) |
2017 |
Jan
(19) |
Feb
(18) |
Mar
(25) |
Apr
(25) |
May
(10) |
Jun
(2) |
Jul
(5) |
Aug
(9) |
Sep
|
Oct
(5) |
Nov
(18) |
Dec
(4) |
2018 |
Jan
(17) |
Feb
(14) |
Mar
(4) |
Apr
(8) |
May
(9) |
Jun
(9) |
Jul
(12) |
Aug
(26) |
Sep
(10) |
Oct
(2) |
Nov
(6) |
Dec
(2) |
2019 |
Jan
(4) |
Feb
(2) |
Mar
(4) |
Apr
(2) |
May
(16) |
Jun
(2) |
Jul
(5) |
Aug
(16) |
Sep
(13) |
Oct
(16) |
Nov
(7) |
Dec
(18) |
2020 |
Jan
(4) |
Feb
(6) |
Mar
(9) |
Apr
(21) |
May
(33) |
Jun
(15) |
Jul
(12) |
Aug
(2) |
Sep
(9) |
Oct
(2) |
Nov
(17) |
Dec
(9) |
2021 |
Jan
(16) |
Feb
(21) |
Mar
(8) |
Apr
(5) |
May
(4) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
|
Oct
|
Nov
(5) |
Dec
(6) |
2022 |
Jan
(9) |
Feb
(3) |
Mar
(18) |
Apr
(7) |
May
(4) |
Jun
(5) |
Jul
(10) |
Aug
(4) |
Sep
(4) |
Oct
(2) |
Nov
(6) |
Dec
(8) |
2023 |
Jan
(3) |
Feb
(4) |
Mar
(24) |
Apr
(13) |
May
(1) |
Jun
|
Jul
(21) |
Aug
(1) |
Sep
(10) |
Oct
(5) |
Nov
|
Dec
(2) |
2024 |
Jan
(9) |
Feb
|
Mar
(1) |
Apr
|
May
(5) |
Jun
|
Jul
(1) |
Aug
(13) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
From: Roberto B. <rob...@pr...> - 2024-05-21 15:40:19
|
I am trying to configure proftpd for using ftps under Ubuntu 24.04 running in a virtual machine (VirtualBox, in a NAT Network). 1. I have generated the certificates with certbot and successfully used them to provide https with apache 2. I have installed proftpd and it works in the standard ftp mode. 3. I have then modified the standard proftpd.conf file by uncommenting Include /etc/proftpd/tls.conf 4. I have modified modules.conf uncommenting LoadModule mod_tls.c 5. I have the following tls.conf file: <IfModule mod_tls.c> > TLSEngine on TLSLog /var/log/proftpd/tls.log TLSProtocol SSLv23 TLSOptions NoCertRequest TLSRSACertificateFile /etc/letsencrypt/live/ > osservatorio.energia.provincia.tn.it/fullchain.pem TLSRSACertificateKeyFile /etc/letsencrypt/live/ > osservatorio.energia.provincia.tn.it/privkey.pem TLSVerifyClient off #TLSRequired on </IfModule> and when I use lftp to connect with the following options: oetools@oeweb:/etc/proftpd$ lftp > lftp :~> open --user xxxx --port 21 ftps:// > osservatorio.energia.provincia.tn.it > Password: > lftp ap...@os...:~> ls > ls: Fatal error: gnutls_handshake: The TLS connection was non-properly > terminated. > and I get the following output in proftpd.log (tls.log remains empty): 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it[...]): > -----BEGIN STACK TRACE----- 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [0] /usr/lib/proftpd/mod_tls.so(+0x26962) [0x7fb5037e6962] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [1] /usr/lib/proftpd/mod_tls.so(+0x26962) [0x7fb5037e6962] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [2] /usr/lib/proftpd/mod_tls.so(+0x29fae) [0x7fb5037e9fae] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [3] proftpd: (accepting > connections)(modules_session_init+0x64) [0x5ed9abc83244] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [4] proftpd: (accepting connections)(+0x2981e) [0x5ed9abc5d81e] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [5] proftpd: (accepting connections)(+0x2a239) [0x5ed9abc5e239] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [6] proftpd: (accepting connections)(main+0x648) > [0x5ed9abc54098] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [7] /lib/x86_64-linux-gnu/libc.so.6(+0x2a1ca) [0x7fb50382a1ca] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [8] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x8b) > [0x7fb50382a28b] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): [9] proftpd: (accepting connections)(_start+0x25) > [0x5ed9abc546b5] 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): -----END STACK TRACE----- 2024-05-21 16:38:57,806 oeweb proftpd[13837] > osservatorio.energia.provincia.tn.it (osservatorio.energia.provincia.tn.it > [ ... ]): ProFTPD terminating (signal 11) Any help is greatly appreciated! Roberto -- |
From: Lists <li...@se...> - 2024-03-14 17:12:29
|
It’s my understanding init script is required for clustered rh8 Geoffrey Myers > On Jan 26, 2024, at 7:25 PM, Robillard, Bob <bro...@ic...> wrote: > > >> >> I'm wondering, why you want to work with init scripts on Redhat8 instead of doing a proper systemd integration > > As an aside, that's how we did it...there's a proftpd.service file in the "contrib" source tree to start from: > > > [Unit] > Description = ProFTPD FTP Server > Wants=network-online.target > After=network-online.target nss-lookup.target local-fs.target remote-fs.target > > [Service] > Type = simple > Environment = PROFTPD_OPTIONS= > EnvironmentFile = -/etc/sysconfig/proftpd > ExecStartPre = /usr/sbin/proftpd --configtest > ExecStart = /usr/sbin/proftpd --nodaemon $PROFTPD_OPTIONS > ExecReload = /bin/kill -HUP $MAINPID > PIDFile = /run/proftpd/proftpd.pid > > [Install] > WantedBy = multi-user.target > > > > -----Original Message----- > From: Preuße, Hilmar via Proftp-user <pro...@li...> > Sent: Thursday, January 25, 2024 5:07 PM > To: pro...@li... > Cc: Preuße, Hilmar <hi...@we...> > Subject: Re: [Proftpd-user] Init script for RHEL8 > > This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. > > On 22.01.2024 20:36, Lists wrote: > > Hi, > >> We are migrating our proftpd from RHEL7 to RHEL8. We copied our >> /etc/init.d script but it does not work. Curious if someone has >> conquered this issue. Proftpd does start when calling >> /usr/sbin/proftpd directly. >> > I'm wondering, why you want to work with init scripts on Redhat8 instead of doing a proper systemd integration. IIRC there are some templates in the proftp source package, which you can use. Further I'd expect that proftp is packaged for Redhat, but I did not check. > > Hilmar > > _______________________________________________ > ProFTPD Users List <pro...@pr...> > Unsubscribe problems? > http://www.proftpd.org/list-unsub.html |
From: Robillard, B. <bro...@ic...> - 2024-01-27 00:23:38
|
> I'm wondering, why you want to work with init scripts on Redhat8 instead of doing a proper systemd integration As an aside, that's how we did it...there's a proftpd.service file in the "contrib" source tree to start from: [Unit] Description = ProFTPD FTP Server Wants=network-online.target After=network-online.target nss-lookup.target local-fs.target remote-fs.target [Service] Type = simple Environment = PROFTPD_OPTIONS= EnvironmentFile = -/etc/sysconfig/proftpd ExecStartPre = /usr/sbin/proftpd --configtest ExecStart = /usr/sbin/proftpd --nodaemon $PROFTPD_OPTIONS ExecReload = /bin/kill -HUP $MAINPID PIDFile = /run/proftpd/proftpd.pid [Install] WantedBy = multi-user.target -----Original Message----- From: Preuße, Hilmar via Proftp-user <pro...@li...> Sent: Thursday, January 25, 2024 5:07 PM To: pro...@li... Cc: Preuße, Hilmar <hi...@we...> Subject: Re: [Proftpd-user] Init script for RHEL8 This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. On 22.01.2024 20:36, Lists wrote: Hi, > We are migrating our proftpd from RHEL7 to RHEL8. We copied our > /etc/init.d script but it does not work. Curious if someone has > conquered this issue. Proftpd does start when calling > /usr/sbin/proftpd directly. > I'm wondering, why you want to work with init scripts on Redhat8 instead of doing a proper systemd integration. IIRC there are some templates in the proftp source package, which you can use. Further I'd expect that proftp is packaged for Redhat, but I did not check. Hilmar |
From: Preuße, H. <hi...@we...> - 2024-01-25 22:07:24
|
On 22.01.2024 20:36, Lists wrote: Hi, > We are migrating our proftpd from RHEL7 to RHEL8. We copied our > /etc/init.d script but it does not work. Curious if someone has > conquered this issue. Proftpd does start when calling /usr/sbin/proftpd > directly. > I'm wondering, why you want to work with init scripts on Redhat8 instead of doing a proper systemd integration. IIRC there are some templates in the proftp source package, which you can use. Further I'd expect that proftp is packaged for Redhat, but I did not check. Hilmar |
From: Lists <li...@se...> - 2024-01-22 19:51:17
|
We are migrating our proftpd from RHEL7 to RHEL8. We copied our /etc/init.d script but it does not work. Curious if someone has conquered this issue. Proftpd does start when calling /usr/sbin/proftpd directly. Geoffrey Myers |
From: TJ S. <tj...@ca...> - 2024-01-04 23:12:31
|
> Would it be possible to log Kex & Encryption & Mac algos to the logs, too? > > I have a server with "legacy" ciphers still enabled, and it's difficult > to identify which users are still on old technology stacks - and we > can't just turn them off and tell our users to deal with it - so I want > to identify our offenders and contact them directly. The SSH algorithms selected for a session are logged, in the SFTPLog file, over a series of messages: Session key exchange: ... Session server hostkey: ... Session client-to-server encryption: ... Session server-to-client encryption: ... Session client-to-server MAC: ... Session server-to-client MAC: ... Session client-to-server compression: ... Session server-to-client compression: ... Adding these algorithms as fields on every subsequent log message would be redundant, and increase the size of each log message unnecessarily. Usually such requests for information/details being logged come down to _which_ logs contain the information, and when. There's no one place that works for everyone's desires/needs. Sometimes what is considered _crucial_ log info for one site, in one log, is considered trivial/unnecessary to another site, using that same log. Often there is a lot of _state_ information, contained across multiple logs and multiple messages, that given sites want. Post-processing of ProFTPD-generated log files, according to the site-specific needs, is usually the best way to obtain that state. Cheers, TJ |
From: Chris Y. <mr...@gm...> - 2024-01-03 18:26:18
|
You're logging "MOD_SFTP_VERSION" Would it be possible to log Kex & Encryption & Mac algos to the logs, too? I have a server with "legacy" ciphers still enabled, and it's difficult to identify which users are still on old technology stacks - and we can't just turn them off and tell our users to deal with it - so I want to identify our offenders and contact them directly. On Wed, Jan 3, 2024 at 10:56 AM TJ Saunders <tj...@ca...> wrote: > > > I've been asked to monitor SFTP logins on a host using proftpd v1.3.7e > > running on Ubuntu 22.04.3 LTS. I've noticed that when a user is > > authenticated, the log message looks like this: > > > > 2024-01-01 21:05:56,180 mod_sftp/1.0.1[206509]: user 'blah' > > authenticated via 'password' method > > > > but you don't show the remove IP address associated with that login. > > > > I haven't tried this yet, but would modifying the pr_log_writefile() > > to look like this work? > > > > (void) pr_log_writefile(sftp_logfd, MOD_SFTP_VERSION, > > "user '%s' authenticated via '%s' method from IP '%s'", user, > > method, session.c->remote_addr); > > > > So it's trivial to figure out where the use logged in from? > > Close. It'd be: > > (void) pr_log_writefile(sftpd_logfd, MOD_SFTP_VERSION, > "user '%s' authenticated via '%s' method from IP '%s'", user, > method, pr_netaddr_get_ipstr(session.c->remote_addr)); > > since session.c->remote_addr points to a non-printable C struct. > > Another way to achieve this, if you want to avoid patching the source code > directly, might be to configure an ExtendedLog that includes this > information, using something like this: > > # Use JSON here, assuming parseability of the generated ExtendedLog > would be useful > LogFormat login '{user="%U",ip="%a",proto="%{protocol}"}' > ExtendedLog AUTH login > > unless you need the specific SSH authentication method as well; I'm not > sure that's exposed (yet) for such custom LogFormat/ExtendedLog > configurations. > > Cheers, > TJ > > > _______________________________________________ > ProFTPD Users List <pro...@pr...> > Unsubscribe problems? > http://www.proftpd.org/list-unsub.html > |
From: John S. <jo...@st...> - 2024-01-03 17:28:14
|
>>>>> "TJ" == TJ Saunders <tj...@ca...> writes: >> I've been asked to monitor SFTP logins on a host using proftpd v1.3.7e >> running on Ubuntu 22.04.3 LTS. I've noticed that when a user is >> authenticated, the log message looks like this: >> >> 2024-01-01 21:05:56,180 mod_sftp/1.0.1[206509]: user 'blah' >> authenticated via 'password' method >> >> but you don't show the remove IP address associated with that login. >> >> I haven't tried this yet, but would modifying the pr_log_writefile() >> to look like this work? >> >> (void) pr_log_writefile(sftp_logfd, MOD_SFTP_VERSION, >> "user '%s' authenticated via '%s' method from IP '%s'", user, >> method, session.c->remote_addr); >> >> So it's trivial to figure out where the use logged in from? > Close. It'd be: > (void) pr_log_writefile(sftpd_logfd, MOD_SFTP_VERSION, > "user '%s' authenticated via '%s' method from IP '%s'", user, > method, pr_netaddr_get_ipstr(session.c->remote_addr)); > since session.c->remote_addr points to a non-printable C struct. Duh... I'm sure I would have found that once I started actually compiling the code. I do think it's a good change to make down the line, since the core login info should be more easily seen in the logs. > Another way to achieve this, if you want to avoid patching the > source code directly, might be to configure an ExtendedLog that > includes this information, using something like this: > # Use JSON here, assuming parseability of the generated ExtendedLog would be useful > LogFormat login '{user="%U",ip="%a",proto="%{protocol}"}' > ExtendedLog AUTH login > unless you need the specific SSH authentication method as well; I'm > not sure that's exposed (yet) for such custom LogFormat/ExtendedLog > configurations. Thanks, this is a good suggestion. I don't want JSON format, just plain text on a per-line basis if fine, but I think I can figure this out from the docs. Also, you might want to thing about putting a CNAME into DNS to point proftpd.org to www.proftpd.org so that web connections from lazy sods like me actually go through. :-) Thanks again for all your work on this software, it's really quite amazing. John |
From: TJ S. <tj...@ca...> - 2024-01-03 16:54:49
|
> I've been asked to monitor SFTP logins on a host using proftpd v1.3.7e > running on Ubuntu 22.04.3 LTS. I've noticed that when a user is > authenticated, the log message looks like this: > > 2024-01-01 21:05:56,180 mod_sftp/1.0.1[206509]: user 'blah' > authenticated via 'password' method > > but you don't show the remove IP address associated with that login. > > I haven't tried this yet, but would modifying the pr_log_writefile() > to look like this work? > > (void) pr_log_writefile(sftp_logfd, MOD_SFTP_VERSION, > "user '%s' authenticated via '%s' method from IP '%s'", user, > method, session.c->remote_addr); > > So it's trivial to figure out where the use logged in from? Close. It'd be: (void) pr_log_writefile(sftpd_logfd, MOD_SFTP_VERSION, "user '%s' authenticated via '%s' method from IP '%s'", user, method, pr_netaddr_get_ipstr(session.c->remote_addr)); since session.c->remote_addr points to a non-printable C struct. Another way to achieve this, if you want to avoid patching the source code directly, might be to configure an ExtendedLog that includes this information, using something like this: # Use JSON here, assuming parseability of the generated ExtendedLog would be useful LogFormat login '{user="%U",ip="%a",proto="%{protocol}"}' ExtendedLog AUTH login unless you need the specific SSH authentication method as well; I'm not sure that's exposed (yet) for such custom LogFormat/ExtendedLog configurations. Cheers, TJ |
From: John S. <jo...@st...> - 2024-01-03 16:37:30
|
TJ, Thanks for all your hard work on this software and for continuing to maintain it. I really appreciate what you do. John |
From: John S. <jo...@st...> - 2024-01-03 16:37:30
|
I've been asked to monitor SFTP logins on a host using proftpd v1.3.7e running on Ubuntu 22.04.3 LTS. I've noticed that when a user is authenticated, the log message looks like this: 2024-01-01 21:05:56,180 mod_sftp/1.0.1[206509]: user 'blah' authenticated via 'password' method but you don't show the remove IP address associated with that login. Looking at mod_sftp/auth.c, we can see the following lines in the function XXXXX if (session.auth_mech != NULL) { pr_log_debug(DEBUG2, "user '%s' authenticated by %s", user, session.auth_mech); } (void) pr_log_writefile(sftp_logfd, MOD_SFTP_VERSION, "user '%s' authenticated via '%s' method", user, method); /* This allows for the %s response code LogFormat variable to be populated * in an AUTH ExtendedLog. */ pr_response_add(R_230, "User %s logged in", user); pr_cmd_dispatch_phase(pass_cmd, POST_CMD, 0); pr_cmd_dispatch_phase(pass_cmd, LOG_CMD, 0); pr_response_clear(&resp_list); pr_cmd_dispatch_phase(cmd, POST_CMD, 0); pr_cmd_dispatch_phase(cmd, LOG_CMD, 0); I haven't tried this yet, but would modifying the pr_log_writefile() to look like this work? (void) pr_log_writefile(sftp_logfd, MOD_SFTP_VERSION, "user '%s' authenticated via '%s' method from IP '%s'", user, method, session.c->remote_addr); So it's trivial to figure out where the use logged in from? I think I can also just look at the xferlog file and then cross-correlate, but it's a pain in the ass and if the information is already available at login, this would seem to make things simpler. My config looks like this for LOG directives: proftpd.conf:TransferLog /var/log/proftpd/xferlog proftpd.conf:SystemLog /var/log/proftpd/proftpd.log proftpd.conf:SyslogLevel INFO conf.d/sftp.conf: SFTPLog /var/log/proftpd/sftp.log |
From: TJ S. <tj...@ca...> - 2023-12-20 04:49:13
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, ProFTPD community. The ProFTPD Project team is happy to announce that the second maintenance release for ProFTPD 1.3.8 is now available for public consumption. You can download 1.3.8b, including PGP signatures and SHA256 sums, from GitHub: https://github.com/proftpd/proftpd/archive/v1.3.8b.tar.gz Alternatively, you can download proftpd from the main site: ftp://ftp.proftpd.org/distrib/source The 1.3.8b release is a maintenance release, containing various fixes backported from the 1.3.9 development cycle. Please read the included NEWS and RELEASE_NOTES files for the full details. The SHA256 sum for the source tarball is: 183ab7c6107de271a2959ff268f55c9b6c76b2cf0029e6584fccc019686601e0 proftpd-1.3.8b.tar.gz The PGP signature for the source tarball is: proftpd-1.3.8b.tar.gz: -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEABECAAYFAmWCcGMACgkQt46JP6URl2rOOACgqd6poiniUeOej3gVoE4ZHA1Z PKgAoKgsyi9zqoilnOtZJKfzWw4BJ546 =GIJC -----END PGP SIGNATURE----- My PGP key has been used to sign the source tarballs as well as this announcement; it is available via MIT's public keyserver. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAmWCcX8ACgkQt46JP6URl2r2YQCgz5CLfTFc5Wm8GLB5UZjCOlko unIAnjxvBt4hL/KPjnHp+vKaHTpALJz/ =JYci -----END PGP SIGNATURE----- |
From: TJ S. <tj...@ca...> - 2023-12-20 04:41:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, ProFTPD community. The ProFTPD Project team is pleased to announce that the second release candidate for ProFTPD 1.3.9 is now available for public consumption. You can download 1.3.9rc2, including PGP signature, from GitHub: https://github.com/proftpd/proftpd/archive/v1.3.9rc2.tar.gz Alternatively, you can download proftpd from the main site: ftp://ftp.proftpd.org/distrib/source The 1.3.9rc2 release includes security fixes, and other bugfixes, including: + Addressing "Terrapin" SSH attack (CVE-2023-48795) + Fixed builds for ChaChaPoly SSH support using older OpenSSL versions Please read the included NEWS and RELEASE_NOTES files for the full details. The SHA256 sum for the source tarball is: ffec3df8dc9f727203255b467bba9404b17b9ea3b61715ceb477c2417e081b76 proftpd-1.3.9rc2.tar.gz The PGP signature for the source tarball is: proftpd-1.3.9rc2.tar.gz: -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEABECAAYFAmWCarIACgkQt46JP6URl2oNkgCfeyPsyKljSwK36TiTZu16wAGY ZG0AoPx8OnkjA5m4rz42qQxozY9B+MpK =bMjA -----END PGP SIGNATURE----- My PGP key has been used to sign the source tarballs as well as this announcement; it is available via MIT's public keyserver. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAmWCbBgACgkQt46JP6URl2oLNQCgv4PS+58YzNJCWYVzizji5Tuk +xQAnRLPvYfgDtNe3c4gqkz1e7ct+kfp =Uxk+ -----END PGP SIGNATURE----- |
From: TJ S. <tj...@ca...> - 2023-10-09 00:00:45
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, ProFTPD community. The ProFTPD Project team is pleased to announce that the first maintenance release for ProFTPD 1.3.8 is now available for public consumption. You can download 1.3.8a, including PGP signatures and SHA256 sums, from GitHub: https://github.com/proftpd/proftpd/archive/v1.3.8a.tar.gz Alternatively, you can download proftpd from the main site: ftp://ftp.proftpd.org/distrib/source The 1.3.8a release is a maintenance release, containing various fixes backported from the 1.3.9 development cycle. Please read the included NEWS and RELEASE_NOTES files for the full details. The SHA256 sum for the source tarball is: 56093b890a712220b09b98e29de2974a590e8fae6b36ed78c698a90945466aaf proftpd-1.3.8a.tar.gz The PGP signature for the source tarball is: proftpd-1.3.8a.tar.gz: -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEABECAAYFAmUjQZQACgkQt46JP6URl2qpFwCggqITzFB6fkGfBU5z0+AX3aGn EVgAnRC//qyIouovEZcf/STTg6CDAbMn =sgjA -----END PGP SIGNATURE----- My PGP key has been used to sign the source tarballs as well as this announcement; it is available via MIT's public keyserver. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAmUjQckACgkQt46JP6URl2qK2wCg89VT/KA7bmSIROtuApa9GCaQ Do4An3BndI0II5LoGGEtpg6jbi0pH+Zs =Oemg -----END PGP SIGNATURE----- |
From: TJ S. <tj...@ca...> - 2023-10-08 23:40:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, ProFTPD community. The ProFTPD Project team is pleased to announce that the first release candidate for ProFTPD 1.3.9 is now available for public consumption. You can download 1.3.9rc1, including PGP signature, from GitHub: https://github.com/proftpd/proftpd/archive/v1.3.9rc1.tar.gz Alternatively, you can download proftpd from the main site: ftp://ftp.proftpd.org/distrib/source The 1.3.9rc1 release includes major new features and numerous bugfixes, including: + Support for the cha...@op... SSH cipher algorithm + Support for OpenSSh FIDO security keys + Fixed builds using OpenSSL 3.x + Improved file download speed Please read the included NEWS and RELEASE_NOTES files for the full details. The SHA256 sum for the source tarball is: 9d25e4ae7256df43753cb4e16f1e3946f379deb5cc32131765d97e60ed4c2464 proftpd-1.3.9rc1.tar.gz The PGP signature for the source tarball is: proftpd-1.3.9rc1.tar.gz: -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEABECAAYFAmUjOdIACgkQt46JP6URl2pSBACg+GZ1+xXTCAEUW6XxRBQfRly4 9SgAoPyC3gUcgi+q/xNtdAGFO8L6HqZS =wKtt -----END PGP SIGNATURE----- My PGP key has been used to sign the source tarballs as well as this announcement; it is available via MIT's public keyserver. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAmUjOi0ACgkQt46JP6URl2rCjQCg9MViaUvsminL/zTd9iifcQud 64UAn00/DWHhIi4EVQfRW8QJI8gv93XS =3lmV -----END PGP SIGNATURE----- |
From: TJ S. <tj...@ca...> - 2023-10-04 02:11:42
|
> In the log I see: > > mod_sftp.c: error initializing session: Permission denied. To see more details, I recommend configuring an SFTPLog file. The mod_sftp module will log more information to that log. http://www.proftpd.org/docs/contrib/mod_sftp.html#SFTPLog Cheers, TJ |
From: Lists <li...@se...> - 2023-10-03 19:02:52
|
Geoffrey Myers > On Oct 2, 2023, at 3:55 PM, Geoffrey Myers <geo...@gm...> wrote: > > > Slowly debugging this installation. I have: > > LoadModule mod_sftp.c in my config. > > In the log I see: > > mod_sftp.c: error initializing session: Permission denied. > > Suggestions? > > Geoffrey Myers |
From: Geoffrey M. <geo...@gm...> - 2023-10-02 19:55:41
|
Slowly debugging this installation. I have: LoadModule mod_sftp.c in my config. In the log I see: mod_sftp.c: error initializing session: Permission denied. Suggestions? Geoffrey Myers |
From: Lists <li...@se...> - 2023-09-27 18:03:33
|
Geoffrey Myers > On Sep 26, 2023, at 4:01 PM, TJ Saunders <tj...@ca...> wrote: > > >> >> New install rpm install on rh8. 1.3.6e. >> >> Get this error: fatal: SFTPHostKey unable to use /etc/ssh/…. as host >> key, as it is group- or world-accessible. Perms are rw-r——- root >> ssh_keys >> >> These perms default install for red hat. Is there a way around this. > > I think you may need to use: > > SFTPOptions InsecureHostKeyPerms > > See: > http://www.proftpd.org/docs/contrib/mod_sftp.html#SFTPOptions > > Hope this helps, > TJ Must be missing something. Added in <virtual host> just above the key entries. Same error |
From: Alexey K. <ax...@gm...> - 2023-09-27 17:50:50
|
Heh, thanks for a nice hardening of my boxes - i'd better deal with more strict permissions. Respectfully, Alexey On Tue, Sep 26, 2023 at 11:01 PM TJ Saunders <tj...@ca...> wrote: > > New install rpm install on rh8. 1.3.6e. > > > > Get this error: fatal: SFTPHostKey unable to use /etc/ssh/…. as host > > key, as it is group- or world-accessible. Perms are rw-r——- root > > ssh_keys > > > > These perms default install for red hat. Is there a way around this. > > I think you may need to use: > > SFTPOptions InsecureHostKeyPerms > > See: > http://www.proftpd.org/docs/contrib/mod_sftp.html#SFTPOptions > > Hope this helps, > TJ > > > _______________________________________________ > ProFTPD Users List <pro...@pr...> > Unsubscribe problems? > http://www.proftpd.org/list-unsub.html |
From: TJ S. <tj...@ca...> - 2023-09-26 19:59:57
|
> New install rpm install on rh8. 1.3.6e. > > Get this error: fatal: SFTPHostKey unable to use /etc/ssh/…. as host > key, as it is group- or world-accessible. Perms are rw-r——- root > ssh_keys > > These perms default install for red hat. Is there a way around this. I think you may need to use: SFTPOptions InsecureHostKeyPerms See: http://www.proftpd.org/docs/contrib/mod_sftp.html#SFTPOptions Hope this helps, TJ |
From: Geoffrey M. <geo...@gm...> - 2023-09-26 19:28:37
|
New install rpm install on rh8. 1.3.6e. Get this error: fatal: SFTPHostKey unable to use /etc/ssh/…. as host key, as it is group- or world-accessible. Perms are rw-r——- root ssh_keys These perms default install for red hat. Is there a way around this. Geoffrey Myers |
From: Geoffrey M. <li...@se...> - 2023-09-22 15:51:37
|
We have proftpd successfully running on RHEL7 server. We are migrating to RHEL8. We have proftpd installed and have sudo command to start/stop proftpd from an existing non-root application id. When running, proftpd shows our application id as the id associated with the proftpd process. Same configuration on RHEL8, shows the application id as 'nobody'. Although proftpd is running, connections are refused. I'm guessing this could be an selinux issue? Anyone run into a similar issue? Thanks Geoffrey Myers |
From: Lists <li...@se...> - 2023-09-12 21:02:23
|
Found my solution. LoadModule mod_sftp.c Geoffrey Myers > On Sep 12, 2023, at 3:57 PM, Lists <li...@se...> wrote: > > I get the error ‘unknown configuration directive SFTPEngine’ > > proftpd-V shows mod_sftp included in —with-modules > > proftpd -l does not list mod_sftp > > Geoffrey Myers |
From: Lists <li...@se...> - 2023-09-12 19:55:36
|
I get the error ‘unknown configuration directive SFTPEngine’ proftpd-V shows mod_sftp included in —with-modules proftpd -l does not list mod_sftp Geoffrey Myers |