Processed: tagging 903855

Processing commands for cont...@bugs.debian.org: > tags 903855 + upstream Bug #903855 [ruby-rails-admin] CVE-2016-10522 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 903855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903855 Debian

Processed: found 903855 in 0.8.1+dfsg-3

Processing commands for cont...@bugs.debian.org: > found 903855 0.8.1+dfsg-3 Bug #903855 [ruby-rails-admin] CVE-2016-10522 Marked as found in versions ruby-rails-admin/0.8.1+dfsg-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 903855:

Bug#885918: marked as done (Fail to start with UTF-8 anthy dict)

Your message dated Mon, 16 Jul 2018 04:19:44 + with message-id and subject line Bug#885918: fixed in kasumi 2.5-9 has caused the Debian Bug report #885918, regarding Fail to start with UTF-8 anthy dict to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: tagging 903767

Processing commands for cont...@bugs.debian.org: > tags 903767 + pending Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8 Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot Bug #903821 [src:linux]

Bug#903862: FTBFS: override_dh_auto_test exits with exit 2

On Monday, 16 July 2018 9:03:59 AM AEST Vincent Lefevre wrote: > Start 22: test-real-data > 22/118 Test #22: test-real-data ...***Failed > 0.01 sec There is not enough information in this bug report to have a slightest clue about the problem. Could you

Processed: tagging 903862

Processing commands for cont...@bugs.debian.org: > tags 903862 + unreproducible moreinfo Bug #903862 [src:gnucash] FTBFS: override_dh_auto_test exits with exit 2 Added tag(s) moreinfo and unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 903862:

Processed: severity of 903862 is normal

Processing commands for cont...@bugs.debian.org: > severity 903862 normal Bug #903862 [src:gnucash] FTBFS: override_dh_auto_test exits with exit 2 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 903862:

Bug#900897: marked as done (missing dependency on pciutils)

Your message dated Sun, 15 Jul 2018 23:33:59 + with message-id and subject line Bug#900897: fixed in ladvd 1.1.2-1 has caused the Debian Bug report #900897, regarding missing dependency on pciutils to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#903862: FTBFS: override_dh_auto_test exits with exit 2

It is the following test that fails: Start 22: test-real-data 22/118 Test #22: test-real-data ...***Failed 0.01 sec -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR

Bug#903868: heat: FTBFS in buster/sid (dh_installman: Cannot find "doc/build/man/heat-api.1")

Package: src:heat Version: 1:10.0.0-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep pyversions: missing X(S)-Python-Version in

Bug#903867: cod-tools: FTBFS when built with dpkg-buildpackage -A

Package: src:cod-tools Version: 2.2+dfsg-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster with "dpkg-buildpackage -A" but it failed: [...] debian/rules build-indep dh

Bug#903866: python-{clang,lldb}-4.0: missing Breaks+Replaces against python-clang-3.[45], python-lldb-3.5

Package: python-clang-4.0,python-lldb-4.0 Version: 1:4.0.1-10~deb9u2 Severity: serious Tags: stretch User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to

Processed: Re: FTBFS: override_dh_auto_test exits with exit 2

Processing commands for cont...@bugs.debian.org: > tags 903862 ftbfs Bug #903862 [src:gnucash] FTBFS: override_dh_auto_test exits with exit 2 Added tag(s) ftbfs. > End of message, stopping processing here. Please contact me if you need assistance. -- 903862:

Bug#903862: FTBFS: override_dh_auto_test exits with exit 2

Source: gnucash Version: 3.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The build with "apt-get source -b gnucash" ends with: [...] 118/118 Testing: python-bindings 118/118 Test: python-bindings Command: "/usr/bin/python3"

Bug#903860: python3-stem: File "/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / self.method.async = self /

