From 540c4883d6f2de25dd38db0c18d59d568cd35f1e Mon Sep 17 00:00:00 2001
From: Dolph Mathews <dolph.mathews@gmail.com>
Date: Fri, 13 Jul 2012 14:54:24 -0500
Subject: [PATCH] Secure password prompt (docs)

Change-Id: I879a8aba13318f1dd660a487cbd1fd20c7ae659b
---
 README.rst | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/README.rst b/README.rst
index a935ef8440..4ea7000d4b 100644
--- a/README.rst
+++ b/README.rst
@@ -66,14 +66,17 @@ The 'password flow' variation is most commonly used::
    export OS_AUTH_URL=<url-to-openstack-identity>
    export OS_TENANT_NAME=<tenant-name>
    export OS_USERNAME=<user-name>
-   export OS_PASSWORD=<password>    # yes, it isn't secure, we'll address it in the future
+   export OS_PASSWORD=<password> # (optional)
 
 The corresponding command-line options look very similar::
 
    --os-auth-url <url>
    --os-tenant-name <tenant-name>
    --os-username <user-name>
-   --os-password <password>
+   [--os-password <password>]
+
+If a password is not provided above (in plaintext), you will be interactively
+prompted to provide one securely.
 
 The token flow variation for authentication uses an already-aquired token
 and a URL pointing directly to the service API that presumably was acquired