On 21/02/2009, at 6:52 AM, Oleg Gusakov wrote:
Brett Porter wrote:
On 20/02/2009, at 10:19 PM, Brett Porter wrote:
Hi,
To make it a bit easier to remember, I added two options to the
CLI for 2.1: --enc-master-passwd and --enc-passwd; which are
equivalent to -m and -p on DefaultSecDispatcher.
For consistency with other options, it takes the password as an
option on the CLI rather than delegating to the DSD prompting.
Afterwards it terminates (like -v).
What do others think - is this the best way to configure it?
To reply to self - after talking to Benjamin and also reading the
docs I saw there was some plan to use a plugin to generate these.
This would also be useful for more general uses of the encryption,
but the reason I chose the CLI here is that you might need the
passwords to get the plugin in the first place, so this is more
convenient for a typical setup use case.
I have a problem with this alteration: as this CLI is a temporary
measure - I'd rather not have too many efforts to change that: -m
and -p are a clear indication that it's temporary.
If you start adding more stuff around temporary solutions, people
expect them supported in the future. Please remove them - the plugin
wil take care of the users long term.
I don't view this as a temporary measure - as my second comment said,
you may need a password to get the plugin in the first place. How
would you address this case?
Another one: "enc" is usually used for encoding, so it's at least
misleading.
Happy to change that to the full word if kept.
- Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
