f update docs and messages

Author: TheBlueMatt

rust/auth-impls/src/signature.rs

@@ -2,8 +2,10 @@
 //! come with a public key and proof of private key knowledge. Access is then granted to the user
 //! defined by the public key.
 //!
-//! Because no rate-limiting of new user accounts is done, a higher-level service is required to
-//! ensure requests are not triggering excess new user registrations.
+//! There is no specific restriction of who is allowed to store data in VSS using this
+//! authentication scheme, only that each user is only allowed to store and access data for which
+//! they have a corresponding private key. Thus, you must ensure new user accounts are
+//! appropriately rate-limited or access to the VSS server is somehow limited.
 //!
 //! [`Authorizer`]: api::auth::Authorizer
 

rust/server/src/main.rs

@@ -99,13 +99,14 @@ fn main() {
 		#[cfg(feature = "sigs")]
 		{
 			if authorizer.is_none() {
+				println!("Configured signature-validating authorizer");
 				authorizer = Some(Arc::new(SignatureValidatingAuthorizer));
 			}
 		}
 		let authorizer = if let Some(auth) = authorizer {
 			auth
 		} else {
-			println!("No authentication method configured, all storage will be comingled");
+			println!("No authentication method configured, all storage with the same store id will be commingled.");
 			Arc::new(NoopAuthorizer {})
 		};