Some examples (e.g., SASL examples) include strings that are encoded using Base64 (see &rfc3548;). An easy way to generate these is to place the source text in a file and use the OpenSSL "enc" command to generate the base64-encoded equivalent. For example, if the file "tmp.txt" contains the string "bard@shakespeare.lit" then the command 'openssl enc -base64 -in tmp.txt' will generate the base64-encoded string "YmFyZEBzaGFrZXNwZWFyZS5saXQK".
-Some examples (e.g., avatar examples) include strings that are SHA-1 hashes (see &rfc3174;). An easy way to generate these is to place the source text in a file and use the OpenSSL "dgst" command to generate the SHA-1 hash. For example, if the file "tmp.txt" contains the string "bard@shakespeare.lit" then the command 'openssl dgst -sha1 tmp.txt' will generate the SHA-1 hash "e87f5008d779053ac53b29b335b7be8820d5c303".
+Some examples (e.g., SASL examples) include strings that are encoded using Base64 (see &rfc3548;). An easy way to generate these is to use the OpenSSL "enc" command to generate the base64-encoded equivalent. For example, the following command will generate the base64-encoded string "YmFyZEBzaGFrZXNwZWFyZS5saXQ=":
+
+echo -n 'bard@shakespeare.lit' | openssl enc -base64
+
+ Some examples (e.g., avatar examples) include strings that are SHA-1 hashes (see &rfc3174;). An easy way to generate these is to use the OpenSSL "dgst" command to generate the SHA-1 hash. For example, the following command will generate the SHA-1 hash "9f5f9fdab9da7fc12e3c52b258acbcb4bb8e66ac":
+
+echo -n 'bard@shakespeare.lit' | openssl dgst -sha1
+
Conformance terms (e.g,, "MUST" and "SHOULD") are specified in RFC 2119. Use them. When such terms are not in ALL CAPS, the special conformance sense does not apply (this should be obvious but may not be to all authors).