search

dxc-technology / Hanlon-Microkernel

A small (in-memory) Microkernel used by the Hanlon server for discovery of new nodes
Other
20 stars 21 forks source link

Documentation for SSH Password for devel/debug images #14

Closed hh closed 8 years ago

hh commented 10 years ago

The releases allow for ssh, but do not seem to document the used default password.

https://github.com/csc/Hanlon-Microkernel/releases/tag/v2.0.0

hh commented 10 years ago

https://github.com/csc/Hanlon-Microkernel/blob/46dcd8d38cdd682202accc42cd53096edb0f9c7b/build-bundle-file.sh#L477

tjmcs commented 10 years ago

As a general rule, I try not to post default passwords on public Wiki pages (where a simple Google search can find them). That being said, the real reason that the default password isn't documented is that it is so easy to change on the command line (using the -t, --tc-passwd=PASSWD option to the build-bundle-file.sh script). Not only that, but for users of the production Microkernel, the only one of these three ISOs that we recommend using in a production environment, default password really doesn't matter (because that Microkernel doesn't provide a mechanism for getting to the command line, either locally via the console or remotely via SSH). The other two Microkernel types that we support in this project, the debug and development Microkernels, are really not suitable for use in a production environment because of the existence of the default password and SSH keys that are burned into them).

Finally, our assumption when we released the original Razor (and Razor-Microkernel) projects was that many users would want to build their own (custom) Microkernel images (to support their own hardware). The Microkernels provided in the releases area of this project are still a good starting point for most users who are using Hanlon with commodity hardware, but for more specialized gear you are going to likely have to add additional drivers that aren't included in the default Microkernel images we've provided in a pre-built form through the releases page of this project. In those cases, my assumption would be that the user building their own Microkernel would likely setup a "non-default" password that is different from the one we've embedded in that script.

That being said, if there are others who really feel strongly that we should document this default password other than in the codebase, speak up. I'm more than happy to try to document it if others feel that it should be documented outside of the script...

Thoughts?

hh commented 10 years ago

Thanks for the quick and thorough response. :) I feel it's good to be clear that there is a default (and what that default is), and that it is exposed if you use the devel/debug images, of course we should point to the build-bundle process as a suggested next step.

tjmcs commented 8 years ago

Closing, as the way that we setup these passwords is now completely documented in the Wiki (for the new, Docker-based Microkernel images)