PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-02-07 14:06:33 +00:00
Code Issues Projects Releases Wiki Activity

Remove nmap-update

Browse Source 
This feature was never publicly released, and has not been distributed
in our binary builds for a couple versions now. It needed to be removed
in order to reduce the number of places Nmap looks for data files. See #2051
This commit is contained in:
dmiller
2020-08-27 19:13:31 +00:00
parent 2520edd8fe
commit 210adf941e
32 changed files with 18 additions and 8411 deletions
Download Patch File Download Diff File Expand all files Collapse all files

270
docs/3rd-party-licenses.txt
View File

@@ -32,9 +32,6 @@ On all platforms, Nmap is normally linked with:
http://www.openssl.org/
o LIBLINEAR. Used for IPv6 OS classifiction.
http://www.csie.ntu.edu.tw/~cjlin/liblinear/
o libsvn. The Subversion library, used by the updater program
nmap-update. http://subversion.apache.org/
o APR (Apache Portable Runtime). Used by libsvn. http://apr.apache.org/
On Windows only, Nmap uses:
o WinPcap: libpcap for Windows. The libpcap license applies to WinPcap,
@@ -371,273 +368,6 @@ License of OpenSSL
========
License of libsvn and APR.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
SUBVERSION SUBCOMPONENTS:
Subversion includes a number of subcomponents with separate copyright
notices and license terms. Your use of the source code for the these
subcomponents is subject to the terms and conditions of the following
licenses.
For portions of the Python bindings test suite at
subversion/bindings/swig/python/tests/trac/:
I. Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
II. Copyright (C) 2003, 2004, 2005 Edgewall Software
Copyright (C) 2003, 2004, 2005 Jonas Borgström <jonas@edgewall.com>
Copyright (C) 2005 Christopher Lenz <cmlenz@gmx.de>
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
the documentation and/or other materials provided with the
distribution.
3. The name of the author may not be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
========
License of WinPcap
Copyright (c) 1999 - 2005 NetGroup, Politecnico di Torino (Italy).

45
docs/3rd-party.xml
View File

@@ -2,7 +2,6 @@
<!-- Info regarding third-party open source software included in Nmap. -->
<!-- TODO:
* Software and versions used in Zenmap on OS X
* Software and versions used in nmap-update
-->
<!DOCTYPE licenses [
<!ENTITY nmap_version "7.25SVN">
@@ -38,7 +37,6 @@
<!ENTITY license_mpl_11 SYSTEM "licenses/MPL-1.1">
<!ENTITY license_openssl SYSTEM "licenses/OpenSSL">
<!ENTITY license_python SYSTEM "https://docs.python.org/2.7/license.html">
<!ENTITY license_apache2 SYSTEM "https://www.apache.org/licenses/LICENSE-2.0">
]>
<licenses>
@@ -191,29 +189,6 @@
python="&python_version;"
</file>
</package>
<package>
<name>nmap-update</name>
<version>&nmap_version;</version>
<url>https://nmap.org/</url>
<license>&nmap_license;</license>
<file name="nmap-&nmap_version;.tar.bz2">
<alt name="nmap-&nmap_version;.tgz" />
<alt name="nmap-&nmap_version;-1.src.rpm" />
</file>
<file name="nmap-&nmap_version;-setup.exe">
openssl="&openssl_version;" subversion apr aprutil sqlite zlib serf
</file>
<file name="nmap-&nmap_version;-win32.zip">
openssl="&openssl_version;" subversion apr aprutil sqlite zlib serf
</file>
<file name="nmap-update-&nmap_version;-1.x86_64.rpm">
<alt name="nmap-update-&nmap_version;-1.i686.rpm" />
openssl="&openssl_version;" subversion apr aprutil sqlite zlib serf
</file>
<file name="nmap-&nmap_version;.dmg">
openssl="&openssl_version;" subversion apr aprutil sqlite zlib serf
</file>
</package>
</submodules>
<thirdparty>
<package id="slaxml">
@@ -295,24 +270,6 @@
<copyright>Roy Hills</copyright>
<license>&license_bsd_simplified;</license>
</package>
<package id="subversion">
<name>Apache Subversion</name>
<url>https://subversion.apache.org/</url>
<copyright>Apache Software Foundation</copyright>
<license>&license_apache2;</license>
</package>
<package id="apr">
<name>Apache Portable Runtime</name>
<url>https://apr.apache.org/</url>
<copyright>Apache Software Foundation</copyright>
<license>&license_apache2;</license>
</package>
<package id="aprutil">
<name>Apache Portable Runtime Utility</name>
<url>https://apr.apache.org/</url>
<copyright>Apache Software Foundation</copyright>
<license>&license_apache2;</license>
</package>
<package id="sqlite">
<name>SQLite</name>
<url>https://sqlite.org/</url>
@@ -320,7 +277,5 @@
</package>
<package id="zlib">
</package>
<package id="serf">
</package>
</thirdparty>
</licenses>

