Your message dated Wed, 25 Jun 2025 08:10:15 +0000
with message-id <e1uulcx-00dwme...@fasolo.debian.org>
and subject line Bug#1106873: fixed in proftpd-mod-proxy-protocol 0.6-1
has caused the Debian Bug report #1106873,
regarding ITP: proftpd-mod-proxy-protocol -- Handle protocols which are used by 
proxies, e.g. haproxy
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1106873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Hilmar Preuße <hill...@debian.org>
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name    : proftpd-mod-proxy-protocol
  Version         : 0.6
  Upstream Contact: TJ Saunders  <t...@castaglia.org>
* URL             : https://github.com/Castaglia/proftpd-mod_proxy_protocol/
* License         : GPL-2+
  Programming Lang: C
  Description     : Handle protocols which are used by proxies, e.g. haproxy

 The purpose of the mod_proxy_protocol module is to handle protocols which are
used by proxies, e.g. haproxy, for conveying information about the real
origin/client to the backend server. Protocols like HTTP often have their
own mechanism for doing so, via headers such as "X-Forwarded-For".
Unfortunately, FTP does not have such a mechanism, nor does SSH.

However, there are protocols which an provide this information without
impacting FTP. HAproxy's PROXY protocol is one such mechanism.
The mod_proxy_protocol module uses these mechanisms to change the
information about the "remote" client so that it is the real client,
not the proxy, whose IP address/port are logged and used for e.g.
network ACLs.

<snip>

I'm a member of the Proftp team and I plan to maintain the package in the
team.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: proftpd-mod-proxy-protocol
Source-Version: 0.6-1
Done: Hilmar Preuße <hill...@debian.org>

We believe that the bug you reported is fixed in the latest version of
proftpd-mod-proxy-protocol, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1106...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preuße <hill...@debian.org> (supplier of updated 
proftpd-mod-proxy-protocol package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 30 May 2025 23:44:32 +0200
Source: proftpd-mod-proxy-protocol
Binary: proftpd-mod-proxy-protocol proftpd-mod-proxy-protocol-dbgsym
Architecture: source arm64
Version: 0.6-1
Distribution: unstable
Urgency: medium
Maintainer: ProFTPD Maintainance Team 
<pkg-proftpd-maintain...@alioth-lists.debian.net>
Changed-By: Hilmar Preuße <hill...@debian.org>
Description:
 proftpd-mod-proxy-protocol - ProFTPD module mod_proxy_protocol
Closes: 1106873
Changes:
 proftpd-mod-proxy-protocol (0.6-1) unstable; urgency=medium
 .
   [ Dmitry Smirnov ]
   * Initial release (Closes: #1106873).
Checksums-Sha1:
 a04e4be4af89b30a0ec400e2d2660d0d1c8142ab 2365 
proftpd-mod-proxy-protocol_0.6-1.dsc
 8b13469550b9b3d9be309b42a03a9e99c1077e0f 23647 
proftpd-mod-proxy-protocol_0.6.orig.tar.gz
 a9646dc358d291591aa9f412d461481c38530fb6 2816 
proftpd-mod-proxy-protocol_0.6-1.debian.tar.xz
 ac543c37b84170fd37bddb2480c9e0577fca36f4 25128 
proftpd-mod-proxy-protocol-dbgsym_0.6-1_arm64.deb
 a73e290fa02c47d17ad824271b76384dd770a1c0 7254 
proftpd-mod-proxy-protocol_0.6-1_arm64.buildinfo
 ced7605562e0869964da08607e8c65f8483f1f42 16632 
proftpd-mod-proxy-protocol_0.6-1_arm64.deb
Checksums-Sha256:
 fbe3417ba8538f0a7c6f16eb9fbd5fe5568c8abce6314066a76ecd65fff1ced2 2365 
proftpd-mod-proxy-protocol_0.6-1.dsc
 c468c54808f60f83c54e006d2332c73981a08c5bf9a4ccd8a7d2ea9c93b44f47 23647 
proftpd-mod-proxy-protocol_0.6.orig.tar.gz
 395be02cfac8785793322ce42c912a4b5000c8f217487590ff43d0448d122532 2816 
proftpd-mod-proxy-protocol_0.6-1.debian.tar.xz
 c363aaf5adb3a51bc46406bda4f8403beb26fad1ff8a2bd6b01f9b37e0369c01 25128 
proftpd-mod-proxy-protocol-dbgsym_0.6-1_arm64.deb
 1818359fa3ec79473df46112c2b3bd00605a0afc40f17797386e31d51e1a1e5d 7254 
proftpd-mod-proxy-protocol_0.6-1_arm64.buildinfo
 06cb83283e92a78270299ec18dcbefc635a7a11187d3b1250bbb964e1b2be9f9 16632 
proftpd-mod-proxy-protocol_0.6-1_arm64.deb
Files:
 a3267a03c0a03c712cf819d65de58735 2365 net optional 
proftpd-mod-proxy-protocol_0.6-1.dsc
 1a78b6ce29ceff478cb587038410ee0e 23647 net optional 
proftpd-mod-proxy-protocol_0.6.orig.tar.gz
 c95ed9f0bee1f29cef23cc17df2e00b5 2816 net optional 
proftpd-mod-proxy-protocol_0.6-1.debian.tar.xz
 0e9fef994ac9cdd604da5821595a1446 25128 debug optional 
proftpd-mod-proxy-protocol-dbgsym_0.6-1_arm64.deb
 959e456686e5c130a414189712644387 7254 net optional 
proftpd-mod-proxy-protocol_0.6-1_arm64.buildinfo
 7b420f692434ccdaabdb9861ad66c2ec 16632 net optional 
proftpd-mod-proxy-protocol_0.6-1_arm64.deb

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmg6K5RfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LIss7RAAgcW2g0yEd4wnyvmVUG1869xTs0XxkuEIyI4CD1Rh8g7FJimUsqVw8uRg
gDagtZvfnhZcOKI9kli23alfjGeQKpNo7VLLTMlJbPoYckxNxPZ4oIRzkj+ReqIz
w5F0tcuvrQxk1M9KsEboN2j0I6IQSR0XMKP8ptLpSoJKQeVOnf/vpcV9WyvTjuGu
ugfnIwvh6AGqOBiBBzIZ9ZAwxA4zEg0eIc2Y540HfNrRFxSAFZZWipFNOVrHqhZu
HyoxINOJ9FWxIUogITiP5OYVSGrlpdINbl7eBuFkr3UL0JDA2PXBOs8T9DEvKpyu
crNAgFVGH+7ygF8t1JrdOZt6rA8jsDBnMgNM/GL5e0ZeLrwKwf9m4wFAL/JuqTVN
AMkH0vDCVqYVtV8jyjp6YV5jqTM2JWa5Rw5ETh4gzJnuFxLZwghIudTy5wI48WBr
oXpTGgsA9xw8x9zCeotWxbFSFCp5r5dMKdzYzoJrXClNBdsuCiS6JO9c+z7rAaef
onLhbpejT/TnWs+a0VA4eXWjYZ2R4qrjgPbFqTiBYK7bS5JnFlONyPNwLrA5iuBY
TeaWGtzNBNplBy+Xs89QBIdtNVqutz0JJnwOosjMrLD2sI6JdX3IMLEAam67bxn+
hNsyGRdFHf+34HhA2Jf2g2e8l2r0ivSpQ/smdYGpdQXgwy5R5fo=
=r38e
-----END PGP SIGNATURE-----

Attachment: pgpajnBAW4y18.pgp
Description: PGP signature


--- End Message ---

Reply via email to