[ https://issues.jboss.org/browse/ELY-1189?page=com.atlassian.jira.plugin.s... ] Peter Skopek commented on ELY-1189: ----------------------------------- dmlloyd commented on 11 Jan This is a fair point @zregvart. But from an API perspective it can cause a problem since the IV necessarily has to impact the equality of a Password object, being a constituent part of its fields. Since security is not really an expectation with masked passwords (it's a two-way password type with no ancillary information, meaning that if you have the mask string, you have the original password), it might make sense to have a separate MaskedPassword versus EncryptedPassword, the latter including an IV? Or maybe it's simply not worth worrying about the IV variants (since that's essentially a new feature). -- This message was sent by Atlassian JIRA (v7.2.3#72005)