Date: Fri, 05 Nov 2010 23:06:17 -0600 (MDT) From: Warner Losh <imp@bsdimp.com> To: gcooper@FreeBSD.org Cc: jpaetzel@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: txt-sysinstall scrapped Message-ID: <20101105.230617.74669306.imp@bsdimp.com> In-Reply-To: <AANLkTi=62rRhZsN4wUi6p_yokSxG0tkjUHK7gosLtTRZ@mail.gmail.com> References: <201011052316.27839.jpaetzel@freebsd.org> <AANLkTi=62rRhZsN4wUi6p_yokSxG0tkjUHK7gosLtTRZ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Just to add to that (because I do find it a novel idea), 1) how > are you going to properly prevent man in the middle attacks (SSL, TLS, > etc?), and 2) what webserver would you use? https or ssh. We're also toying with the idea of having a partition that you could 'dd' your certs and keys to (so any system can customize the image with keys to make sure you were talking to who you think you are). We'd just reserve 1MB of space on partition s3. We'd then check to see if there was a tar ball. If so, we'd extract it and do the intelligent thing with the keys we find there. > I bring up the former item because I wouldn't want my data going > unencrypted across any wire, and what BSD compatible web servers did > you guys have in store and who would maintain the server, and what > kinds of vulnerabilities would you be introducing by adding a service > which would be enabled by default at runtime? The web server would just be there at installation time. You'd run it out of the ram disk and it would evaporate when the system reboots after it being installed. Also, I'm not sure we even need to have to have a set of prompts. If we do the web page right, we likely can just go directly to lynx... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101105.230617.74669306.imp>