Documentation: convert http URLS to https
Remove some dead links or point them to archive.org while at it. All updated links have been verified. Change-Id: Icf02167a13d5fe9dfce39ea57525b3f185554c9d Reviewed-on: https://code.wireshark.org/review/34028 Petri-Dish: Peter Wu <peter@lekensteyn.nl> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
This commit is contained in:
Peter Wu
Anders Broman
parent
36e1f782aa
commit
c88e525168
|
|
@ -54,7 +54,7 @@ S<B<--remote-interface>=E<lt>the router interfaceE<gt>>
|
|||
B<ciscodump> is an extcap tool that relys on Cisco EPC to allow a user to run a remote capture
|
||||
on a Cisco router in a SSH connection. The minimum IOS version supporting this feature is 12.4(20)T. More details can be
|
||||
found here:
|
||||
http://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-embedded-packet-capture/datasheet_c78-502727.html
|
||||
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-embedded-packet-capture/datasheet_c78-502727.html
|
||||
|
||||
Supported interfaces:
|
||||
|
||||
|
|
@ -120,7 +120,12 @@ recommended to use keyfiles with a SSH agent.
|
|||
|
||||
=item --remote-filter=E<lt>filterE<gt>
|
||||
|
||||
The remote filter on the router. This is a capture filter that follows the Cisco IOS standards (http://www.cisco.com/c/en/us/support/docs/ip/access-lists/26448-ACLsamples.html). Multiple filters can be specified using a comma between them. BEWARE: when using a filter, the default behavior is to drop all the packets except the ones that fall into the filter.
|
||||
The remote filter on the router. This is a capture filter that follows the Cisco
|
||||
IOS standards
|
||||
(https://www.cisco.com/c/en/us/support/docs/ip/access-lists/26448-ACLsamples.html).
|
||||
Multiple filters can be specified using a comma between them. BEWARE: when using
|
||||
a filter, the default behavior is to drop all the packets except the ones that
|
||||
fall into the filter.
|
||||
|
||||
Examples:
|
||||
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@ B<encap>:I<name> Packet data should be dissected using the
|
|||
libpcap/Npcap/WinPcap data link type (DLT) I<name>, e.g. B<encap:EN10MB> for
|
||||
Ethernet. Names are converted using pcap_datalink_name_to_val().
|
||||
A complete list of DLTs can be found at
|
||||
L<http://www.tcpdump.org/linktypes.html>.
|
||||
L<https://www.tcpdump.org/linktypes.html>.
|
||||
|
||||
B<encap>:I<number> Packet data should be dissected using the
|
||||
libpcap/Npcap/WinPcap LINKTYPE_ I<number>, e.g. B<encap:105> for raw IEEE
|
||||
|
|
|
|||
|
|
@ -146,13 +146,13 @@ of an IP packet (i.e. has complete L4 information) but does not have
|
|||
an IP header with each packet. Note that an appropriate Ethernet header
|
||||
is automatically included with each packet as well.
|
||||
Example: I<-i 46> to specify an RSVP packet (IP protocol 46). See
|
||||
L<http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml> for
|
||||
L<https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml> for
|
||||
the complete list of assigned internet protocol numbers.
|
||||
|
||||
=item -l
|
||||
|
||||
Specify the link-layer header type of this packet. Default is Ethernet
|
||||
(1). See L<http://www.tcpdump.org/linktypes.html> for the complete list
|
||||
(1). See L<https://www.tcpdump.org/linktypes.html> for the complete list
|
||||
of possible encapsulations. Note that this option should be used if
|
||||
your dump is a complete hex dump of an encapsulated packet and you wish
|
||||
to specify the exact type of encapsulation. Example: I<-l 7> for ARCNet
|
||||
|
|
|
|||
|
|
@ -567,7 +567,7 @@ Read a list of entries from a "hosts" file, which will then be written
|
|||
to a capture file. Implies B<-W n>. Can be called multiple times.
|
||||
|
||||
The "hosts" file format is documented at
|
||||
L<http://en.wikipedia.org/wiki/Hosts_(file)>.
|
||||
L<https://en.wikipedia.org/wiki/Hosts_(file)>.
|
||||
|
||||
=item -i E<lt>capture interfaceE<gt> | -
|
||||
|
||||
|
|
|
|||
|
|
@ -12,8 +12,8 @@ all_guides` or `msbuild all_guides.vcxproj`. Requirements are listed
|
|||
below.
|
||||
|
||||
The guides and release notes are written in
|
||||
http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/[Asciidoctor syntax].
|
||||
For more information see http://asciidoctor.org.
|
||||
https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/[Asciidoctor syntax].
|
||||
For more information see https://asciidoctor.org.
|
||||
|
||||
Conversions from Asciidoctor markup to each of our supported output
|
||||
formats is done via the following steps:
|
||||
|
|
@ -34,7 +34,7 @@ on installing required packages for your platform.
|
|||
== AsciidoctorJ (recommended) or Asciidoctor
|
||||
|
||||
Text markup format and publishing toolchain:
|
||||
http://asciidoctor.org/
|
||||
https://asciidoctor.org/
|
||||
|
||||
AsciidoctorJ is a self-contained bundle which includes Asciidoctor and
|
||||
JRuby. It can be installed via Chocolatey on Windows, Homebrew on macOS,
|
||||
|
|
@ -60,16 +60,16 @@ most Linux distributions.
|
|||
== HTML Help Workshop (Windows only)
|
||||
|
||||
The HTML Help compiler is part of the
|
||||
http://www.microsoft.com/en-us/download/details.aspx?id=21138[HTML Help Workshop]
|
||||
https://www.microsoft.com/en-us/download/details.aspx?id=21138[HTML Help Workshop]
|
||||
from Microsoft. It is used to generate the documentation shipped with
|
||||
the Windows installers.
|
||||
|
||||
= Asciidoctor Markup
|
||||
|
||||
The User’s and Developer’s Guides were originally written in DocBook and
|
||||
were later converted to http://asciidoc.org/[AsciiDoc]. We subsequently
|
||||
were later converted to https://asciidoc.org/[AsciiDoc]. We subsequently
|
||||
switched from AsciiDoc to Asciidoctor. As a result we currently use
|
||||
http://asciidoctor.org/docs/migration/[compat mode], but may switch
|
||||
https://asciidoctor.org/docs/migration/[compat mode], but may switch
|
||||
to Asciidoctor’s modern markup at a later date.
|
||||
|
||||
Please use the following conventions when writing documentation:
|
||||
|
|
@ -149,7 +149,7 @@ works in Firefox & Chrome, but not in Safari, Preview, or Internet Explorer.
|
|||
|
||||
== Qt Help
|
||||
|
||||
Qt provides an extensive http://doc.qt.io/qt-5/qthelp-framework.html[help system].
|
||||
Qt provides an extensive https://doc.qt.io/qt-5/qthelp-framework.html[help system].
|
||||
However, to use it we need to generate a Qt Help Project (.qhp) file,
|
||||
which isn't currently supported by Asciidoctor or via DocBook XSL.
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@
|
|||
:wireshark-users-guide-url: {wireshark-docs-url}wsug_html_chunked/
|
||||
|
||||
// External URLs
|
||||
:tcpdump-main-url: http://www.tcpdump.org/
|
||||
:tcpdump-main-url: https://www.tcpdump.org/
|
||||
:pcap-filter-man-page-url: {tcpdump-main-url}manpages/pcap-filter.7.html
|
||||
:tcpdump-man-page-url: {tcpdump-main-url}manpages/tcpdump.1.html
|
||||
|
||||
|
|
@ -53,8 +53,8 @@
|
|||
:wikipedia-main-url: https://en.wikipedia.org/wiki/
|
||||
:pcre2pattern-url: https://www.pcre.org/current/doc/html/pcre2pattern.html
|
||||
|
||||
:greenwichmeantime-main-url: http://wwp.greenwichmeantime.com/
|
||||
:timeanddate-main-url: http://www.timeanddate.com/worldclock/
|
||||
:greenwichmeantime-main-url: https://wwp.greenwichmeantime.com/
|
||||
:timeanddate-main-url: https://www.timeanddate.com/worldclock/
|
||||
:ntp-main-url: http://www.ntp.org/
|
||||
|
||||
:gplv2-url: https://www.gnu.org/licenses/gpl-2.0.html
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ The following table shows the typographic conventions that are used in this guid
|
|||
// `backticks` for monospaces.
|
||||
// Asciidoctor’s modern mode is more strict, and only allows _underline_
|
||||
// italics and `backtick` monospaces.
|
||||
// http://asciidoctor.org/docs/migration/
|
||||
// https://asciidoctor.org/docs/migration/
|
||||
|
||||
.Typographic Conventions
|
||||
[options="header",cols="1,3,3"]
|
||||
|
|
|
|||
|
|
@ -49,9 +49,9 @@ gone offline.
|
|||
|
||||
More information on the name change can be found here:
|
||||
|
||||
* http://www.prweb.com/releases/2006/6/prweb396098.htm[Original press
|
||||
* https://www.prweb.com/releases/2006/6/prweb396098.htm[Original press
|
||||
release]
|
||||
* http://archive09.linux.com/articles/54968[NewsForge article]
|
||||
* https://www.linux.com/news/ethereal-changes-name-wireshark[NewsForge article]
|
||||
* Many other articles in https://www.wireshark.org/bibliography.html[our
|
||||
bibliography]
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ An IRC channel dedicated to Wireshark can be found at
|
|||
irc://irc.freenode.net/wireshark[irc://irc.freenode.net/wireshark].
|
||||
|
||||
Self-paced and instructor-led training is available at
|
||||
http://www.wiresharktraining.com[Wireshark University]. Wireshark
|
||||
https://www.wiresharktraining.com[Wireshark University]. Wireshark
|
||||
University also offers certification via the Wireshark Certified Network
|
||||
Analyst program.
|
||||
|
||||
|
|
@ -470,8 +470,8 @@ although the device doesn't necessarily have to be running as an IP
|
|||
interface in order to support traffic capture.
|
||||
|
||||
On Linux and FreeBSD, libpcap 0.8 and later support the API for
|
||||
http://www.endace.com/products.htm[Endace Measurement Systems' DAG
|
||||
cards], so that a system with one of those cards, and its driver and
|
||||
Endace Measurement Systems' DAG
|
||||
cards, so that a system with one of those cards, and its driver and
|
||||
libraries, installed can capture traffic with those cards with
|
||||
libpcap-based applications. You would either have to have a version of
|
||||
Wireshark built with that version of libpcap, or a dynamically-linked
|
||||
|
|
|
|||
|
|
@ -3,9 +3,9 @@ include::attributes.adoc[]
|
|||
:linkcss:
|
||||
|
||||
= Wireshark {wireshark-version} Release Notes
|
||||
// AsciiDoc quick reference: http://powerman.name/doc/asciidoc
|
||||
// AsciiDoc quick reference: https://powerman.name/doc/asciidoc
|
||||
// Asciidoctor Syntax Quick Reference:
|
||||
// http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
|
||||
// https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
|
||||
|
||||
This is an experimental release intended to test new features for
|
||||
Wireshark 3.2.
|
||||
|
|
@ -125,7 +125,7 @@ Bugs and feature requests can be reported on
|
|||
https://bugs.wireshark.org/[the bug tracker].
|
||||
|
||||
Official Wireshark training and certification are available from
|
||||
http://www.wiresharktraining.com/[Wireshark University].
|
||||
https://www.wiresharktraining.com/[Wireshark University].
|
||||
|
||||
== Frequently Asked Questions
|
||||
|
||||
|
|
|
|||
|
|
@ -127,14 +127,15 @@ and its dependencies.
|
|||
|
||||
The GLib library is available for most Linux distributions and UNIX
|
||||
flavors. If it isn't already installed and isn't available as a package
|
||||
for your platform, you can get it at http://www.gtk.org[].
|
||||
for your platform, you can get it at https://wiki.gnome.org/Projects/GLib[].
|
||||
|
||||
[[ChLibsWin32GLib]]
|
||||
|
||||
[discrete]
|
||||
==== Windows
|
||||
|
||||
You can get the latest version at http://www.gtk.org[].
|
||||
Part of our vcpkg-export bundle at
|
||||
https://anonsvn.wireshark.org/wireshark-win32-libs/trunk/packages/[].
|
||||
|
||||
[[ChLibsSMI]]
|
||||
|
||||
|
|
@ -149,7 +150,7 @@ LibSMI is used for MIB and PIB parsing and for OID resolution.
|
|||
|
||||
If this library isn't already installed or available as a
|
||||
package for your platform, you can get it at
|
||||
http://www.ibr.cs.tu-bs.de/projects/libsmi/[].
|
||||
https://www.ibr.cs.tu-bs.de/projects/libsmi/[].
|
||||
|
||||
[[ChLibsWin32SMI]]
|
||||
|
||||
|
|
@ -157,7 +158,7 @@ http://www.ibr.cs.tu-bs.de/projects/libsmi/[].
|
|||
==== Windows
|
||||
|
||||
Wireshark uses the source libSMI distribution at
|
||||
http://www.ibr.cs.tu-bs.de/projects/libsmi/[].
|
||||
https://www.ibr.cs.tu-bs.de/projects/libsmi/[].
|
||||
LibSMI is cross-compiled using MinGW32. It’s stored in the libsmi zip archive at
|
||||
https://anonsvn.wireshark.org/wireshark-win32-libs/trunk/packages/[].
|
||||
|
||||
|
|
@ -174,7 +175,7 @@ resolution library in Wireshark.
|
|||
==== Unix
|
||||
|
||||
If this library isn't already installed or available as a package for your
|
||||
platform, you can get it at http://c-ares.haxx.se/[].
|
||||
platform, you can get it at https://c-ares.haxx.se/[].
|
||||
|
||||
[[ChLibsWin32Cares]]
|
||||
|
||||
|
|
@ -188,10 +189,10 @@ https://anonsvn.wireshark.org/wireshark-win32-libs/trunk/packages/[].
|
|||
|
||||
=== zlib (Optional)
|
||||
|
||||
[quote, The zlib web site, http://www.zlib.net/]
|
||||
[quote, The zlib web site, https://www.zlib.net/]
|
||||
____
|
||||
zlib is designed to be a
|
||||
http://www.gzip.org/zlib/zlib_license.html[free],
|
||||
https://www.gzip.org/zlib/zlib_license.html[free],
|
||||
general-purpose, legally unencumbered -- that is, not covered by any
|
||||
patents -- lossless data-compression library for use on virtually any computer
|
||||
hardware and operating system.
|
||||
|
|
@ -204,7 +205,7 @@ ____
|
|||
|
||||
This library is almost certain to be installed on your system. If it isn't or
|
||||
you don't want to use the default library you can download it from
|
||||
http://www.zlib.net/[].
|
||||
https://www.zlib.net/[].
|
||||
|
||||
[[ChLibsWin32Zlib]]
|
||||
|
||||
|
|
@ -317,7 +318,7 @@ secureLDAP protocols.
|
|||
|
||||
If this library isn't already installed or available as a
|
||||
package for your platform, you can get it at
|
||||
http://web.mit.edu/Kerberos/dist/[].
|
||||
https://web.mit.edu/Kerberos/dist/[].
|
||||
|
||||
[[ChLibsWin32Kerberos]]
|
||||
|
||||
|
|
@ -340,7 +341,7 @@ The LUA library is used to add scripting support to Wireshark.
|
|||
|
||||
If this library isn't already installed or available as a
|
||||
package for your platform, you can get it at
|
||||
http://www.lua.org/download.html[].
|
||||
https://www.lua.org/download.html[].
|
||||
|
||||
[[ChLibsWin32Lua]]
|
||||
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@ Chocolatey installs Python in _C:\Python37_ by default.
|
|||
==== Install Perl
|
||||
|
||||
Get a Perl installer from http://strawberryperl.com/
|
||||
http://www.ActiveState.com/ and install Perl into the default location.
|
||||
https://www.activestate.com/ and install Perl into the default location.
|
||||
|
||||
Alternatively you can install Perl using Chocolatey:
|
||||
|
||||
|
|
@ -234,7 +234,7 @@ Chocolatey ensures cmake.exe is on your path.
|
|||
|
||||
==== Install Asciidoctor, Xsltproc, And DocBook
|
||||
|
||||
http://asciidoctor.org/[Asciidoctor] can be run directly as a Ruby
|
||||
https://asciidoctor.org/[Asciidoctor] can be run directly as a Ruby
|
||||
script or via a Java wrapper (AsciidoctorJ). It is used in conjunction
|
||||
with Xsltproc and DocBook to generate the documenation you're reading
|
||||
and the User’s Guide.
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ such as where to find specific functionality. This is done in
|
|||
|
||||
=== The Wireshark Git repository
|
||||
|
||||
http://git-scm.com/[Git] is used to keep track of the changes made to the
|
||||
https://git-scm.com/[Git] is used to keep track of the changes made to the
|
||||
Wireshark source code. The code is stored inside Wireshark project’s Git
|
||||
repository located at a server at the wireshark.org domain.
|
||||
|
||||
|
|
@ -50,8 +50,8 @@ command line and is integrated with many popular tools.
|
|||
.Git is our *third* revision control system
|
||||
[NOTE]
|
||||
====
|
||||
Wireshark originally used http://www.nongnu.org/cvs/[Concurrent Versions System]
|
||||
(CVS) and migrated to http://subversion.apache.org/[Subversion] in July 2004.
|
||||
Wireshark originally used https://www.nongnu.org/cvs/[Concurrent Versions System]
|
||||
(CVS) and migrated to https://subversion.apache.org/[Subversion] in July 2004.
|
||||
The Subversion repository was subsequently migrated to Git in January 2014.
|
||||
====
|
||||
|
||||
|
|
@ -80,7 +80,7 @@ https://code.wireshark.org/review/gitweb?p=wireshark.git
|
|||
==== Git Naming Conventions
|
||||
|
||||
Like most revision control systems, Git uses
|
||||
http://en.wikipedia.org/wiki/Branching_%28revision_control%29[branching] to
|
||||
https://en.wikipedia.org/wiki/Branching_%28revision_control%29[branching] to
|
||||
manage different copies of the source code and allow parallel development.
|
||||
Wireshark uses the following branch naming conventions:
|
||||
|
||||
|
|
@ -571,7 +571,7 @@ as described at <<ChSrcGit>>.
|
|||
|
||||
// ==== What is a diff file (a patch)?
|
||||
//
|
||||
// A http://en.wikipedia.org/wiki/Diff[diff file]is a plain text file containing the differences between a pair of files
|
||||
// A https://en.wikipedia.org/wiki/Diff[diff file]is a plain text file containing the differences between a pair of files
|
||||
// (or a multiple of such file pairs).
|
||||
//
|
||||
// .A diff file is often also called a patch.
|
||||
|
|
@ -1207,7 +1207,7 @@ If you have a question not addressed here, please contact
|
|||
|
||||
The Debian Package is built using dpkg-buildpackage, based on information
|
||||
found in the source tree under _debian_. See
|
||||
http://www.debian-administration.org/articles/336 for a
|
||||
https://www.debian.org/doc/manuals/maint-guide/build.en.html for a
|
||||
more in-depth discussion of the build process.
|
||||
|
||||
|
||||
|
|
@ -1215,7 +1215,7 @@ In the wireshark directory, type:
|
|||
|
||||
[source,sh]
|
||||
----
|
||||
$ dpkg-buildpackage -rfakeroot -us -uc
|
||||
$ dpkg-buildpackage -b -us -uc -jauto
|
||||
----
|
||||
|
||||
to build the Debian Package.
|
||||
|
|
@ -1228,7 +1228,7 @@ You can build an RPM package using the `rpm-package` target. The package
|
|||
version is derived from the current git HEAD, so you must build from a
|
||||
git checkout.
|
||||
|
||||
The package is built using http://www.rpm.org/[rpmbuild], which comes as
|
||||
The package is built using https://rpm.org/[rpmbuild], which comes as
|
||||
standard on many flavours of Linux, including Red Hat, Fedora, and
|
||||
openSUSE. The process creates a clean build environment in
|
||||
_$\{CMAKE_BINARY_DIR}/packaging/rpm/BUILD_ each time the RPM is built.
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ available in different "flavours":
|
|||
on the supported UNIX and UNIX-like platforms. Cygwin is unsupported.
|
||||
* Windows native: Some tools are available as native Windows tools, no
|
||||
special emulation is required. Many of these tools can be installed
|
||||
(and updated) using http://chocolatey.org[Chocolatey], a Windows
|
||||
(and updated) using https://chocolatey.org[Chocolatey], a Windows
|
||||
package manager similar to the Linux package managers apt-get or yum.
|
||||
|
||||
[WARNING]
|
||||
|
|
@ -48,7 +48,7 @@ development tasks in <<ChapterSources>>.
|
|||
|
||||
Chocolatey is a Windows package manager that can be used to install (and update)
|
||||
many of the packages required for Wireshark development. Chocolatey can be
|
||||
obtained from the http://chocolatey.org[website] or from a Command Prompt:
|
||||
obtained from the https://chocolatey.org[website] or from a Command Prompt:
|
||||
|
||||
[source,cmd]
|
||||
----
|
||||
|
|
@ -135,20 +135,11 @@ The home page of the CMake project: https://cmake.org/
|
|||
|
||||
Official documentation: https://cmake.org/documentation/
|
||||
|
||||
About CMake in general and why KDE4 uses it: http://lwn.net/Articles/188693/
|
||||
About CMake in general and why KDE4 uses it: https://lwn.net/Articles/188693/
|
||||
|
||||
Introductory tutorial/presentation:
|
||||
http://ait.web.psi.ch/services/linux/hpc/hpc_user_cookbook/tools/cmake/docs/Cmake_VM_2007.pdf
|
||||
Useful variables: https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/Useful-Variables
|
||||
|
||||
Introductory article in the Linux Journal:
|
||||
http://www.linuxjournal.com/node/6700/print
|
||||
|
||||
Useful variables: http://www.cmake.org/Wiki/CMake_Useful_Variables
|
||||
|
||||
Frequently Asked Questions: http://www.cmake.org/Wiki/CMake_FAQ
|
||||
|
||||
// 2017-08-04 dead
|
||||
//Additional cmake modules: http://code.google.com/p/cmake-modules/
|
||||
Frequently Asked Questions: https://gitlab.kitware.com/cmake/community/wikis/FAQ
|
||||
|
||||
[[ChToolsGNUChain]]
|
||||
|
||||
|
|
@ -163,7 +154,7 @@ systems.
|
|||
|
||||
If GCC isn't already installed or available
|
||||
as a package for your platform, you can get it at:
|
||||
http://gcc.gnu.org/[].
|
||||
https://gcc.gnu.org/[].
|
||||
|
||||
After correct installation, typing at the
|
||||
bash command line prompt:
|
||||
|
|
@ -197,7 +188,7 @@ available], including Qt Creator, CLion, and Eclipse.
|
|||
|
||||
If gdb isn't already installed or available
|
||||
as a package for your platform, you can get it at:
|
||||
http://www.gnu.org/software/gdb/gdb.html[].
|
||||
https://www.gnu.org/software/gdb/gdb.html[].
|
||||
|
||||
After correct installation:
|
||||
|
||||
|
|
@ -209,20 +200,11 @@ $ gdb --version
|
|||
should result in something like:
|
||||
|
||||
----
|
||||
GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs
|
||||
Copyright (C) 2014 Free Software Foundation, Inc.
|
||||
GNU gdb (GDB) 8.3
|
||||
Copyright (C) 2019 Free Software Foundation, Inc.
|
||||
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
|
||||
This is free software: you are free to change and redistribute it.
|
||||
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
|
||||
and "show warranty" for details.
|
||||
This GDB was configured as "x86_64-linux-gnu".
|
||||
Type "show configuration" for configuration details.
|
||||
For bug reporting instructions, please see:
|
||||
<http://www.gnu.org/software/gdb/bugs/>.
|
||||
Find the GDB manual and other documentation resources online at:
|
||||
<http://www.gnu.org/software/gdb/documentation/>.
|
||||
For help, type "help".
|
||||
Type "apropos word" to search for commands related to "word".
|
||||
There is NO WARRANTY, to the extent permitted by law.
|
||||
----
|
||||
|
||||
Your version string may vary, of course.
|
||||
|
|
@ -239,7 +221,7 @@ platforms.
|
|||
|
||||
If GNU Make isn't already installed or
|
||||
available as a package for your platform, you can get it at:
|
||||
http://www.gnu.org/software/make/[].
|
||||
https://www.gnu.org/software/make/[].
|
||||
|
||||
After correct installation:
|
||||
|
||||
|
|
@ -615,7 +597,7 @@ The bash shell is needed to run several shell scripts.
|
|||
Bash (the GNU Bourne-Again SHell) is available for most UNIX and
|
||||
UNIX-like platforms. If it isn't already installed or available as a
|
||||
package for your platform, you can get it at
|
||||
http://www.gnu.org/software/bash/bash.html[].
|
||||
https://www.gnu.org/software/bash/bash.html[].
|
||||
|
||||
After correct installation, typing at the bash command line prompt:
|
||||
|
||||
|
|
@ -686,7 +668,7 @@ Your version string may vary of course.
|
|||
|
||||
Perl is an interpreted programming language. The
|
||||
homepage of the Perl project is
|
||||
http://www.perl.com[]. Perl is used to convert
|
||||
https://www.perl.org[]. Perl is used to convert
|
||||
various text files into usable source code. Perl version 5.6
|
||||
and above should work fine.
|
||||
|
||||
|
|
@ -697,7 +679,7 @@ and above should work fine.
|
|||
|
||||
Perl is available for most UNIX and UNIX-like platforms. If perl isn't
|
||||
already installed or available as a package for your platform, you can
|
||||
get it at http://www.perl.com/[].
|
||||
get it at https://www.perl.org/[].
|
||||
|
||||
After correct installation, typing at the
|
||||
bash command line prompt:
|
||||
|
|
@ -732,7 +714,7 @@ However, the version string may vary.
|
|||
|
||||
A native Windows Perl package can be obtained from
|
||||
http://strawberryperl.com/[Strawberry Perl] or
|
||||
http://www.ActiveState.com[Active State]. The installation should be
|
||||
https://www.activestate.com[Active State]. The installation should be
|
||||
straightforward.
|
||||
|
||||
You may also use Chocolatey to install either package:
|
||||
|
|
@ -787,7 +769,7 @@ Bison is available for most UNIX and UNIX-like platforms. See the next
|
|||
section for native Windows options.
|
||||
|
||||
If GNU Bison isn't already installed or available as a package for your
|
||||
platform you can get it at: http://www.gnu.org/software/bison/bison.html[].
|
||||
platform you can get it at: https://www.gnu.org/software/bison/bison.html[].
|
||||
|
||||
After correct installation running the following
|
||||
|
||||
|
|
@ -838,7 +820,7 @@ Flex is available for most UNIX and UNIX-like platforms. See the next
|
|||
section for native Windows options.
|
||||
|
||||
If GNU flex isn't already installed or available as a package for your platform
|
||||
you can get it at http://www.gnu.org/software/flex/[].
|
||||
you can get it at https://www.gnu.org/software/flex/[].
|
||||
|
||||
After correct installation running the following
|
||||
|
||||
|
|
@ -896,7 +878,7 @@ client.
|
|||
|
||||
Git is available for most UNIX and UNIX-like platforms. If Git isn't
|
||||
already installed or available as a package for your platform, you can
|
||||
get it at: http://git-scm.com/[].
|
||||
get it at: https://git-scm.com/[].
|
||||
|
||||
After correct installation, typing at the bash command line prompt:
|
||||
|
||||
|
|
@ -919,7 +901,7 @@ Your version will likely be different.
|
|||
==== Windows
|
||||
|
||||
The Git command line tools for Windows can be found at
|
||||
http://git-scm.com/download/win[] and can also be installed using Chocolatey:
|
||||
https://git-scm.com/download/win[] and can also be installed using Chocolatey:
|
||||
|
||||
[source,cmd]
|
||||
----
|
||||
|
|
@ -961,7 +943,7 @@ PS:\>choco install poshgit
|
|||
|
||||
Along with the traditional command-line client, several
|
||||
GUI clients are available for a number of platforms. See
|
||||
http://git-scm.com/downloads/guis[] for details.
|
||||
https://git-scm.com/downloads/guis[] for details.
|
||||
|
||||
// [[ChToolsUnixGitGUI]]
|
||||
// XXX Add Gui client section
|
||||
|
|
@ -988,7 +970,7 @@ tool.
|
|||
|
||||
Patch is available for most UNIX and UNIX-like platforms. If GNU patch
|
||||
isn't already installed or available as a package for your platform, you
|
||||
can get it at http://www.gnu.org/software/patch/patch.html[].
|
||||
can get it at https://www.gnu.org/software/patch/patch.html[].
|
||||
|
||||
After correct installation, typing at the
|
||||
bash command line prompt:
|
||||
|
|
@ -1049,7 +1031,7 @@ You can find more instructions on using NSIS in <<ChSrcNSIS>>.
|
|||
=== Windows: WiX Toolset (Optional)
|
||||
|
||||
The Wix Toolset can be used to generate Windows Installer (_.msi_)
|
||||
packages. You can download it from the link:http://wixtoolset.org/[WiX
|
||||
packages. You can download it from the link:https://wixtoolset.org/[WiX
|
||||
web site] or install it using Chocolatey:
|
||||
|
||||
[source,cmd]
|
||||
|
|
@ -1071,7 +1053,7 @@ files.
|
|||
To install it, do the following:
|
||||
|
||||
* Download the latest PortableApps.com Platform release from
|
||||
http://portableapps.com/[].
|
||||
https://portableapps.com/[].
|
||||
|
||||
* Install the following applications in the PortableApps.com environment:
|
||||
|
||||
|
|
|
|||
|
|
@ -170,9 +170,9 @@ your code.
|
|||
|
||||
Sometimes we have to call {cpp} functions from one of
|
||||
Wireshark’s C callbacks and pass {cpp} objects to or from C. Tap
|
||||
listeners are a common example. The {cpp} FAQ link:http://www.
|
||||
parashift.com/c++-faq/mixing-c-and-cpp.html:[describes how to do this
|
||||
safely].
|
||||
listeners are a common example. The {cpp} FAQ
|
||||
https://www.parashift.com/c++-faq/mixing-c-and-cpp.html[describes how to do
|
||||
this safely].
|
||||
|
||||
Tapping usually involves declaring static methods for callbacks, passing `this`
|
||||
as the tap data.
|
||||
|
|
@ -210,7 +210,7 @@ directory in the Wireshark user configuration directory
|
|||
UNIX).
|
||||
|
||||
For more information about Qt Linguist see
|
||||
http://qt-project.org/doc/qt-4.8/linguist-manual.html[its manual].
|
||||
https://doc.qt.io/qt-5/qtlinguist-index.html[its manual].
|
||||
|
||||
You can also manage translations online with
|
||||
https://www.transifex.com/projects/p/wireshark/[Transifex].
|
||||
|
|
@ -225,7 +225,7 @@ code through the following steps:
|
|||
|
||||
===== Colors And Themes
|
||||
|
||||
Qt provides a number of colors via the http://doc.qt.io/qt-5/qpalette.html[QPalette]
|
||||
Qt provides a number of colors via the https://doc.qt.io/qt-5/qpalette.html[QPalette]
|
||||
class. Use this class when you need a standard color provided by the
|
||||
underlying operating system.
|
||||
|
||||
|
|
@ -255,7 +255,7 @@ around this by using `ColorUtils::themeLinkBrush()` and
|
|||
The main window has many QActions which are shared with child widgets. See
|
||||
_ui/qt/proto_tree.cpp_ for an example of this.
|
||||
|
||||
http://www.kdab.com/kdab-products/gammaray/[GammaRay] lets you inspect
|
||||
https://www.kdab.com/development-resources/qt-tools/gammaray/[GammaRay] lets you inspect
|
||||
the internals of a running Qt application similar to $$Spy++$$ on Windows.
|
||||
|
||||
[[ChUIGUIDocs]]
|
||||
|
|
|
|||
|
|
@ -288,11 +288,11 @@ Lrexlib PCRE implementation, with a few differences as follows:
|
|||
Since: 1.11.3
|
||||
|
||||
This page is based on the full documentation for Lrexlib at
|
||||
link:http://rrthomas.github.io/lrexlib/manual.html[http://rrthomas.github.io/lrexlib/manual.html]
|
||||
https://rrthomas.github.io/lrexlib/manual.html[]
|
||||
|
||||
The GLib Regular expression syntax (which is essentially PCRE syntax) can be
|
||||
found at
|
||||
link:https://developer.gnome.org/glib/2.38/glib-regex-syntax.html[https://developer.gnome.org/glib/2.38/glib-regex-syntax.html]
|
||||
https://developer.gnome.org/glib/2.38/glib-regex-syntax.html[]
|
||||
|
||||
[[lua_class_GRegex]]
|
||||
|
||||
|
|
@ -546,7 +546,7 @@ GRegex object previously compiled with GRegex.new().
|
|||
Since: 1.11.3
|
||||
|
||||
For details see:
|
||||
link:http://rrthomas.github.io/lrexlib/manual.html#gsub[http://rrthomas.github.io/lrexlib/manual.html#gsub]
|
||||
https://rrthomas.github.io/lrexlib/manual.html#gsub[]
|
||||
|
||||
[float]
|
||||
===== Arguments
|
||||
|
|
|
|||
|
|
@ -851,7 +851,7 @@ The replacement text for the macro it uses $1, $2, $3, ... as the input argument
|
|||
|
||||
=== ESS Category Attributes
|
||||
|
||||
Wireshark uses this table to map ESS Security Category attributes to textual representations. The values to put in this table are usually found in a link:$$http://www.xmlspif.org/$$[XML SPIF], which is used for defining security labels.
|
||||
Wireshark uses this table to map ESS Security Category attributes to textual representations. The values to put in this table are usually found in a http://www.xmlspif.org/[XML SPIF], which is used for defining security labels.
|
||||
|
||||
This table is a user table, as described in <<ChUserTable>>, with the
|
||||
following fields:
|
||||
|
|
@ -870,12 +870,12 @@ The textual representation for the value.
|
|||
=== MaxMind Database Paths
|
||||
|
||||
If your copy of Wireshark supports
|
||||
link:http://www.maxmind.com/[MaxMind’s] MaxMindDB library, you can use
|
||||
https://www.maxmind.com/[MaxMind’s] MaxMindDB library, you can use
|
||||
their databases to match IP addresses to countries, cites, autonomous
|
||||
system numbers, and other bits of information. Some databases are
|
||||
link:https://dev.maxmind.com/geoip/geoip2/downloadable/[available at no
|
||||
https://dev.maxmind.com/geoip/geoip2/downloadable/[available at no
|
||||
cost], while others require a licensing fee. See
|
||||
link:http://www.maxmind.com/[the MaxMind web site] for more information.
|
||||
https://www.maxmind.com/[the MaxMind web site] for more information.
|
||||
|
||||
The configuration for the MaxMind database is a user table, as described
|
||||
in <<ChUserTable>>, with the following fields:
|
||||
|
|
|
|||
|
|
@ -713,7 +713,7 @@ Export packet bytes into C arrays so you can import the stream data into your ow
|
|||
|
||||
Export packet data into PSML. This is an XML based format including only the
|
||||
packet summary. The PSML file specification is available at:
|
||||
link:http://www.nbee.org/doku.php?id=netpdl:psml_specification[].
|
||||
https://web.archive.org/web/20141115200425/http://www.nbee.org/doku.php?id=netpdl:psml_specification[].
|
||||
|
||||
.The “Export as PSML File” dialog box
|
||||
image::wsug_graphics/ws-export-psml.png[{screenshot-attrs}]
|
||||
|
|
@ -731,7 +731,7 @@ format is defined by the PSML specification.
|
|||
|
||||
Export packet data into PDML. This is an XML based format including the packet
|
||||
details. The PDML file specification is available at:
|
||||
link:http://www.nbee.org/doku.php?id=netpdl:pdml_specification[].
|
||||
https://web.archive.org/web/20140416072301/http://www.nbee.org/doku.php?id=netpdl:pdml_specification[].
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
|
|
|||
|
|
@ -67,9 +67,7 @@ There are some ways to circumvent this.
|
|||
|
||||
Many vendor’s switches support a feature known as “port spanning” or “port
|
||||
mirroring” in which all of the traffic to and from port A are also sent out
|
||||
port B. An excellent reference on the “port spanning” feature of Cisco
|
||||
switches can be found at
|
||||
link:$$http://www.cisco.com/warp/public/473/41.html$$[Configuring the Catalyst Switched Port Analyzer (SPAN) Feature]
|
||||
port B.
|
||||
|
||||
=== Examples of troubleshooting
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ Input:
|
|||
|
||||
Output:
|
||||
-l <typenum> link-layer type number; default is 1 (Ethernet). See
|
||||
http://www.tcpdump.org/linktypes.html for a list of
|
||||
https://www.tcpdump.org/linktypes.html for a list of
|
||||
numbers. Use this option if your dump is a complete
|
||||
hex dump of an encapsulated packet and you wish to
|
||||
specify the exact type of encapsulation.
|
||||
|
|
|
|||
Loading…
Reference in New Issue