Bug#962105: znc: CVE-2020-13775

03.06.2020 11:25, Salvatore Bonaccorso пишет: > Source: znc > Version: 1.8.0-1 > Severity: important > Tags: security upstream > > Hi, > > The following vulnerability was published for znc. > > CVE-2020-13775[0]: > | ZNC before 1.8.1-rc1 allows attackers to trigger an application crash > |

Bug#925270: znc unwisely advertises exact Debian version

22.03.2019 8:08, Uli Schlachter пишет: > Hi, > > On 22.03.19 00:53, T. Joseph Carter wrote: >> <-- nick (~u@h) has quit (Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in) >> <-- nick (~u@h) has quit (Quit: ZNC 1.6.6+deb1ubuntu0.1 - http://znc.in) >> <-- nick (~u@h) has quit (Quit: ZNC

Bug#914783: Switch znc to cmake build

Package: znc Version: 1.7.1-2+b1 Hi Patrick Upstream added support for CMake in 1.7.0, and soft-deprecated autoconf. That is, eventually configure.ac will be removed, but for now, both are available, and configure.ac simply doesn't get any new features. E.g. i18n is now available only if ZNC was

Bug#820517: (no subject)

Hi Can we just drop znc-tcl package? It's not necessary for the rest of ZNC, and is rarely used. But I'm going to release ZNC 1.7 soon where this is fixed. -- Best regards, Alexey "DarthGandalf" Sokolov

Bug#858205: Update ZNC package to 1.6.5

|2 > 15 files changed, 4478 insertions(+), 3574 deletions(-) > > > Am 28.03.2017 um 13:32 schrieb Alexey Sokolov: >> Hi Patrick, >> Are you looking at the right versions? >> https://github.com/znc/znc/compare/znc-1.6.4...znc-1.6.5 is much >

Bug#858205: Update ZNC package to 1.6.5

Hi Patrick, Are you looking at the right versions? https://github.com/znc/znc/compare/znc-1.6.4...znc-1.6.5 is much smaller than what you've shown. 2017-03-28 11:19 GMT+01:00 Patrick Matthäi : > Am 19.03.2017 um 19:41 schrieb Thomas Ward: >> Source: znc >> Severity: wishlist

Bug#734442: patch

> Cool. Outside of packaging, there are probably some hardening options > that would be useful to add. Have you considered adding socket > activation support, sd_notify and syslogging support to make this work > a little better with systemd? I'd be happy to contribute some > patches. Unless there

Bug#734442: patch

, or e.g. a env variable used by ./configure... 29.12.2015 22:30, Eric Dorland пишет: > * Alexey Sokolov (ale...@asokolov.org) wrote: >> Hi Eric, Does the service file need to be different from the >> included one? >> (https://github.com/znc/znc/blob/master/znc.service.in) &

Bug#734442: patch

Hi Eric, Does the service file need to be different from the included one? (https://github.com/znc/znc/blob/master/znc.service.in) Also please check the recent discussion about it at https://github.com/znc/znc/issues/1165

Bug#804618: znc: FTBFS: error: ‘SSLv3_client_method’ was not declared in this scope

Hi, This is fixed upstream in upcoming 1.6.2. I hope to release it in several days. Upstream reference: https://github.com/znc/znc/issues/1146 2015-11-09 21:25 GMT+00:00 Chris West (Faux) : > Source: znc > Version: 1.6.1-1 > Severity: serious > Justification: fails

Bug#672035: using std::pair

I am unsure though if this is really the issue that building znc runs into. It seems to happen only with using std::pair, which the znc sources do not do. ZNC has this statement in Utils.h, which is %include'd to modpython.i Your patch to modpython.i got merged to upstream ZNC, thanks. So I

Bug#672035: [Swig-user] Using own string class

27.05.2012 04:14, William S Fulton пишет: I can't replicate this bug with 2.0.6, you are going to have to provide a test case. swig-2.0.5 introduced a regression which was fixed in 2.0.7 - incorrect typemaps for templates were being used in conjunction with typedef. Please try 2.0.7 and report

Bug#672035: Using own string class

Hello! At ZNC we have an own string class CString, which is inherited from std::string. The goal is to use it as a just string in target languages. How to do that properly? When I was writing modperl and modpython ZNC modules, I used an approach described at

Bug#666405: Info received (Backtraces of the crash, on ZNC with Android client)

(gdb) info reg rax0xdf7acb17 3749366551 rbx0xff2d -211 rcx0x79 121 rdx0x0 0 rsi0x12 18 rdi0x98b3f8 10007544 rbp0x985a5a 0x985a5a rsp0x7fffd680 0x7fffd680

Bug#666405: Fwd: Re: [Pkg-openssl-devel] Bug#666405: Info received (Backtraces of the crash, on ZNC with Android client)

I was building openssl from debian wheezy sources, with that patch applied... It seems that it helps, yes. PS. Ups, sent the letter to the wrong address first time. signature.asc Description: OpenPGP digital signature

Bug#565380: fix

Current Terence's implementation violates CAP specs. Now xchat looks only to first capability returned by server. This patch makes xchat to look the whole cap list, not only the first one. http://ssh.shellium.org/~somebody/xchat.patch.txt -- To UNSUBSCRIBE, email to