Once you start dealing with encryption, there will be export legalities and configuration issues (setting up different policy files).
Maybe we can avoid most of this by making the default encryption type something harmless and providing directions for enabling more encryption. Also, have you considered using JNDI instead? Some containers already provide encrypted JNDI data sources. On 8/10/06, Michael Gentry <[EMAIL PROTECTED]> wrote:
It looks like I might need the ability to encrypt the JDBC settings (or at least the password) in my current applications. Is this something that should be added to Cayenne (and Modeler) or should I think of alternative solutions? Note that this would be encrypted, not hashed, since that sometimes gets confused. There would need to be a facility to decrypt, too. Just looking for thoughts/ideas at this moment. Thanks, /dev/mrg