Package: python3-stem Version: 1.6.0-1 Severity: serious Tags: a11y Justification: fails to build from source Dear Maintainer, * What led up to the situation? Package was pulled in as a dependency for nyx which is a dependency for tor-arm and onionshare * What exactly did you do (or not

Bug#903849: marked as done (klibc rebuilt with toolchain from unstable crashes at startup on amd64)

Your message dated Sun, 15 Jul 2018 21:37:06 + with message-id and subject line Bug#903849: fixed in klibc 2.0.4-12 has caused the Debian Bug report #903849, regarding klibc rebuilt with toolchain from unstable crashes at startup on amd64 to be marked as done. This means that you claim that

Bug#886939: marked as done (klibc-utils: leaves diversion after upgrade from stretch)

Your message dated Sun, 15 Jul 2018 21:37:06 + with message-id and subject line Bug#886939: fixed in klibc 2.0.4-12 has caused the Debian Bug report #886939, regarding klibc-utils: leaves diversion after upgrade from stretch to be marked as done. This means that you claim that the problem

Bug#903855: CVE-2016-10522

Package: ruby-rails-admin Severity: grave Tags: security http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10522

Bug#903803: marked as done (puredata-gui: missing Breaks+Replaces: puredata-core (<< 0.48.1-6))

Your message dated Sun, 15 Jul 2018 20:43:07 + with message-id and subject line Bug#903803: fixed in puredata 0.48.1-7 has caused the Debian Bug report #903803, regarding puredata-gui: missing Breaks+Replaces: puredata-core (<< 0.48.1-6) to be marked as done. This means that you claim that

Bug#903821: [Pkg-xen-devel] Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

Hi, On 07/15/2018 12:16 PM, Benoît Tonnerre wrote: > [...] > > After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I > notice a kernel panic on these 3 servers. Thanks for the report. This is probably all related: This went into 4.9.102:

Processed: Bug #903803 in puredata marked as pending

Processing control commands: > tag -1 pending Bug #903803 [puredata-gui] puredata-gui: missing Breaks+Replaces: puredata-core (<< 0.48.1-6) Added tag(s) pending. -- 903803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903803 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#903803: Bug #903803 in puredata marked as pending

Control: tag -1 pending Hello, Bug #903803 in puredata reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#903849: klibc rebuilt with toolchain from unstable crashes at startup on amd64

Package: src:klibc Version: 2.0.4-11 Severity: grave Rebuilding the current version of klibc for amd64 adds a large amount of padding to the .text and .rodata sections of klibc.so: /lib/klibc-MiRPTuou9LIwcm_gDpcF7E1m-p8.so: file format elf64-x86-64 Sections: Idx Name Size VMA

Bug#903821: 4.16 kernel

Hi, Thanks your report! I can start my system with 4.16 backport kernel.

Bug#903821: linux-image-4.9.0-7-amd64: Can not boot 4.9.0_7_amd64 with Xen

Package: src:linux Followup-For: Bug #903821 When booting with the new kernel, I got the following Dom0 crash: Loading Xen 4.8-amd64 ... Loading Linux 4.9.0-7-amd64 ... Loading initial ramdisk ... (XEN) Xen version 4.8.4-pre (Debian 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9)

Processed: limit source to klibc, tagging 891924, tagging 886939, tagging 884716

Processing commands for cont...@bugs.debian.org: > limit source klibc Limiting to bugs with field 'source' containing at least one of 'klibc' Limit currently set to 'source':'klibc' > tags 891924 + pending Bug #891924 [libklibc] klibc: crashes on mips64el if any syscall fails Added tag(s)

Bug#903800: Confirming same problem as Dom0 or DomU

I'm seeing the same behavior; this kernel cannot be used as a Dom0 or DomU kernel on xen-hypervisor-4.8-amd64. So glad for remote IPMI KVM... that was almost a disaster. --Jered

Bug#896725: marked as done (dlmodelbox: missing build dependency on dh-python)

Your message dated Sun, 15 Jul 2018 17:49:05 + with message-id and subject line Bug#896725: fixed in dlmodelbox 0.1.3-1 has caused the Debian Bug report #896725, regarding dlmodelbox: missing build dependency on dh-python to be marked as done. This means that you claim that the problem has

Bug#903328: marked as done (cobertura: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

Your message dated Sun, 15 Jul 2018 17:48:57 + with message-id and subject line Bug#903328: fixed in cobertura 2.1.1-2 has caused the Debian Bug report #903328, regarding cobertura: FTBFS in buster/sid (dh_installdocs: Cannot find "README") to be marked as done. This means that you claim

Processed: reassign 903767 to src:linux, forcibly merging 903767 903800, severity of 903767 is serious

Processing commands for cont...@bugs.debian.org: > reassign 903767 src:linux 4.9.110-1 Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8 Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot Bug #903821 [src:linux]

Processed: forcibly merging 903767 903800

Processing commands for cont...@bugs.debian.org: > forcemerge 903767 903800 Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8 Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64) Bug #903800

