Update a comment to reflect the addition of TLS support. [skip ci]

If TLS is used with rpcap, user names and pasword don't go over the wire
in clear text.

(cherry picked from commit 19802b3f6ef7502a3fb33ce298af8e13d5878dae)

diff --git a/pcap/pcap.h b/pcap/pcap.h
index e66abb04f066ab021bdd81ece81cbbcc1054b117..aa03856eb0f10cab668c12bfa7cc2d0f17937b16 100644 (file)
--- a/pcap/pcap.h
+++ b/pcap/pcap.h
@@ -1013,10 +1013,11 @@ PCAP_API const char *pcap_lib_version(void);
  * authentication is successful (and the user has the right to open network
  * devices) the RPCAP connection will continue; otherwise it will be dropped.
  *
- * *******NOTE********: the username and password are sent over the network
- * to the capture server *IN CLEAR TEXT*.  Don't use this on a network
- * that you don't completely control!  (And be *really* careful in your
- * definition of "completely"!)
+ * *******NOTE********: unless TLS is being used, the username and password
+ * are sent over the network to the capture server *IN CLEAR TEXT*.  Don't
+ * use this, without TLS (i.e., with rpcap:// rather than rpcaps://) on
+ * a network that you don't completely control!  (And be *really* careful
+ * in your definition of "completely"!)
  */
 #define RPCAP_RMTAUTH_PWD 1