On 2017-02-18 15:31:07, Moritz Mühlenhoff wrote:
> On Sat, Feb 18, 2017 at 01:22:19AM +0100, Bálint Réczey wrote:
>> Were there any reason for handling the last CVE very quickly? I can
>> catch up with the changes in Jessie.
>
> No. It's totally harmless, for jessie let's also line this one up in
On Sat, Feb 18, 2017 at 01:22:19AM +0100, Bálint Réczey wrote:
> Were there any reason for handling the last CVE very quickly? I can
> catch up with the changes in Jessie.
No. It's totally harmless, for jessie let's also line this one up in
git for the next Wireshark advisory round.
Cheers,
Hi All,
Thank you for the upload, but I would have happily handled the CVE
since I have already prepared
other CVE-s for the next batch in the packaging repository.
I saw the email on my phone but I expected longer timeout for waiting
for my response.
There is also debian/README.Debian.security
Hello dear maintainer(s),
the Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of wireshark:
https://security-tracker.debian.org/tracker/source-package/wireshark
Would you like to take care of this yourself?
If yes, please follow the workflow
