Bug#1019230: Bug#1021276: Pending snort 2.9.20 update

Dear Markus, Thank you for preparing. Could you please share the patch you are working on? Snort is available in Salsa. Maybe you could upload / provide there your propose changes in a separate branch? Saludos, Javier El vie, 20 ene 2023, 21:42, Markus Koschany escribió: > Control: tags -1

Bug#991113: libpam-chroot: pam_chroot.so installed in wrong place - Not able to login after upgrade

Dear Michael, Thanks for the proposed patch. I will try to review and submit a new package version is the coming days. Saludos, Javier El mié, 8 jun 2022 20:45, M. Buecher escribió: > I had a look at the package source and only the paths in the file > debian/rules [1] have to be changed. >

Bug#1009820: snort: Privilege escalation due to insecure use of logrotate

fix for this bug in any case is to adjust the definitions in the logrotate file, which uses "/var/log/snort/*/alert" and "/var/log/ snort/*/*log". These definitions are too broad and could be simplified. Best regards, Javier Fernandez-Sanguino On Mon, 18 Apr 2022 at 19:27

Bug#965455: chrootuid: diff for NMU version 1.3-6.1

ild-arch build-indep clean binary-indep binary-arch > binary install configure > diff -u chrootuid-1.3/debian/control chrootuid-1.3/debian/control > --- chrootuid-1.3/debian/control > +++ chrootuid-1.3/debian/control > @@ -2,7 +2,7 @@ > Section: admin > Priority: optional >

Bug#965458: chntpw: Removal of obsolete debhelper compat 5 and 6 in bookworm

Dear Fabio and Adrian, I have just uploaded version 140201-1 to the archive based on Fabio's work in Salsa. I have taken some time to fix some additional bugs as well as incorporate some patches / improvements published in Github by Adrian Gibanel Lopez (https://github.com/rescatux/chntpw/)

Bug#961359: Bug#929276: remem: diff for NMU version 2.12-7.1

Dear Boyuan, On Tue, 31 Aug 2021 at 16:39, Boyuan Yang wrote: > Control: tags -1 +patch +pending > X-Debbugs-CC: j...@debian.org > > Dear maintainer, > > I've prepared an NMU for remem (versioned as 2.12-7.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it

Bug#980047: libpam-chroot: diff for NMU version 0.9-4.4

Dear Adrian, Thank you for preparing the NMU but please cancel it. I have just uploaded version 0.9-5 to unstable to fix the RC bugs. Sorry for the delay. Best regards, Javier On Wed, 16 Jun 2021 at 13:48, Adrian Bunk wrote: > Control: tags 980047 + patch > Control: tags 980047 + pending >

Bug#984614: #984614 - fixed in unstable

El mar., 13 abr. 2021 19:51, Chris Hofstaedtler escribió: > Hello again, > > just in case you are not aware - if snort should stay in testing, > someone will need to file an unblock bug against release.debian.org. > This was done already: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986908

Bug#984614: snort in Bullseye

On Fri, 9 Apr 2021 at 20:10, Chris Hofstaedtler wrote: > Control: found -1 2.9.15.1-2 > > Hi, > > it appears this conffile handling problem is caused by a not good > enough attempt to move the old conffile /etc/cron.daily/5snort to > /etc/cron.daily/snort-common. > You are correct. > It would

Bug#962275: snort: Failed to start LSB

An update on this bug: The missing symbols issue is really a problem in the daq library. A patch introduced in 2.0.7-1 to fix some FTBFS bugs (959617, 958101) actually disabled symbols in the library which are required. This will be soon fixed. The issue related to the library location is a

Bug#962275: snort: Failed to start LSB

