From c164e48096c89d82dc6fedf4ef16f0b2fa69fc1b Mon Sep 17 00:00:00 2001 From: https://www.google.com/accounts/o8/id?id=AItOawkgUir7k_amh9RFp4D3QutX1fGh_nd7ko4 Date: Sat, 13 Dec 2014 18:25:23 +0000 Subject: Added a comment: Passwords in PrivData --- doc/security/comment_7_ebbb6f3617c879715a35900a07ea1909._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/security/comment_7_ebbb6f3617c879715a35900a07ea1909._comment (limited to 'doc/security/comment_7_ebbb6f3617c879715a35900a07ea1909._comment') diff --git a/doc/security/comment_7_ebbb6f3617c879715a35900a07ea1909._comment b/doc/security/comment_7_ebbb6f3617c879715a35900a07ea1909._comment new file mode 100644 index 00000000..e9d20642 --- /dev/null +++ b/doc/security/comment_7_ebbb6f3617c879715a35900a07ea1909._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkgUir7k_amh9RFp4D3QutX1fGh_nd7ko4" + nickname="Philipp" + subject="Passwords in PrivData" + date="2014-12-13T18:25:23Z" + content=""" +I wonder if there could be a shortcut in PrivData handling that hashes the input with crypt() instead of passing it raw to a machine. For instance passwords are stored in plain on the target machines, while this is not required to set the password in shadow: the hash would suffice. I think this page should at least spell out that fact. +"""]] -- cgit v1.2.3