[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#964228: marked as done (buster-pu: package nmap/7.70+dfsg1-6+deb10u1)

Your message dated Sat, 01 Aug 2020 12:51:28 +0100
with message-id <43535efb498a168cf81452ca0c326f004f46adc6.camel@adam-barratt.org.uk>
and subject line Closing bugs for fixes included in 10.5 point release
has caused the Debian Bug report #964228,
regarding buster-pu: package nmap/7.70+dfsg1-6+deb10u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
964228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964228
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu

A backported upstream patch [0] is required to fix #940284 [1] on nmap;
Bug title: autogeneration of ssl key in ssl server mode of ncat is broken

The issue itself is well described in both BTS [1] and the upstream
bug report [2], but the summary of it is that the openssl shipped with
Buster requires a key with minimum size of 2048b, while nmap 7.70
generates one sized 1024b. This has been fixed in 7.80 (which is the
version on Testing right now).

The debdiff is attached to this email,

Thanks,

[0] https://github.com/nmap/nmap/commit/25db5fbb0d8fb88b6e7f4f298c862cd05ed0f8b1
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940284
[2] https://github.com/nmap/nmap/pull/1310

-- 
Samuel Henrique <samueloph>

Attachment: nmap_7.70+dfsg1-6+deb10u1.debdiff
Description: Binary data


--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 10.5

Hi,

Each of these bugs relates to an update that was included in today's
stable point release.

Regards,

Adam

--- End Message ---
Reply to: