> Summary (for quoting here): Unless there are disagreements I will mark
> inspircd as unsupported in LTS in a few days or so.
Done.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Guillaume Delacour wrote:
> Yes, but lamby seems to be working on that [0].
> @lamby: do you want to handle this ?
It seems like you didn't get my previous mail. Sorry about that. Here
is the link:
https://lists.debian.org/debian-lts/2016/09/msg00076.html
Summary (for quoting here): Unless th
Hello,
Le 07/09/2016 à 00:00, Balint Reczey a écrit :
> Hello dear maintainer(s),
>
> the Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of inspircd:
> https://security-tracker.debian.org/tracker/CVE-2016-7142
>
> Would you like to take car
Ben Hutchings wrote:
> > I had an interesting conversation with the inspircd maintainers
> > recently, over IRC: they are basically saying that 2.0.5 is full of
> > security holes, and they do not bother with issuing CVEs, so it's really
> > hard to tell what version if affected by what.
>
> This
On Tue, 2016-09-06 at 22:28 -0400, Antoine Beaupré wrote:
> I am a bit surprised to see this - are ircd packages sponsored now?
> There's a similar issue in Charybdis and I deliberately marked it as
> unsupported in LTS because, AFAIK, no customer expressed the need to
> support those yet.
If Free
Hi
The LTS team also tries to fix security holes in all packages. Not
only the ones explicitly expressed a need for by the customers. The
ones expressed a need for always have a higher priority.
However if it is like you write that 2.0.5 is full of security holes
and nobody have expressed a need,
I am a bit surprised to see this - are ircd packages sponsored now?
There's a similar issue in Charybdis and I deliberately marked it as
unsupported in LTS because, AFAIK, no customer expressed the need to
support those yet.
I'd be glad to see if we can update charybdis in Wheezy as well, but to
b
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of inspircd:
https://security-tracker.debian.org/tracker/CVE-2016-7142
Would you like to take care of this yourself?
If yes, please follow the workflow we have defin