> I'm not following how this helps my case, Keith. I have a truststore with no > password. I don't want the keystore to be used.
Ok. I suggested because I suspected the truststore was created because it was required and duplicated CA info already in the keystore. But that is not your use case, so ignore that line of thought. I think there two distinct issues to consider with this change : password quality and was a password set. It may make sense to require setting a password. However, nothing should be baked into the code that attempts to measure password quality and reject bad passwords. If we are going to disallow empty string, then why stop there? Why not also disallow single character passwords? In the 2.0 branch I think I added something to AccumuloConfig to check if a prop was set or not, but I don't think this is in 1.9. If there is an easy way to distinguish between set and not set in 1.9, then I think requiring the user to set any password (including empty string) would be good. If this solution is not easy to do in 1.9, then I don't have strong opinion for or against making this change as is. [ Full content available at: https://github.com/apache/accumulo/pull/646 ] This message was relayed via gitbox.apache.org for [email protected]
