Network2/Security: Difference between revisions

Revision as of 23:53, 26 July 2009

This optional section is included merely to offer some hints about where we think communications security ought to be headed.

Spoofing, Integrity, Confidentiality. See communications security and petnames for some background. A very rough road along which something reasonable might lie:
- Use physical introduction to CNAME cscott.michael.laptop.org to <key>.cscott.laptop.org.
- Then, my dnscurve-compatible DNS resolver will refuse to give me addresses unless the nameserver I contact for cscott proves knowledge of cscott's private key.
- Then I have a nice basis with which to configure IPsec security associations.
System Integrity
DoS

Revision as of 23:52, 26 July 2009 (view source) Mstone (talk \| contribs) m (New page: This ''optional'' section is included merely to offer some hints about where we think communications security ought to be headed. # Spoofing, Integrity, Confid...)		Revision as of 23:53, 26 July 2009 (view source) Mstone (talk \| contribs) mNo edit summary Newer edit →
Line 1:		Line 1:
			{{Network2 header}}

	This ''optional'' section is included merely to offer some hints about where we think [[Communications security\|communications security]] ought to be headed.		This ''optional'' section is included merely to offer some hints about where we think [[Communications security\|communications security]] ought to be headed.