Please sync nmap 4.50-4 (main) from Debian unstable (main)

Bug #178888 reported by Marco Rodrigues
16
Affects Status Importance Assigned to Milestone
nmap (Ubuntu)
Fix Released
Wishlist
LaMont Jones

Bug Description

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 affects ubuntu/nmap
 status New
 importance wishlist
 subscribe dholbach
 subscribe norsetto

Please sync nmap 4.20-2 (main) from Debian unstable (main).
Changelog since current hardy version 4.20-3:

nmap (4.50-4) unstable; urgency=low

  * control: zenmap Depends: python-pysqlite2. Closes: #457694

 -- LaMont Jones <email address hidden> Tue, 25 Dec 2007 09:06:55 -0700

nmap (4.50-3) unstable; urgency=low

  * use global copyright file for zenmap

 -- LaMont Jones <email address hidden> Sat, 22 Dec 2007 11:14:17 -0700

nmap (4.50-2) unstable; urgency=low

  * copyright: incorporate remaining copyright info from upstream

 -- LaMont Jones <email address hidden> Sat, 22 Dec 2007 09:37:25 -0700

nmap (4.50-1) unstable; urgency=low

  [Fyodor]

  * New upstream release. Many changes. Closes: #456232

  [LaMont Jones]

  * debian/rules: nmapfe migration
  * build: properly target install
  * build: finish cleaning up the build process, I hope.
  * meta: drop usr/share/pixmaps/ubuntu.svg, collides with gnome-screensaver
  * meta: zenmap Conflicts/Replaces/Provides nmapfe
  * rules: sed hack: remove build directory from python code

 -- LaMont Jones <email address hidden> Thu, 13 Dec 2007 13:39:44 -0700

nmap (4.49~rc7-1) experimental; urgency=low

  * New upstream

 -- LaMont Jones <email address hidden> Tue, 11 Dec 2007 07:25:17 -0700

nmap (4.49~rc6-1) experimental; urgency=low

  * New upstream release

 -- LaMont Jones <email address hidden> Tue, 27 Nov 2007 06:07:37 -0700

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHc8hXQGoC3MKACe8RAtbmAJ9AhroJvofbdjEsptxAB/4UuBV5kACeNaGj
OSuXVWZ/LmM9gl9+HAyHIhc=
=MtWe
-----END PGP SIGNATURE-----

Revision history for this message
Marco Rodrigues (gothicx) wrote :

The last version in Hardy 4.20-2 is auto-synced.

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

The last version in hardy is 4.20-3 (not 4.20-2) and you are requesting to sync 4.50-4 (not 4.20-2, you corrected the title but not the description).
Can you explain why you are requesting this sync?
Note that J. Lamont is also an ubuntu core-dev .....

Revision history for this message
Marco Rodrigues (gothicx) wrote :

It was a typo.. yes.. it's 4.20-3. I don't touch normally the description, because that will break the SHA-1 encryption in the message.

I'm requesting this, because others ubuntu users want it, like I saw in nmap 4.50 upstream release day, they come to #ubuntu-motu asking for it.
After it goes to hardy, it can also be backport to gutsy (if there isn't any problem building it).

I know "lamont" is a ubuntu core-dev and debian developer :) I reported him when 4.50 comes out from upstream in Debian. I think he doesn't have any problem to someone like me request it to be synced.

Revision history for this message
LaMont Jones (lamont) wrote :

I was waiting for the package to stablize a bit more before I requested the sync myself. It would be preferable if 4.50-4 could be synced.

LaMont Jones (lamont)
Changed in nmap:
assignee: nobody → lamont
status: New → Confirmed
Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Reading highlights from
http://insecure.org/stf/Nmap-4.50-Release.html
before final decision might be a good idea.

I think the most important reasons for upgrade are
that the version currently in Ubuntu has an obsolete
GUI and an obsolete OS detection subsystem. Spending
one LTS support period for learning a GUI that will go
away and submitting OS finger prints to /dev/null
doesn't make lots of sense.

Also, as a rather interesting detail, 4.5 has been made
more friendly towards female users.

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

For the release note regarding friendliness towards
female users search for "Political correctness" at
http://insecure.org/stf/Nmap-4.50-Release.html

Revision history for this message
Caroline Ford (secretlondon) wrote :

Political correctness
    To cultivate a professional image, we long ago capitalized all references to God in error message text and also reworded all instances of “fucked up” to “borked”. We have now also changed this warning message: “TCP/IP fingerprinting (for OS scan) requires root privileges. Sorry, dude.” A woman reported that it was “highly offensive and sexist”, that “times have changed and many women now use your software”, and “a sexist remark like the one above should have no place in software.”