Dear Thorsten, Indeed I have found two issues in the Snort package related to this bug report: 1.- The location of the libraries in /etc/snort.conf is not correct for different architectures. I need to find a way to ammend this value when the package gets compiled (or find a way to locate this

Bug#962275: snort: Failed to start LSB

On Fri, 5 Jun 2020 at 15:09, Thorsten Bonow wrote: > Package: snort > Version: 2.9.15.1-2 > Severity: grave > > Dear Maintainer, > > installation of 'snort' fails with a subprocess error (fresh install, > /etc/snort doesn't exist before installation. Accepting the propose > d network settings:

Bug#878841: clips FTBFS: uudecode: not found

Saludos Javier On 17 October 2017 at 07:28, Adrian Bunk wrote: > Source: clips > Version: 6.30-1 > Severity: serious > > https://buildd.debian.org/status/package.php?p=clips=sid Thanks for the report, I forgot to adjust the Build-depends with the new changes introduced in the

Bug#861842: snort 2.9.7 is EOL upstream

severity 861842 important thanks On 4 May 2017 at 18:36, Lee Garrett wrote: > Source: snort > Version: 2.9.7.0-5 > Severity: grave > Justification: renders package unusable > I do not agree that this Snort version being EOL makes the package unusable. Sure, it will be

Bug#850632: openuniverse: fails to start "input in flex scanner failed

On 23 January 2017 at 10:19, Petter Reinholdtsen wrote: > Control: tags -1 + patch > > [Petter Reinholdtsen] > > I guess the install target for the configuration file is bad. > > The problem seem to be that autoconf/automake have changed behaviour, > breaking > the old install

Bug#842568: iisemulator: diff for NMU version 0.95-3.2

El 24 nov. 2016 2:03 p. m., "Joao Eriberto Mota Filho" escribió: > > Control: tags 842568 + pending > > Dear maintainer, > > I've prepared an NMU for iisemulator (versioned as 0.95-3.2) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer.

Bug#827791: samhain: logfile-monitor requires build dependency on libpcre3-dev

On 21 June 2016 at 07:37, Logan Rosen wrote: > samhain currently fails to build from source because it doesn't > build-depend on > libpcre3-dev, which is required by the newly-enabled logfile-monitor > module. > Thank you for detecting this. I have just submitted a new

Bug#783683: cron started with -f (foreground), killing processes on restart

On 7 June 2015 at 18:30, Christian Kastner deb...@kvr.at wrote: On 2015-06-06 21:33, Christoph Berg wrote: I had hoped to see this fixed in today's point release. What happened with the jessie package? I'm afraid I couldn't get a hold of Javier regarding an upload. I myself don't have

Bug#735530: samhain: FTBFS on amd64 and kfreebsd

tags 735530 upstream help thanks The latest samhain upload doesn't build on amd64. This was also the case with the previous upload (3.1.0-1). I've forwarded this issue upstream. I have not yet received an answer or patch to fix this. If someone can help review and tackle this issue it would

Bug#735530: samhain: FTBFS on amd64 and kfreebsd

On 16 January 2014 09:33, Ivo De Decker ivo.dedec...@ugent.be wrote: The latest samhain upload doesn't build on amd64. This was also the case with the previous upload (3.1.0-1). (...) Thanks. I'll take a more detailed look but, reviewing this fast: - the amd64 FTBFS issue seem to be an

Bug#701353: samhain: ftbfs with GCC-4.8

El 03/09/2013 12:09, Laurent Bigonville bi...@debian.org escribió: Any news about this bug? No news. Sorry, I cannot work on this until next week. For some reasons (unclean build environment?) the i386 version of the package is depending against libaudit0 and this is blocking the transition

Bug#710068: tiger: postinst uses /usr/share/doc content (Policy 12.3)

From the attached log (scroll to the bottom...): Selecting previously unselected package tiger. (Reading database ... 7084 files and directories currently installed.) Unpacking tiger (from .../tiger_1%3a3.2.3-10_amd64.deb) ... Setting up tiger (1:3.2.3-10) ... ERROR in maintainer

Bug#688379: [Openvas-distro-deb] Bug#688379: openvas-server: modifies conffiles (policy 10.7.3): /etc/openvas/openvasd.conf

Sébastien, Thank you for the patch, but I already asked the debian-release team to remove openvas-server from testing [1]. Openvas-server is replaced by openvas-scanner (available in experimental). I would suggest you do not dedicate too much time in it. Some of openva-server's bugs (I believe

Bug#614497: doc-debian: The OPL-licensed documents taken from Debian website are non-free

On 22 October 2012 14:30, Jonathan Nieder jrnie...@gmail.com wrote: Many parts of www.debian.org are already relicensed by now. Maybe this bug could be resolved by updating the copyright information and calling it a day (update: no). Hello Jonathan, Thanks for the updated information.

Bug#679106: cron: multiple /etc/init.d/cron stop may kill unrelated processes

On 3 July 2012 02:39, Christoph Anton Mitterer cales...@scientia.net wrote: On Tue, 2012-07-03 at 02:04 +0200, Javier Fernández-Sanguino Peña wrote: This should be fixed in cron itself (through it's SIG handler) Are you going to follow this up? I you are asking if this is going to fix in the

Bug#679106: cron: multiple /etc/init.d/cron stop may kill unrelated processes

On 29/06/2012, Christoph Anton Mitterer cales...@scientia.net wrote: On Wed, 2012-06-27 at 20:36 +0200, Javier Fernandez-Sanguino wrote: For its stop argument, cron uses /lib/lsb/init-functions's killproc. I believe killproc should remove the pidfile if the processes is killed properly. ok

Bug#679106: cron: multiple /etc/init.d/cron stop may kill unrelated processes

tag 679106 moreinfo thanks Apparently, cron doesn't clear the PID file once stopped, so subsequent invokations of: /etc/init.d/cron stop continue to try killing a process of that PID. For its stop argument, cron uses /lib/lsb/init-functions's killproc. I believe killproc should remove the

Bug#650060: NMU

Thanks for the NMU, I did not have time this week to make an upload myself. Regards Javier PS: If I have time I might make an upload soon with the same changes, in order to acknowledge the NMU -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe.

Bug#676066: farpd: FTBFS: configure: error: libevent not found

Thanks for taking care of this bug and provide a patch. I will review it and upload as soon as possible. Javier El 16/06/2012 18:24, Sebastian Ramacher sebast...@ramacher.at escribió: tags 676066 + patch thanks On 05/06/12 00:04, Lucas Nussbaum wrote: Relevant part: debian/rules build

Bug#650060: snort: diff for NMU version 2.9.2.2-1.1

Yes, I will make an upload hopefully today. Regards Javier El 17/06/2012 19:14, Adam D. Barratt a...@adam-barratt.org.uk escribió: On Sun, 2012-06-03 at 18:18 +0200, gregor herrmann wrote: Now we just have to figure out why it fa... Is there any chance of an upload including the updated patch

Bug#650060: snort: diff for NMU version 2.9.2.2-1.1

I've prepared an NMU for snort (versioned as 2.9.2.2-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Thank you, I have applied this patch to the GIT repo, I will test it out and, if it works as expected I will upload a new package version myself.

Bug#622011: [Openvas-distro-deb] Bug#622011: openvas-client: FTBFS: nessus.c:485: undefined reference to `SSLv2_client_method'

Thanks for the patch, I will apply it an upload a new version as soon as possible. Regards Javier El 21/08/2011 16:33, Ilya Barygin bary...@gmail.com escribió: tags 622011 patch thanks Hello, Attached is the patch which was used in Ubuntu to fix this problem.

Bug#618112: titantools: FTBFS: collect2: ld returned 1 exit status

On 29 March 2011 09:15, Adam D. Barratt a...@adam-barratt.org.uk wrote: On Tue, March 29, 2011 06:29, Lucas Nussbaum wrote: Strange, you are rebuilding titantools 4.0.11-4 (from oldstable) when the latest version is 4.0.11+notdfsg1-2. 4.0.11-4 is still available in lenny and sid. I suspect

Bug#608590: snort: Local changes to some configuration files are not preserved on upgrades

Package: snort Version: 2.8.5.2-2 Priority: serious Justification: Policy violation 10.7.3 Tags: stable unstable The Snort package handles a configuration file /etc/snort/snort.debian.conf through debconf but does not preserver changes introduced in this configuration file by the local admin. It

Bug#607951: Snort-common: error in preinst script generates improper config files

Package: snort-common Version: 2.8.5.2-2 Severity: serious Tag: pending Reviewing today the patch introduced in snort-common's preinst has two bugs that have the following consequences: - the /etc/snort/database.conf file created gets overwritten with the contents of snort.conf and the

Bug#607751: snort: Update gives current Snort configuration is invalid error and it will not start

+++ Initializing rule chains... Warning: /etc/snort/rules/dos.rules(42) = threshold (in rule) is deprecated; use detection_filter instead. ERROR: /etc/snort/rules/community-smtp.rules(13) = !any is not allowed Fatal Error, Quitting.. ---8---

Bug#603428: snort: prompting due to modified conffiles which where not modified by the user

+0100, Javier Fernandez-Sanguino wrote: Which warning? The NEWS ... The config file. Why would you want to discourage editing that directly? Cheers, Julien -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJND8kjAAoJEDEBgAUJBeQMlr4QANWdboAB2S5DBNj/b1eSkigo 0g

Bug#603428: snort: prompting due to modified conffiles which where not modified by the user

Which warning? The NEWS file or the header in the autogenerated config file? I do not see any harm in either. Can you please elaborate? Javier El 20/12/2010 16:48, Julien Cristau jcris...@debian.org escribió: On Mon, Dec 20, 2010 at 15:57:17 +0100, Javier Fernández-Sanguino Peña wrote: On

Bug#528434: Review of the cron security patches - improved in 3.0pl1-109

Hi, Recarding his bug in Vixie Cron, Christian Kastner pointed me to an additional place where the call to initgroups was unchecked. I've commited a fix in the latest cron package version (3.0pl1-109). You might want to review this fix too to include it in Ubuntu. The patch is available at

Bug#575784: cron: security hole ? allowes opening user sessions ?

That logging appears because those users have setup cron jobs and an entry is generated every time a job is started. This is fixed in sid (by not using pam's session-interactive) but does not mean you have been hacked through cron. Regards Javier 2010/3/29, Oz Nahum nahu...@gmail.com: Package:

Bug#540679: Update on this bug

Just for reference, this bug appears in other architectures too, from the build logs of the recently-uploaded 1.6-1 version: - Armel: https://buildd.debian.org/fetch.cgi?pkg=xorpver=1.6-1arch=armelstamp=1267677892file=log - hppa:

Bug#566677: [Openvas-distro-deb] Bug#566677: prompts user without following Debian Configuration Management Specification

2010/1/25 Luk Claes l...@debian.org: I was under the idea that prompting during a purge should not rely on debconf being available. Isn't that right? Maybe I'm not up to date. You're right on one thing: purge should not fail when debconf is not available. So if Debconf is not available it

Bug#566677: [Openvas-distro-deb] Bug#566677: Bug#566677: prompts user without following Debian Configuration Management Specification

On Montag, 25. Januar 2010, Javier Fernandez-Sanguino wrote: I was under the idea that prompting during a purge should not rely on debconf being available. Isn't that right? Maybe I'm not up to date. debian-policy 3.8.2 finally fixed #206684, there is no exception for purge. Thanks Holder, I

Bug#566677: [Openvas-distro-deb] Bug#566677: prompts user without following Debian Configuration Management Specification

during a test with piuparts I noticed your package prompts the user badly. Prompting in maintainer scripts must be done by communicating through a program such as debconf which conforms to the Debian Configuration management specification, version 2 or higher. I was under the idea that

Bug#552071: snort-mysql: last upgraded version starts snort in foreground, failing upgrade and loading

2009/10/23 alex bodnaru alexb...@012.net.il: Package: snort-mysql Version: 2.8.4.1-4+b1 Severity: grave Justification: renders package unusable hello friends, thanks for providing us snort. a problem with last version i've installed: snort is starting in foreground (even though by

Bug#512486: wordtrans-qt: uncompressed man page (although with .gz suffix)

2009/1/22 Evgeni Golov sarge...@die-welt.net: I'll prepare an NMU, making the package binNMU-able, and hoping the new build will have correctly gziped manpages. Go ahead an NMU but please forward first a proposed patch to this bug report. If time permits I might be able to make the upload

Bug#460886: cron: Fails to stop because of incorrect .pid file name

2008/1/15, Frans Pop [EMAIL PROTECTED]: Seems like the error is in this line: PIDFILE=/var/run/cron.pid which should probably be PIDFILE=/var/run/crond.pid Aggh a typo. I hate that. I will fix that ASAP (i.e. today) Which makes me wonder if [ -e /etc/cron.pid ] PIDFILE=/etc/cron.pid

Bug#445113: Reopen bug

reopen bug 445113 thanks This bug has not been fixed by the upload of snort 2.7.0-8 as there are still build failures in hppa and sparc The root bug (that causes ps2pdf to do a segmentation fault) seems to have been fixed in ia64 and s390, however. I'm reopening this bug again since

Bug#445113: snort: FTBFS on a few archs

When I checked snort for testing migration, I saw that it did not build on a few archs (arm, hppa, ia64, s390 and sparc) and it always has this error message: This seems to be a new bug. Bus error ? Anyway, the FAQ and other documentation should be arch: all packages, I will review why this is

Bug#439642: Probably something debian buildd specific

2007/10/1, Cyril Brulebois [EMAIL PROTECTED]: And where's the patch? Put the .so in the appropriate package, do you really expect more? You might have wanted to remove the help tag instead, since you've now got the hint you were looking for, haven't you? Well, a patch is a patch. A comment

Bug#439642: Probably something debian buildd specific

2007/10/1, Cyril Brulebois [EMAIL PROTECTED]: I think you mean NEW. Incoming is http://incoming.debian.org, and is described in http://www.debian.org/devel/incoming_mirrors.html. True, got confused, meant NEW. Regards Javier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#295154: etherape: Etherape does not start (breaks)

Package: etherape Version: 0.9.0-8 Severity: grave Justification: renders package unusable It seems etherape will not run at all for me, if I run it as root I get this: # LC_ALL=C etherape (etherape:19457): Gtk-WARNING **: gtkwidget.c:3138: widget `GtkToolButton' has no activatable signal