I'm trying to understand Maven 3's[password encryption feature. I have found that this feature is poorly documented and confusing. For example, the feature documentation and a blog post by the author of the feature contradict each other about several points.
This question is broader than How does maven --encrypt-master-password work and is not covered by Maven encrypt-master-password good practice for choosing password.
Specifically, I am trying to answer the following questions which are not covered by the documentation. I've put what information I have been able to gather so far below each question in italics.
- Does the encrypted master password provide security simply by existing in
settings-security.xml
in a folder that only one user can access (~/.m2
)? If so, why bother with encrypting a 'master password' (why not just use some random value)? Isn't the 'master password' really just an entropy input to the cryptographic function? Calling it a password is confusing - I expected Maven to prompt me for this password before de-crypting any encrypted server passwords, but it did not.
My understanding is that yes, this only provides security by existing in an operating-system protected file. I believe Maven allows you to encrypt a master password so that if you loose the settings-security.xml
file you can re-generate it. Is this correct?
- Do the master password and server passwords use the same encryption process/cipher? The server passwords are based on the master password, so there must be some difference in the algorithm. Where is the source code for this located?
Marcelo Morales' answer on How does maven --encrypt-master-password work links to the plexus-cihper project on GitHub. It isn't clear if that is just the cipher, or the actual Maven plugin that provides the password functionality though.
- I have observed that the same master password or server password encrypted multiple times gives different hashes. According to Marcelo Morales' answer on How does maven --encrypt-master-password work, this is because 'a JVM-configuration-specific (usually SHA1PRNG) 64-bit random salt' is added to the password prior to encrypting. Maven decrypts stored passwords when they are used at compile time. Doesn't this mean the salts have to be stored somewhere?
I have no idea.
- I have also observed that a regular password encrypted using one encrypted master password will still work if the master password is re-encrypted and stored in the
settings-security.xml
file, even though the encrypted master password ciphertext is now different. Can someone explain how this works?
I have no idea. This seems to me like Maven is doing something fishy or storing cleartext somewhere.
- My understanding is that the encrypted passwords can only be used with
<server />
tags in thesettings.xml
file. is this true? Where can servers defined insettings.xml
be used?
My understanding is that <server />
definitions can be used in <repositories />
and <distributionManagement />
, but not <scm />
. Can someone verify this?
- For such a critical feature (build system security) it seems to me that there is a lot of confusion and poor documentation. Can someone point out how the documentation on the Maven 3 website works? Is there a wiki link somewhere that would allow me to try and improve the documentation at all?
I have no idea
Sorry for the wall of text, and thanks for any answers.
settings-security.xml
on an external storage device like usb. If you like to improve the docs or suggest how it could be improved or better explained please create an appropriate JIRA: issues.apache.org/jira/browse/MNGSITE – khmarbaise