Ignore:
Timestamp:
05/30/2005 09:28:37 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.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
Children:
5e9a7236
Parents:
17e6d48
Message:

Removed excess spaces from the ends of lines in the source files

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • basicnet/netutils/traceroute.xml

    r17e6d48 r1065a91  
    3030    <title>Introduction to Traceroute</title>
    3131
    32     <para>The <application>Traceroute</application> package contains a program 
    33     which is used to display the network route that packets take to reach a 
    34     specified host. This is a standard network troubleshooting tool. If you find 
    35     yourself unable to connect to another system, traceroute can help pinpoint 
     32    <para>The <application>Traceroute</application> package contains a program
     33    which is used to display the network route that packets take to reach a
     34    specified host. This is a standard network troubleshooting tool. If you find
     35    yourself unable to connect to another system, traceroute can help pinpoint
    3636    the problem.</para>
    3737
     
    6363    <title>Installation of Traceroute</title>
    6464
    65     <para>Install <application>Traceroute</application> by running the following 
     65    <para>Install <application>Traceroute</application> by running the following
    6666    commands:</para>
    6767
     
    8080    <title>Command Explanations</title>
    8181
    82     <para><command>sed 's/-o bin/-o root/' Makefile.in</command>: 
    83     Adjusts the <filename>Makefile</filename> so that the program is installed 
    84     with user root instead of user bin (which doesn't exist on a default 
     82    <para><command>sed 's/-o bin/-o root/' Makefile.in</command>:
     83    Adjusts the <filename>Makefile</filename> so that the program is installed
     84    with user root instead of user bin (which doesn't exist on a default
    8585    LFS system).</para>
    8686
    8787    <para><command>make install</command>: Installs <command>traceroute</command>
    88     with SUID set to <systemitem class="username">root</systemitem> in the 
    89     <filename class='directory'>/usr/sbin</filename> directory. This makes it 
    90     possible for all users to execute <command>traceroute</command>. For absolute 
    91     security, turn off the SUID bit in <command>traceroute</command>'s file permissions 
     88    with SUID set to <systemitem class="username">root</systemitem> in the
     89    <filename class='directory'>/usr/sbin</filename> directory. This makes it
     90    possible for all users to execute <command>traceroute</command>. For absolute
     91    security, turn off the SUID bit in <command>traceroute</command>'s file permissions
    9292    with the command:</para>
    9393
    9494<screen role='root'><userinput>chmod -v 0755 /usr/sbin/traceroute</userinput></screen>
    9595
    96     <para>The risk is that if a security problem such as a buffer overflow was 
    97     ever found in the <application>Traceroute</application> code, a regular user 
     96    <para>The risk is that if a security problem such as a buffer overflow was
     97    ever found in the <application>Traceroute</application> code, a regular user
    9898    on your system could gain <systemitem class="username">root</systemitem>
    99     access if the program is SUID <systemitem class="username">root</systemitem>. 
    100     Of course, removing the SUID permission also makes it impossible for users other 
    101     than <systemitem class="username">root</systemitem> to utilize 
    102     <command>traceroute</command>, so decide what's right for 
     99    access if the program is SUID <systemitem class="username">root</systemitem>.
     100    Of course, removing the SUID permission also makes it impossible for users other
     101    than <systemitem class="username">root</systemitem> to utilize
     102    <command>traceroute</command>, so decide what's right for
    103103    your individual situation.</para>
    104104
    105     <para>The goal of BLFS is to be completely FHS compliant, so if you do leave the 
    106     <command>traceroute</command> binary SUID <systemitem 
    107     class="username">root</systemitem>, then you should move 
     105    <para>The goal of BLFS is to be completely FHS compliant, so if you do leave the
     106    <command>traceroute</command> binary SUID <systemitem
     107    class="username">root</systemitem>, then you should move
    108108    <filename>traceroute</filename> to <filename class='directory'>/usr/bin</filename>
    109109    with the following command:</para>
     
    138138        <term><command>traceroute</command></term>
    139139        <listitem>
    140           <para>does basically what it says: it traces the route your packets 
    141           take from the host you are working on to another host on a network, showing 
     140          <para>does basically what it says: it traces the route your packets
     141          take from the host you are working on to another host on a network, showing
    142142          all the intermediate hops (gateways) along the way.</para>
    143143          <indexterm zone="traceroute traceroute-prog">
Note: See TracChangeset for help on using the changeset viewer.