Date: Sun, 7 Dec 2025 12:35:27 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Bacula-Web project maintainer <hello@bacula-web.org> Cc: "freebsd-security@FreeBSD.org" <freebsd-security@FreeBSD.org> Subject: Re: Guidance on how to handle FreeBSD port vulnerability Message-ID: <11DA25E7-8840-4182-995A-B976439C2E04@FreeBSD.org> In-Reply-To: <cXTG30QIfXitaGbKSlG7Uj3ytQSr9Iwe6xcuhV_WSSmTA4gYKUzb0RZV2MDm9bi7EHeImSfmx66JWr26-O1iM1w4WyMWnGOI4s8KjJqNNq8=@bacula-web.org> References: <cXTG30QIfXitaGbKSlG7Uj3ytQSr9Iwe6xcuhV_WSSmTA4gYKUzb0RZV2MDm9bi7EHeImSfmx66JWr26-O1iM1w4WyMWnGOI4s8KjJqNNq8=@bacula-web.org>
index | next in thread | previous in thread | raw e-mail
On 7 Dec 2025, at 12:28, Bacula-Web project maintainer <hello@bacula-web.org> wrote: > > > Hello there, > > I'd need some help to tackle a known FreeBSD port vulnerability which doesn't seem to be referenced on FreshPort.org. > > The affected port is https://www.freshports.org/www/bacula-web/. > > Also, I'd like to put some efforts to keep updated above ports as it deserve some more "love". > > An hints / link to documented process would be nice. Report a bug on https://bugs.freebsd.org/bugzilla/, the "Report an update or defect to a port" link there is the most appropriate. If you start the subject of the bug report with the string "www/bacula-web: " it will automatically get assigned to the port maintainer, which at the moment is ler@FreeBSD.org <mailto:ler@FreeBSD.org>. -Dimitryhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11DA25E7-8840-4182-995A-B976439C2E04>