Martin Husemann <martin%duskware.de@localhost> writes: > On Wed, Jan 27, 2016 at 07:09:17PM -0500, Greg Troxel wrote: >> It is irregular to enable ssh at install time without the user >> configuring it. Someone may want to do that, and they can patch their >> build. But it's a security bug to have it on by default. >> >> Another view is that machines should have a working console, and >> dealing with issues due to not having one is a workaround, not the main >> path. > > Or we could provide two images, the only difference being an additional > user (in group wheel) with documented password and predefined root password. > > Of course name that image accordingly so noone installs it accidently and > document all this very clear (at the same wiki page where we hopefully soon > clearly document what arch and kernel to use for which arm board). I see your point, but NetBSD has long had a secure by default notion, and I see that as a pretty serious line to cross. So if it does happen it probably should have -totally-insecure in the filename :-) I wonder if it would be reasonable to have a script/program that can run on an installed other-arch NetBSD system and modify the arm install image, so that people could make their own images (that depart from security norms, which is ok for them in controlled environments). With rump, it could perhaps run portably, and be in pkgsrc. This does sound like a lot of work.
Attachment:
signature.asc
Description: PGP signature