Attachment 51113 Details for Bug 77729 – contrac4.diff

[patch] contrac4.diff

contrac4.diff (text/plain), 4.75 KB, created by Joel Dahl on 2005-02-19 13:40:15 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Joel Dahl

Created: 2005-02-19 13:40:15 UTC

Size: 4.75 KB

patch

obsolete

>Index: firewalls/chapter.sgml
>===================================================================
>RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml,v
>retrieving revision 1.36
>diff -u -r1.36 chapter.sgml
>--- firewalls/chapter.sgml	18 Feb 2005 12:08:24 -0000	1.36
>+++ firewalls/chapter.sgml	19 Feb 2005 13:14:01 -0000
>@@ -258,7 +258,7 @@
> 	    <entry>PF is part of the base system.
> 	      Do <emphasis>not</emphasis> use the
> 	      <filename role="package">security/pf</filename> port
>-	      on these versions of &os;.  It won't work.
>+	      on these versions of &os;.  It will not work.
> 	      Use the &man.pf.4; support of the base system instead.</entry>
> 	  </row>
> 	</tbody>
>@@ -2587,7 +2587,7 @@
>             may be allowed in by the later authorized service rules.
>             Second reason is that by having a rule that explicitly
>             blocks selected packets that I receive on an infrequent
>-            bases and don't want to see in the log, this keeps them from
>+            bases and do not want to see in the log, this keeps them from
>             being caught by the last rule in the section which blocks
>             and logs all packets which have fallen through the rules.
>             The last rule in the section which blocks and logs all
>Index: ports/chapter.sgml
>===================================================================
>RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v
>retrieving revision 1.238
>diff -u -r1.238 chapter.sgml
>--- ports/chapter.sgml	13 Feb 2005 10:24:10 -0000	1.238
>+++ ports/chapter.sgml	19 Feb 2005 13:13:04 -0000
>@@ -331,7 +331,7 @@
>        <replaceable>string</replaceable> is some text to search for.
>        This searches port names, comments, descriptions and
>        dependencies and can be used to find ports which relate to a
>-       particular subject if you don't know the name of the program
>+       particular subject if you do not know the name of the program
>        you are looking for.</para>
> 
>       <para>In both of these cases, the search string is case-insensitive.
>Index: security/chapter.sgml
>===================================================================
>RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v
>retrieving revision 1.262
>diff -u -r1.262 chapter.sgml
>--- security/chapter.sgml	13 Feb 2005 10:24:10 -0000	1.262
>+++ security/chapter.sgml	19 Feb 2005 13:22:57 -0000
>@@ -2425,7 +2425,7 @@
>       <para>Now it is time to start up the <acronym>KDC</acronym> services.
> 	Run <command>/etc/rc.d/kerberos start</command> and
> 	<command>/etc/rc.d/kadmind start</command> to bring up the
>-	services.  Note that you won't have any kerberized daemons running
>+	services.  Note that you will not have any kerberized daemons running
> 	at this point but you should be able to confirm the that the
> 	<acronym>KDC</acronym> is functioning by obtaining and listing a
> 	ticket for the principal (user) that you just created from the
>@@ -2697,7 +2697,7 @@
> 	      and reverse) in <acronym>DNS</acronym> (or
> 	      <filename>/etc/hosts</filename> as a minimum).  CNAMEs
> 	      will work, but the A and PTR records must be correct and in
>-	      place. The error message isn't very intuitive:
>+	      place. The error message is not very intuitive:
> 	      <errorname>Kerberos5 refuses authentication because Read req
> 	      failed: Key table entry not found</errorname>.</para>
> 	  </listitem>
>@@ -3371,7 +3371,7 @@
>         </listitem>
>         <listitem>
>           <para>The internal addresses of the two networks can be
>-            public or private IP addresses, it doesn't matter.  You can
>+            public or private IP addresses, it does not matter.  You can
>             be running NAT on the gateway machine if necessary.</para>
>         </listitem>
>         <listitem>
>@@ -3733,7 +3733,7 @@
>         </listitem>
>         <listitem>
>           <para>There must be a mechanism for specifying which traffic
>-            should be encrypted.  Obviously, you don't want to encrypt
>+            should be encrypted.  Obviously, you do not want to encrypt
>             all your outgoing traffic -- you only want to encrypt the
>             traffic that is part of the VPN.  The rules that you put in
>             place to determine what traffic will be encrypted are called
>@@ -3811,7 +3811,7 @@
>          this to encrypt the traffic over the VPN.  They periodically
>          change this secret, so that even if an attacker were to crack one
>          of the keys (which is as theoretically close to unfeasible as it
>-         gets) it won't do them much good -- by the time they've cracked
>+         gets) it will not do them much good -- by the time they have cracked
>          the key the two daemons have chosen another one.</para>
>  
>        <para>racoon's configuration is stored in

Actions: View | Diff

Attachments on bug 77729: 51113