99
docs/nmap-update.1
View File

@@ -1,99 +0,0 @@
'\" t
.\" Title: nmap-update
.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 08/12/2019
.\" Manual: nmap-update Reference Guide
.\" Source: nmap-update
.\" Language: English
.\"
.TH "NMAP\-UPDATE" "1" "08/12/2019" "nmap\-update" "nmap\-update Reference Guide"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
nmap-update \- Updater for Nmap\*(Aqs architecture\-independent files
.SH "SYNOPSIS"
.HP \w'\fBnmap\-update\fR\ 'u
\fBnmap\-update\fR [\fIoptions\fR] [\fIchannel\fR]
.SH "DESCRIPTION"
.PP
nmap\-update is an updater for Nmap\*(Aqs architecture\-independent files\&. It is used to keep up to date with changes and new scripts for the Nmap Scripting Engine\&.
.PP
Updates are distributed in the form of
\(lqchannels\(rq, which are named directories that usually correspond to Nmap version numbers\&. When nmap\-update is installed, it will pull from the channel corresponding to the version of Nmap it was installed with, until Nmap and nmap\-update are upgraded as a whole\&.
.PP
The program works by updating from a remote Subversion repository\&. To supply authentication credentials, create a configuration file:
.RS 4 /home/\fIuser\fR/\&.nmap/nmap\-config\&.conf on non\-Windows systems, or .RE .RS 4 C:\eUsers\e\fIuser\fR\eAppData\eRoaming\enmap\enmap\-config\&.conf on Windows\&. .RE
The contents of the file should be:
.sp
.if n \{\
.RS 4
.\}
.nf
username = \fIusername\fR
password = \fIpassword\fR
.fi
.if n \{\
.RE
.\}
.sp
Alternatively, you can cache your credentials more securely if you have the
\fBsvn\fR
command\-line program installed\&. Run the command
\fBsvn ls https://svn\&.nmap\&.org/updates\fR, enter your credentials, and agree to cache them when asked\&.
.SH "OPTIONS SUMMARY"
.PP
\fB\-d \fR\fB\fIdirectory\fR\fR
.RS 4
Install to
\fIdirectory\fR\&. Normally installation goes to a suitable place under your home directory:
\&.nmap/updates/\fIchannel\fR
on Unix and
AppData\eRoaming\enmap\eupdates\e\fIchannel\fR
on Windows\&. This option can be used by root to install updates system\-wide\&.
.RE
.PP
\fB\-h\fR, \fB\-\-help\fR
.RS 4
Show a help message and exit\&.
.RE
.PP
\fB\-r\fR, \fB\-\-repo\fR \fIrepository\fR
.RS 4
Use the given repository and path rather than the default\&. For example,
\fB\-\-repo https://svn\&.example\&.com/updates\fR\&.
.RE
.PP
\fB\-\-username\fR \fIusername\fR
.RS 4
Authenticate with the given username\&.
.RE
.PP
\fB\-\-password\fR \fIpassword\fR
.RS 4
Authenticate with the given password\&.
.RE
.PP
\fB\-v\fR, \fB\-\-verbose\fR
.RS 4
Be more verbose\&. Show the used channel and repository\&.
.RE
.PP
Any other arguments are taken to be the names of channels to load from\&. The channels are tried in order until one is successful\&.

125
docs/nmap-update.xml
View File

@@ -1,125 +0,0 @@
<refentry id='man-nmap-update'>
<refmeta>
<refentrytitle>nmap-update</refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo class="source">nmap-update</refmiscinfo>
<refmiscinfo class="manual">nmap-update Reference Guide</refmiscinfo>
</refmeta>
<refnamediv id='man-name'>
<refname>nmap-update</refname>
<refpurpose>Updater for Nmap's architecture-independent files</refpurpose>
</refnamediv>
<refsynopsisdiv id='man-synopsis'>
<cmdsynopsis>
<command>nmap-update</command>
<arg choice='opt'>
<replaceable>options</replaceable>
</arg>
<arg choice='opt' repeat='rep'>
<replaceable>channel</replaceable>
</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 id='man-description'>
<title>Description</title>
<para>
nmap-update is an updater for Nmap's architecture-independent files. It is
used to keep up to date with changes and new scripts for the Nmap Scripting
Engine.
</para>
<para>
Updates are distributed in the form of <quote>channels</quote>, which are
named directories that usually correspond to Nmap version numbers. When
nmap-update is installed, it will pull from the channel corresponding to the
version of Nmap it was installed with, until Nmap and nmap-update are
upgraded as a whole.
</para>
<para>
The program works by updating from a remote Subversion repository. To supply
authentication credentials, create a configuration file:
<simplelist>
<member><filename>/home/<replaceable>user</replaceable>/.nmap/nmap-config.conf</filename>
on non-Windows systems, or</member>
<member><filename>C:\Users\<replaceable>user</replaceable>\AppData\Roaming\nmap\nmap-config.conf</filename>
on Windows.</member>
</simplelist>
The contents of the file should be:
<programlisting>
username = <replaceable>username</replaceable>
password = <replaceable>password</replaceable>
</programlisting>
Alternatively, you can cache your credentials more securely if you have the
<command>svn</command> command-line program installed. Run the command
<command>svn ls https://svn.nmap.org/updates</command>, enter your
credentials, and agree to cache them when asked.
</para>
</refsect1>
<refsect1 id='man-briefoptions'>
<title>Options Summary</title>
<variablelist>
<varlistentry>
<term><option>-d <replaceable>directory</replaceable></option></term>
<listitem>
<para>
Install to <filename><replaceable>directory</replaceable></filename>.
Normally installation goes to a suitable place under your home
directory:
<filename>.nmap/updates/<replaceable>channel</replaceable></filename>
on Unix and
<filename>AppData\Roaming\nmap\updates\<replaceable>channel</replaceable></filename>
on Windows. This option can be used by root to install updates
system-wide.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-h</option></term>
<term><option>--help</option></term>
<listitem>
<para>Show a help message and exit.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-r</option></term>
<term><option>--repo</option> <replaceable>repository</replaceable></term>
<listitem>
<para>Use the given repository and path rather than the default.
For example, <option>--repo https://svn.example.com/updates</option>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>--username</option> <replaceable>username</replaceable></term>
<listitem>
<para>Authenticate with the given username.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>--password</option> <replaceable>password</replaceable></term>
<listitem>
<para>Authenticate with the given password.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-v</option></term>
<term><option>--verbose</option></term>
<listitem>
<para>Be more verbose. Show the used channel and repository.</para>
</listitem>
</varlistentry>
</variablelist>
<para>
Any other arguments are taken to be the names of channels to load from. The
channels are tried in order until one is successful.
</para>
</refsect1>
<!--
<refsect1 id='man-legal'>
&legal-notices;
</refsect1>
-->
</refentry>