From d2884184607fed7785f37634f621b8288a3a106d Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Thu, 4 Feb 2010 21:55:16 +0000 Subject: SSL fingerprint is deprecated Removing all references to the old method of using fingerprints to verify the server you are communicating with. The new way to do this is to use the 'ca' option in bcfg2.conf along with the bcfg2 server's CA certificate. Signed-off-by: Sol Jerome git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@5712 ce84e21b-d406-0410-9b95-82705330c041 --- doc/authentication.txt | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'doc/authentication.txt') diff --git a/doc/authentication.txt b/doc/authentication.txt index ae585da5b..a7baa78d2 100644 --- a/doc/authentication.txt +++ b/doc/authentication.txt @@ -45,16 +45,13 @@ bcfg2.conf from the per-client metadata:: #else password = my-password-foobat #endif - fingerprint = d8b7423da5d8ccd0f3db29742fc8eed00b9d0848 [components] bcfg2 = https://localhost:6789 In this setup, this will cause any clients that have uuids established to be set to use them in bcfg2.conf. It will also cause any clients -with passwords set to use them instead of the global password. The -fingerprint needs to be manually set, per-server, using the output of -"bcfg2-admin fingerprint". +with passwords set to use them instead of the global password. How Authentication Works ======================== -- cgit v1.2.3-1-g7c22