Maybe the node should be auto-booted with a random name also (with the ability to modify the name later for those who are interested)
Problem is that the private key is needed to boot, so you have to input your password to decrypt it.
Could a mechanism be used whereby the password only has to be provided once to identify the user and link it to the client machine. Once positively authenticated create a certificate in the JVM which can be used for future boots. Could security be maintained by only allowing the use of a certificate if it already exists, if the machine remains running the same OS and the same user account (combine computer and user account identities)?
KC