I doubt anyone has issues with being called "dude"...

Revision history for this message
Melissa Draper (melissa) wrote :

While I agree that it is more inconsiderate than offensive, I do recall there being problems with the use of 'chaps' as a term of endearment at some point. The term 'dude' is equally gender-specific.

Revision history for this message
Leigh Honeywell (hypatia) wrote : Re: [Bug 178888] Re: Please sync nmap 4.50-4 (main) from Debian unstable (main)

On Wed, Jan 02, 2008 at 02:52:09PM -0000, Caroline Ford wrote:
> I doubt anyone has issues with being called "dude"...

Someone had issue enough with it to write to Fyodor (the nmap author)
and request that it be changed. I think it's a positive change :)

Revision history for this message
towsonu2003 (towsonu2003) wrote :

Caroline Ford wrote:
...
>
> I doubt anyone has issues with being called "dude"...
>

It's part of the male norm in the language... Well known examples: all
classical sociology and philosophy texts use "he" and "man" to refer to
humanity. But guess what, humanity is not all-male, and its standard
therefore can't be male-ness... The social male-ness standard is there
due to hegemonic power differences...

The slang "dude" is no different, but less researched by feminist
scholars, hence less publicized as part of the male-as-norm linguistic
pattern...

Of course, when one looks at this stuff with the hypocritical-by-nature
term "political correctness" as one's mindset, nothing is problematic.
After all, according to this mindset, we shouldn't use "bitch", "negro"
et al. not because of their linguistic load (connections to hegemony),
but simply because they are politically "incorrect".

Unfortunately, at some point, everyone just forgot that the reason these
and other linguistic patterns were attacked wasn't because they were
"offensive", but because they were inextricably linked to social
patterns of oppression...

Revision history for this message
Dabian (dabian) wrote :

To sum up ... if I got this right.

We want this changed, not because its political incorrect, but because this kind of gender specific language is linked to a tradition of suppressing women.

Unfortunately our culture has a tradition of ignoring women, and especially ignoring their technical, political and other contributions.

This is reflected in our everyday language, for instance by using "male-one" words like "dude", even when the audience actually consists of both genders.

One part of securing equal rights for men and women is to change that where we can.

--
Women will no longer be ignored.

Revision history for this message
William Pitcock (nenolod) wrote :

While I'm glad to hear that nmap developers have made a change
to make their error messages more politically correct, I think that
we should concentrate on the technical merits of upgrading the
nmap package only.

After all, if the error messages are more important than the technical
merits, we can easily patch the error messages in the current version
of nmap offered in Ubuntu.

Revision history for this message
Leigh Honeywell (hypatia) wrote :

On Wed, Jan 02, 2008 at 09:59:15PM -0000, William Pitcock wrote:
> While I'm glad to hear that nmap developers have made a change
> to make their error messages more politically correct, I think that
> we should concentrate on the technical merits of upgrading the
> nmap package only.
>
> After all, if the error messages are more important than the technical
> merits, we can easily patch the error messages in the current version
> of nmap offered in Ubuntu.

Whoever said they were "more" important? They are just both positive
changes to the package :)

That said, the latest is now 4.52, no 4.50, in case anyone is actually
going to package the newer version.

-Leigh

Revision history for this message
Melissa Draper (melissa) wrote :

William,

If you read up to what toni said, the main reason to upgrade was given as "the version currently in Ubuntu has an obsolete GUI and an obsolete OS detection subsystem." and the PC stuff was meantioned as a pleasant and encouraging aside.

Also note that if you want to patch similar PC stuff from other packages, you are most welcome to do so :)

Revision history for this message
William Pitcock (nenolod) wrote :

Hi Melissa,

I realise that point. My purpose was sort of a friendly reminder that this
is a bug report, and not a place for discussing whether or not the word
"dude" is politically correct or not, and nothing more.

I do think it's an amusing thing to read in a changelog entry though, and
probably for the better: nmap has had a reputation of being somewhat
childish (calling people "dude", saying things are "fucked up", etc) in it's
error messages.

As for nmap 4.52, it's not yet in Debian I don't think, so we'd be looking
at nmap 4.52-0ubuntu1, and I'm not sure how lamont feels about that, so
we should probably just leave that to him.

Revision history for this message
Fabio Parri (parrif-ibb) wrote :

I agree, nmap should be update to 4.5x with zenmap instead of the obsolete nmapfe :)

Revision history for this message
Martin Pitt (pitti) wrote :

synced

Changed in nmap:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.