Processed: Bug #903328 in cobertura marked as pending

Processing control commands: > tag -1 pending Bug #903328 [src:cobertura] cobertura: FTBFS in buster/sid (dh_installdocs: Cannot find "README") Added tag(s) pending. -- 903328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903328 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#903328: Bug #903328 in cobertura marked as pending

Control: tag -1 pending Hello, Bug #903328 in cobertura reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#903183: marked as done (mygpoclient: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

Your message dated Sun, 15 Jul 2018 16:49:13 + with message-id and subject line Bug#903183: fixed in mygpoclient 1.8-2 has caused the Debian Bug report #903183, regarding mygpoclient: FTBFS in buster/sid (dh_installdocs: Cannot find "README") to be marked as done. This means that you claim

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

Source: linux Version: 4.9.110-1 Followup-For: Bug #903800 I have same problems but on dum0, server reboots forever, by adding no reboot the screen goes black just after the hypervisor loads (instead of reboot) This happens on i7-2600 and i7-4770 4.9.0-6 worked fine I've also upgraded bios but

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

Control: reassign -1 dh-python Control: affect -1 sphinxbase AFAIU the issue is in dh_python3 then, thus reassigning for now. Samuel Thibault, le sam. 14 juil. 2018 22:52:16 +0200, a ecrit: > Paul Gevers, le ven. 13 juil. 2018 13:46:45 +0200, a ecrit: > > I think this is caused by the fact that

Processed: Re: Bug#903698: sphinxbase: build appears broken for multiple python3 versions

Processing control commands: > reassign -1 dh-python Bug #903698 [src:sphinxbase] sphinxbase: build appears broken for multiple python3 versions Bug reassigned from package 'src:sphinxbase' to 'dh-python'. No longer marked as found in versions sphinxbase/0.8+5prealpha+1-2. Ignoring request to

Bug#903829: myspell-bg: Package not installable; upgrades from 4.1-4 impossible

Package: myspell-bg Version: 4.1-5 Severity: serious This change (commit 311c4d9) * make myspell-bg a transitional package depending on hunspell-bg (Closes: #898709) does not work as intended, because hunspell-bg conflicts with myspell-bg. It also prevents migration to testing: $

Bug#903767: verbose kernel log

I'm seeing the same problem with linux-image-4.9.0-7-amd64:4.9.110-1 from the 9.5 point release running on Xen/pvgrub. In case it's useful, here's the verbose kernel log: [2.028120] registered taskstats version 1 [2.028149] zswap: loaded using pool lzo/zbud [2.030226] ima: No TPM

Bug#902897: marked as done (virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED))

Your message dated Sun, 15 Jul 2018 13:04:43 + with message-id and subject line Bug#902897: fixed in virtualbox 5.2.14-dfsg-5 has caused the Debian Bug report #902897, regarding virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED) to be marked as done. This means that you

Bug#903028: closing 903028

close 903028 0.2018.07.13~dfsg0-1 thanks The problem has been solved upstream and a fixed versions is now in unstable.

Processed: closing 903028

Processing commands for cont...@bugs.debian.org: > close 903028 0.2018.07.13~dfsg0-1 Bug #903028 [src:ejabberd-contrib] ejabberd-contrib: FTBFS with ejabberd >= 18.06 The source 'ejabberd-contrib' and version '0.2018.07.13~dfsg0-1' do not appear to match any binary packages Marked as fixed in

Processed: python3-pycuda: fails to install with python 3.7 as a supported python version

Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903528 903527 903457 902794 902989 903388 903522 902757 903030 903031 902761 903784 902715 903526 903145 903529 903525 903218 902766

Bug#903818: marked as done (screen: should not try to link with -lelf)

Your message dated Sun, 15 Jul 2018 12:34:19 + with message-id and subject line Bug#903818: fixed in screen 4.6.2-3 has caused the Debian Bug report #903818, regarding screen: should not try to link with -lelf to be marked as done. This means that you claim that the problem has been dealt

Processed: reassign 903821 to src:linux, forcibly merging 903767 903821, severity of 903821 is serious

Processing commands for cont...@bugs.debian.org: > reassign 903821 src:linux 4.9.110-1 Bug #903821 [xen-hypervisor-4.8-amd64] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64) Bug reassigned from package 'xen-hypervisor-4.8-amd64' to 'src:linux'.

Bug#903826: python3-pycuda: fails to install with python 3.7 as a supported python version

Package: python3-pycuda Version: 2017.1.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a

Bug#903818: screen: should not try to link with -lelf

On 2018-07-15 14:04 +0200, Axel Beckert wrote: > Control: tag -1 + confirmed pending > > Hi Sven, > > I just noticed the following: > > Sven Joachim wrote: >> , >> | $ dpkg-deb -f screen-udeb_4.6.2-2_i386.udeb Depends >> | libc6-udeb (>= 2.27), libelf1 (>= 0.132), libtinfo6-udeb (>= 6.1) >>

Bug#903825: xserver-xorg-video-sunffb: sparc64 architecture is disabled

Package: xserver-xorg-video-sunffb Version: 1:1.2.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, Debian has dropped support for the sparc (32-bit) architecture some time ago, but a dedicated debian-ports team has started working on a sparc64 port. Since this port

Bug#867886: marked as done (python-neovim: build sometimes hangs with python 3.6 as supported version)

Your message dated Sun, 15 Jul 2018 13:53:30 +0200 with message-id <9e9688bd-6339-d24a-b337-e5c6e9b3e...@viccuad.me> and subject line has caused the Debian Bug report #867886, regarding python-neovim: build sometimes hangs with python 3.6 as supported version to be marked as done. This means

Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)

Dear Gianfranco, thank you very much for your fix indeed. It works like a charm on my siduction box. You really saved my a... . Best wishes jk On Thu, 12 Jul 2018 08:52:59 + (UTC) Gianfranco Costamagna wrote: > Hello, > > > >VMMR0.r0 has been built (presumably due to the recent binutils

Processed: Re: Bug#903818: screen: should not try to link with -lelf

Processing control commands: > tag -1 + confirmed pending Bug #903818 [src:screen] screen: should not try to link with -lelf Added tag(s) pending and confirmed. -- 903818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903818 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#903818: screen: should not try to link with -lelf

Control: tag -1 + confirmed pending Hi Sven, I just noticed the following: Sven Joachim wrote: > , > | $ dpkg-deb -f screen-udeb_4.6.2-2_i386.udeb Depends > | libc6-udeb (>= 2.27), libelf1 (>= 0.132), libtinfo6-udeb (>= 6.1) > ` So this seems to stem from being build in a not so clean

Bug#867886: (no subject)

closes 867886 thanks Just uploaded a new version, with upstream 0.2.6. With the move to pytest and the redoing of tests, I have not seen this behavior again. Closing this bug so the package migrates; I will keep looking at https://tests.reproducible-builds.org/debian/history/python-neovim.html

Processed: bug 903818 is forwarded to https://lists.gnu.org/archive/html/screen-devel/2018-07/msg00003.html

Processing commands for cont...@bugs.debian.org: > forwarded 903818 > https://lists.gnu.org/archive/html/screen-devel/2018-07/msg3.html Bug #903818 [src:screen] screen: should not try to link with -lelf Set Bug forwarded-to-address to

Processed: tagging 903818

Processing commands for cont...@bugs.debian.org: > # Has been accidentially reverted again at upstream > tags 903818 - fixed-upstream Bug #903818 [src:screen] screen: should not try to link with -lelf Removed tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

Hi, I am having the same issue. After upgrade to 4.9.0-7-amd64 from 4.9.0-6-amd64 my xen vm they stop working. I run xenserver 6.2 and as a temporal fix I just convert the VM to HVM from PV xe vm-param-set uuid=YOURVMUID HVM-boot-policy="BIOS order" PV-bootloader="" So looks like running in

Processed: Re: Bug#903818: screen: should not try to link with -lelf

Processing control commands: > severity -1 serious Bug #903818 [src:screen] screen: should not try to link with -lelf Severity set to 'serious' from 'normal' > tag -1 + upstream Bug #903818 [src:screen] screen: should not try to link with -lelf Added tag(s) upstream. -- 903818:

Bug#903821: Re : xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

Hi, If you prefer, you can find a kernel panic screenshot from R720 Dell server's : https://s33.postimg.cc/b2t056y8f/S_lection_027.png Best regards Benoît

Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

Package: xen-hypervisor-4.8-amd64 Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 Severity: critical Justification: breaks the whole system Dear Maintainer, After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I notice a kernel panic on these 3 servers. If I boot xen hypervisor

Bug#903631: openjdk-11: FTBFS on several architectures: dh_install: Cannot find (any matches for) "usr/lib/jvm/java-11-openjdk-armel/bin/jhsdb"

Hi Matthias, On 12/07/18 10:52, Emilio Pozuelo Monfort wrote: > openjdk-11 11~21 failed to build on several architectures due to missing > jhsdb. Either that should be enabled on them (if possible) or not > installed. This is still not fixed for armel,mips64el,mipsel. Cheers, Emilio

Bug#903070: marked as done (haproxyctl FTBFS: update Build-Depends: ruby-ronn -> ronn)

Your message dated Sun, 15 Jul 2018 08:48:52 + with message-id and subject line Bug#903070: fixed in haproxyctl 1.3.0-3 has caused the Debian Bug report #903070, regarding haproxyctl FTBFS: update Build-Depends: ruby-ronn -> ronn to be marked as done. This means that you claim that the

Bug#903070: Bug #903070 in haproxyctl marked as pending

Control: tag -1 pending Hello, Bug #903070 in haproxyctl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #903070 in haproxyctl marked as pending

Processing control commands: > tag -1 pending Bug #903070 [src:haproxyctl] haproxyctl FTBFS: update Build-Depends: ruby-ronn -> ronn Added tag(s) pending. -- 903070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 728144 squid3 squid3/3.3.8-1 Bug #728144 [squid3] squid3: Pinger Segmentation fault in Debug::finishDebug on delete CurrentDebug; Bug #771778 [squid3] squid3: Pinger segfault with libc Ignoring request to reassign bug #728144 to the

Bug#903784: marked as done (python3-pycsw: fails to install: SyntaxError)

Your message dated Sun, 15 Jul 2018 08:36:16 + with message-id and subject line Bug#903784: fixed in pycsw 2.2.0+dfsg-4 has caused the Debian Bug report #903784, regarding python3-pycsw: fails to install: SyntaxError to be marked as done. This means that you claim that the problem has been

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

On 2018-07-15 04:27:39 +0100, Ben Hutchings wrote: > On Sun, 2018-07-15 at 02:27 +0200, Vincent Lefevre wrote: > > Package: src:linux > > Version: 4.9.110-1 > > Severity: critical > > Justification: breaks the whole system > > > > After upgrade to Debian 9.5, I get a kernel panic with

Processed: tagging 903784

Processing commands for cont...@bugs.debian.org: > tags 903784 + pending Bug #903784 [python3-pycsw] python3-pycsw: fails to install: SyntaxError Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 903784:

Bug#903788: znc: path traversal flaw

Control: retitle -1 znc: CVE-2018-14056: path traversal flaw On Sat, Jul 14, 2018 at 10:02:58PM +0200, Salvatore Bonaccorso wrote: > Source: znc > Version: 0.045-1 > Severity: grave > Tags: patch security upstream > Justification: user security hole > > Hi > > See

Processed: Re: Bug#903788: znc: path traversal flaw

Processing control commands: > retitle -1 znc: CVE-2018-14056: path traversal flaw Bug #903788 [src:znc] znc: path traversal flaw Changed Bug title to 'znc: CVE-2018-14056: path traversal flaw' from 'znc: path traversal flaw'. -- 903788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903788

Processed: Re: Bug#903787: znc: privilege escalation to admin permission (injection of rogue values in znc.conf)

Processing control commands: > retitle -1 znc: CVE-2018-14055: privilege escalation to admin permission > (injection of rogue values in znc.conf) Bug #903787 [src:znc] znc: privilege escalation to admin permission (injection of rogue values in znc.conf) Changed Bug title to 'znc:

Bug#903787: znc: privilege escalation to admin permission (injection of rogue values in znc.conf)

Control: retitle -1 znc: CVE-2018-14055: privilege escalation to admin permission (injection of rogue values in znc.conf) On Sat, Jul 14, 2018 at 10:01:02PM +0200, Salvatore Bonaccorso wrote: > Source: znc > Version: 1.6.5-1 > Severity: grave > Tags: patch security upstream > Justification: user