From 68ec561ecb25cdd48a2dac5080919a478956e142 Mon Sep 17 00:00:00 2001 From: Jameson Graef Rollins Date: Fri, 31 Jul 2009 10:27:52 -0400 Subject: [PATCH] small typo fix in lca2010 abstract --- doc/conferences/lca2010/abstract | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/conferences/lca2010/abstract b/doc/conferences/lca2010/abstract index 0b18528..2770675 100644 --- a/doc/conferences/lca2010/abstract +++ b/doc/conferences/lca2010/abstract @@ -7,7 +7,7 @@ automatically fully authenticate people and servers. The Secure Shell protocol has offered public-key-based mutual authentication since its inception, but popular implementations offer no formalized public key infrastructure. This means there is no -straightforward, computable method to to signal re-keying events, key +straightforward, computable method to signal re-keying events, key revocations, or even basic key-to-identity binding (e.g. "host foo.example.org has key X"). As a result, dealing with host keys is usually a manual process with the possibility of tedium, room for -- 2.25.1