Penguin
Diff: OpportunisticEncryption
EditPageHistoryDiffInfoLikePages

Differences between version 2 and previous revision of OpportunisticEncryption.

Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History

Newer page: version 2 Last edited on Friday, October 3, 2003 4:51:54 pm by CraigBox Revert
Older page: version 1 Last edited on Friday, October 3, 2003 4:51:03 pm by CraigBox Revert
@@ -5,7 +5,7 @@
 [IPSec] previously suffered from a scaling problem in that that the system/network administrators from any pair of systems or networks that want to have encryption between them had to exchange some sort of PublicKey. 
  
 With OE, each system/network administrator puts the key(s) needed to create IPSEC tunnels with their networks into the [DNS]. Then when another OE enabled IPSEC gateway wants to send packets to a host on the Internet, a check is first done to see if there are any keys in the DNS for that host and if there are, they are fetched and an encrypted tunnel is set up transparently. If there are no keys, then the packets MAY (if the administrator of the sending network allows so in his security policy) be sent in the clear. 
  
-FreeSwan 2 does OE out of the box. [FreeSWAN's quickstart to Opportunistic Encryption|http://www.freeswan.org/freeswan_trees/CURRENT-TREE/doc/quickstart.html] might help. 
+FreeSwan 2 does [ OE] out of the box. [FreeSWAN's quickstart to Opportunistic Encryption|http://www.freeswan.org/freeswan_trees/CURRENT-TREE/doc/quickstart.html] might help. 
  
 See the very readable [IETF draft for the Opportunistic Encryption specification|http://www.sandelman.ottawa.on.ca/SSW/freeswan/oeid/draft-richardson-ipsec-opportunistic.html]