source: basicnet/netutils/traceroute.xml@ 0aeb696

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts krejzi/svn lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition systemd-11177 systemd-13485 trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 0aeb696 was 0aeb696, checked in by Randy McMurchy <randy@…>, 18 years ago

Added a comment to each file that may need a mention of a test suite added to it, this allows closing of bug #1697

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@5951 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 6.6 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!-- Inserted as a reminder to do this. The mention of a test suite
8 is usually right before the root user installation commands. Please
9 delete these 12 (including one blank) lines after you are done.-->
10
11 <!-- Use one of the two mentions below about a test suite,
12 delete the line that is not applicable. Of course, if the
13 test suite uses syntax other than "make check", revise the
14 line to reflect the actual syntax to run the test suite -->
15
16 <!-- <para>This package does not come with a test suite.</para> -->
17 <!-- <para>To test the results, issue: <command>make check</command>.</para> -->
18
19 <!ENTITY traceroute-download-http "http://gd.tuwien.ac.at/platform/sun/packages/solaris/freeware/SOURCES/traceroute-&traceroute-version;.tar.gz">
20 <!ENTITY traceroute-download-ftp "ftp://ftp.ee.lbl.gov/traceroute-&traceroute-version;.tar.gz">
21 <!ENTITY traceroute-md5sum "964d599ef696efccdeebe7721cd4828d">
22 <!ENTITY traceroute-size "74 KB">
23 <!ENTITY traceroute-buildsize "540 KB">
24 <!ENTITY traceroute-time "0.01 SBU">
25]>
26
27<sect1 id="traceroute" xreflabel="Traceroute-&traceroute-version;">
28 <?dbhtml filename="traceroute.html"?>
29
30 <sect1info>
31 <othername>$LastChangedBy$</othername>
32 <date>$Date$</date>
33 <keywordset>
34 <keyword role="package">traceroute-&traceroute-version;.tar</keyword>
35 <keyword role="ftpdir">traceroute</keyword>
36 </keywordset>
37 </sect1info>
38
39 <title>Traceroute-&traceroute-version;</title>
40
41 <indexterm zone="traceroute">
42 <primary sortas="a-Traceroute">Traceroute</primary>
43 </indexterm>
44
45 <sect2 role="package">
46 <title>Introduction to Traceroute</title>
47
48 <para>The <application>Traceroute</application> package contains a program
49 which is used to display the network route that packets take to reach a
50 specified host. This is a standard network troubleshooting tool. If you find
51 yourself unable to connect to another system, traceroute can help pinpoint
52 the problem.</para>
53
54 <bridgehead renderas="sect3">Package Information</bridgehead>
55 <itemizedlist spacing="compact">
56 <listitem>
57 <para>Download (HTTP): <ulink url="&traceroute-download-http;"/></para>
58 </listitem>
59 <listitem>
60 <para>Download (FTP): <ulink url="&traceroute-download-ftp;"/></para>
61 </listitem>
62 <listitem>
63 <para>Download MD5 sum: &traceroute-md5sum;</para>
64 </listitem>
65 <listitem>
66 <para>Download size: &traceroute-size;</para>
67 </listitem>
68 <listitem>
69 <para>Estimated disk space required: &traceroute-buildsize;</para>
70 </listitem>
71 <listitem>
72 <para>Estimated build time: &traceroute-time;</para>
73 </listitem>
74 </itemizedlist>
75
76 <para condition="html" role="usernotes">User Notes:
77 <ulink url="&blfs-wiki;/traceroute"/></para>
78
79 </sect2>
80
81 <sect2 role="installation">
82 <title>Installation of Traceroute</title>
83
84 <para>Install <application>Traceroute</application> by running the following
85 commands:</para>
86
87<screen><userinput>sed -i -e 's/-o bin/-o root/' Makefile.in &amp;&amp;
88./configure --prefix=/usr &amp;&amp;
89make</userinput></screen>
90
91 <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
92
93<screen role='root'><userinput>make install &amp;&amp;
94make install-man</userinput></screen>
95
96 </sect2>
97
98 <sect2 role="commands">
99 <title>Command Explanations</title>
100
101 <para><command>sed 's/-o bin/-o root/' Makefile.in</command>:
102 Adjusts the <filename>Makefile</filename> so that the program is installed
103 with user <systemitem class='username'>root</systemitem> owning the files
104 instead of user <systemitem class='username'>bin</systemitem>
105 (which doesn't exist on a default LFS system).</para>
106
107 <para><command>make install</command>: Installs <command>traceroute</command>
108 with SUID set to <systemitem class="username">root</systemitem> in the
109 <filename class='directory'>/usr/sbin</filename> directory. This makes it
110 possible for all users to execute <command>traceroute</command>. For absolute
111 security, turn off the SUID bit in <command>traceroute</command>'s file permissions
112 with the command:</para>
113
114<screen role='root'><userinput>chmod -v 0755 /usr/sbin/traceroute</userinput></screen>
115
116 <para>The risk is that if a security problem such as a buffer overflow was
117 ever found in the <application>Traceroute</application> code, a regular user
118 on your system could gain <systemitem class="username">root</systemitem>
119 access if the program is SUID <systemitem class="username">root</systemitem>.
120 Of course, removing the SUID permission also makes it impossible for users other
121 than <systemitem class="username">root</systemitem> to utilize
122 <command>traceroute</command>, so decide what's right for
123 your individual situation.</para>
124
125 <para>The goal of BLFS is to be completely FHS compliant, so if you do leave the
126 <command>traceroute</command> binary SUID <systemitem
127 class="username">root</systemitem>, then you should move
128 <filename>traceroute</filename> to <filename class='directory'>/usr/bin</filename>
129 with the following command:</para>
130
131<screen role='root'><userinput>mv -v /usr/sbin/traceroute /usr/bin</userinput></screen>
132
133 <para>This ensures that the binary is in the path for non-root users.</para>
134
135 </sect2>
136
137 <sect2 role="content">
138 <title>Contents</title>
139
140 <segmentedlist>
141 <segtitle>Installed Program</segtitle>
142 <segtitle>Installed Libraries</segtitle>
143 <segtitle>Installed Directories</segtitle>
144
145 <seglistitem>
146 <seg>traceroute</seg>
147 <seg>None</seg>
148 <seg>None</seg>
149 </seglistitem>
150 </segmentedlist>
151
152 <variablelist>
153 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
154 <?dbfo list-presentation="list"?>
155 <?dbhtml list-presentation="table"?>
156
157 <varlistentry id="traceroute-prog">
158 <term><command>traceroute</command></term>
159 <listitem>
160 <para>does basically what it says: it traces the route your packets
161 take from the host you are working on to another host on a network, showing
162 all the intermediate hops (gateways) along the way.</para>
163 <indexterm zone="traceroute traceroute-prog">
164 <primary sortas="b-traceroute">traceroute</primary>
165 </indexterm>
166 </listitem>
167 </varlistentry>
168
169 </variablelist>
170
171 </sect2>
172
173</sect1>
174
Note: See TracBrowser for help on using the repository browser.