Package Details: proftpd 2:1.3.8c-4

Git Clone URL: https://aur.archlinux.org/proftpd.git (read-only, click to copy)
Package Base: proftpd
Description: High-performance, scalable FTP SSL TLS and SFTP server
Upstream URL: http://www.proftpd.org/
Licenses: GPL
Submitter: xyproto
Maintainer: severach
Last Packager: severach
Votes: 59
Popularity: 0.37
First Submitted: 2013-05-16 15:03 (UTC)
Last Updated: 2024-12-26 20:27 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

severach commented on 2024-12-26 20:00 (UTC)

@eomanis: not a yay bug. pacman vercmp also calculates the upgrade incorrectly. vercmp 1.3.8 1.3.8a would need to be -1 to indicate an upgrade, not 1. I've added some code for improved update detection.

@mmkodali: The vercmp bug elsewhere linked against OpenSSL-1.1 which crashed mod_sql. That should all be fixed.

mmkodali commented on 2024-12-26 13:29 (UTC) (edited on 2024-12-26 13:30 (UTC) by mmkodali)

starting proftpd.service giving the following error.

version: proftpd 2:1.3.8c-2

Dec 26 18:53:58 xxxxx.com proftpd[40908]: 2024-12-26 18:53:58,506 zensmart.cc proftpd[40908]: mod_sql/4.5: notice: no backend modules have been registered
Dec 26 18:53:58 xxxxx.com systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE

Kunda commented on 2023-12-20 14:48 (UTC) 

1.3.8b - Released 19-Dec-2023
--------------------------------
- Issue 1735 - Compiling ProFTPD 1.3.8a mod_sftp, mod_tls using libressl 3.7.3
  fails.
- Issue 1756 - Build system fails for specific module names.
- Issue 1760 - mod_sftp is affected by "Terrapin" Prefix Truncation Attacks in
  SSH Specification (CVE-2023-48795).

severach commented on 2023-10-27 18:03 (UTC)

That sounds like a yay bug. vercmp 1.3.8 1.3.8a outputs 1 so it's known to be a new version. Bumping pkgrel should work and is more sane than bumping the epoch.

eomanis commented on 2023-10-25 19:46 (UTC)

For me, yay was adamant at wanting to build proftpd-2:1.3.8-1 instead of proftpd-2:1.3.8a-1 until I manually deleted the /home/builduser/.cache/yay/proftpd directory.

Maybe the epoch needs to be incremented to fix this, the change history indicates that there was the same problem when this package was updated from upstream version 1.3.6 to 1.3.6a.

cmagnani commented on 2023-01-29 13:54 (UTC)

mod_sql_passwd module is missing in PKGBUILD

eomanis commented on 2022-12-16 17:50 (UTC) (edited on 2022-12-16 20:10 (UTC) by eomanis)

Edit: Created an upstream issue report, 550 PWD: Permission denied for initial directory listing since 1.3.8.

Upgrading from proftpd-2:1.3.7e-1 to proftpd-2:1.3.8-1 causes a fatal regression for me, in that the users cannot list the shared root directory any more. I have manually downgraded to proftpd-2:1.3.7e-1 until I can figure out what is going on.

My current suspicions are a towards a regression with the mod_facl.c module as I am using ACL to control file access, which might be a rather uncommon setup, and I seriously doubt a regression this severe would not have been found before releasing 1.3.8.

With 1.3.7e (good):

Status: Resolving address of XXXXXXXXX.XXX
Status: Connecting to [XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX]:XXXXX...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Status: Directory listing of "/" successful

With 1.3.8 (bad):

Status: Resolving address of XXXXXXXXX.XXX
Status: Connecting to [XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX]:XXXXX...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Command:    PWD
Response:   550 PWD: Permission denied
Error:  Failed to retrieve directory listing

severach commented on 2022-11-09 14:11 (UTC)

proftpd-git is compatible with OpenSSL 3

produnis commented on 2022-11-09 09:12 (UTC)

you need to install openssl-1.1 to make proftpd run again after recent arch update...

migrev commented on 2021-09-09 12:00 (UTC)

@maid: Then it is likely an upstream issue.

1 2 3 4 5 6 Next › Last »