Reflect config changes for crypto in examples

Signed-off-by: Jan Friesse <jfriesse@redhat.com>
Reviewed-by: Fabio M. Di Nitto <fdinitto@redhat.com>

conf/corosync.conf.example

@@ -2,10 +2,11 @@
 totem {
 	version: 2
 
-	# secauth: Enable mutual node authentication. If you choose to
-	# enable this ("on"), then do remember to create a shared
+	# cypto_cipher and crypto_hash: Used for mutual node authentication.
+	# If you choose to enable this, then do remember to create a shared
 	# secret with "corosync-keygen".
-	secauth: off
+	crypto_cipher: none
+	crypto_hash: none
 
 	# interface: define at least one interface to communicate
 	# over. If you define more than one interface stanza, you must

conf/corosync.conf.example.udpu

@@ -1,7 +1,8 @@
 # Please read the corosync.conf.5 manual page
 totem {
 	version: 2
-	secauth: off
+	crypto_cipher: none
+	crypto_hash: none
 	interface {
 		member {
 			memberaddr: 10.16.35.101

conf/corosync.xml.example

@@ -9,12 +9,12 @@
 <!--
     totem tag configures behavior of totem and interfaces.
 
-    secauth:
-	Enable mutual node authentication. If you choose to
-	enable this ("on"), then do remember to create a shared
+    cypto_cipher and crypto_hash:
+	Used for mutual node authentication. If you choose to
+	enable this, then do remember to create a shared
 	secret with "corosync-keygen".
 -->
-<totem version="2" secauth="off">
+<totem version="2" crypto_cipher="none" crypto_hash="none">
     <!--
 	interface tag to define at least one interface to communicate
 	over. If you define more than one interface stanza, you must