View | Details | Raw Unified | Return to bug 77729
Collapse All | Expand All

(-)firewalls/chapter.sgml (-2 / +2 lines)
Lines 258-264 Link Here
258
	    <entry>PF is part of the base system.
258
	    <entry>PF is part of the base system.
259
	      Do <emphasis>not</emphasis> use the
259
	      Do <emphasis>not</emphasis> use the
260
	      <filename role="package">security/pf</filename> port
260
	      <filename role="package">security/pf</filename> port
261
	      on these versions of &os;.  It won't work.
261
	      on these versions of &os;.  It will not work.
262
	      Use the &man.pf.4; support of the base system instead.</entry>
262
	      Use the &man.pf.4; support of the base system instead.</entry>
263
	  </row>
263
	  </row>
264
	</tbody>
264
	</tbody>
Lines 2587-2593 Link Here
2587
            may be allowed in by the later authorized service rules.
2587
            may be allowed in by the later authorized service rules.
2588
            Second reason is that by having a rule that explicitly
2588
            Second reason is that by having a rule that explicitly
2589
            blocks selected packets that I receive on an infrequent
2589
            blocks selected packets that I receive on an infrequent
2590
            bases and don't want to see in the log, this keeps them from
2590
            bases and do not want to see in the log, this keeps them from
2591
            being caught by the last rule in the section which blocks
2591
            being caught by the last rule in the section which blocks
2592
            and logs all packets which have fallen through the rules.
2592
            and logs all packets which have fallen through the rules.
2593
            The last rule in the section which blocks and logs all
2593
            The last rule in the section which blocks and logs all
(-)ports/chapter.sgml (-1 / +1 lines)
Lines 331-337 Link Here
331
       <replaceable>string</replaceable> is some text to search for.
331
       <replaceable>string</replaceable> is some text to search for.
332
       This searches port names, comments, descriptions and
332
       This searches port names, comments, descriptions and
333
       dependencies and can be used to find ports which relate to a
333
       dependencies and can be used to find ports which relate to a
334
       particular subject if you don't know the name of the program
334
       particular subject if you do not know the name of the program
335
       you are looking for.</para>
335
       you are looking for.</para>
336
336
337
      <para>In both of these cases, the search string is case-insensitive.
337
      <para>In both of these cases, the search string is case-insensitive.
(-)security/chapter.sgml (-5 / +5 lines)
Lines 2425-2431 Link Here
2425
      <para>Now it is time to start up the <acronym>KDC</acronym> services.
2425
      <para>Now it is time to start up the <acronym>KDC</acronym> services.
2426
	Run <command>/etc/rc.d/kerberos start</command> and
2426
	Run <command>/etc/rc.d/kerberos start</command> and
2427
	<command>/etc/rc.d/kadmind start</command> to bring up the
2427
	<command>/etc/rc.d/kadmind start</command> to bring up the
2428
	services.  Note that you won't have any kerberized daemons running
2428
	services.  Note that you will not have any kerberized daemons running
2429
	at this point but you should be able to confirm the that the
2429
	at this point but you should be able to confirm the that the
2430
	<acronym>KDC</acronym> is functioning by obtaining and listing a
2430
	<acronym>KDC</acronym> is functioning by obtaining and listing a
2431
	ticket for the principal (user) that you just created from the
2431
	ticket for the principal (user) that you just created from the
Lines 2697-2703 Link Here
2697
	      and reverse) in <acronym>DNS</acronym> (or
2697
	      and reverse) in <acronym>DNS</acronym> (or
2698
	      <filename>/etc/hosts</filename> as a minimum).  CNAMEs
2698
	      <filename>/etc/hosts</filename> as a minimum).  CNAMEs
2699
	      will work, but the A and PTR records must be correct and in
2699
	      will work, but the A and PTR records must be correct and in
2700
	      place. The error message isn't very intuitive:
2700
	      place. The error message is not very intuitive:
2701
	      <errorname>Kerberos5 refuses authentication because Read req
2701
	      <errorname>Kerberos5 refuses authentication because Read req
2702
	      failed: Key table entry not found</errorname>.</para>
2702
	      failed: Key table entry not found</errorname>.</para>
2703
	  </listitem>
2703
	  </listitem>
Lines 3371-3377 Link Here
3371
        </listitem>
3371
        </listitem>
3372
        <listitem>
3372
        <listitem>
3373
          <para>The internal addresses of the two networks can be
3373
          <para>The internal addresses of the two networks can be
3374
            public or private IP addresses, it doesn't matter.  You can
3374
            public or private IP addresses, it does not matter.  You can
3375
            be running NAT on the gateway machine if necessary.</para>
3375
            be running NAT on the gateway machine if necessary.</para>
3376
        </listitem>
3376
        </listitem>
3377
        <listitem>
3377
        <listitem>
Lines 3733-3739 Link Here
3733
        </listitem>
3733
        </listitem>
3734
        <listitem>
3734
        <listitem>
3735
          <para>There must be a mechanism for specifying which traffic
3735
          <para>There must be a mechanism for specifying which traffic
3736
            should be encrypted.  Obviously, you don't want to encrypt
3736
            should be encrypted.  Obviously, you do not want to encrypt
3737
            all your outgoing traffic -- you only want to encrypt the
3737
            all your outgoing traffic -- you only want to encrypt the
3738
            traffic that is part of the VPN.  The rules that you put in
3738
            traffic that is part of the VPN.  The rules that you put in
3739
            place to determine what traffic will be encrypted are called
3739
            place to determine what traffic will be encrypted are called
Lines 3811-3817 Link Here
3811
         this to encrypt the traffic over the VPN.  They periodically
3811
         this to encrypt the traffic over the VPN.  They periodically
3812
         change this secret, so that even if an attacker were to crack one
3812
         change this secret, so that even if an attacker were to crack one
3813
         of the keys (which is as theoretically close to unfeasible as it
3813
         of the keys (which is as theoretically close to unfeasible as it
3814
         gets) it won't do them much good -- by the time they've cracked
3814
         gets) it will not do them much good -- by the time they have cracked
3815
         the key the two daemons have chosen another one.</para>
3815
         the key the two daemons have chosen another one.</para>
3816
 
3816
 
3817
       <para>racoon's configuration is stored in
3817
       <para>racoon's configuration is stored in

Return to bug 77729