>> Lack of good randomness does not quite equal insecure install. Warn
>> about it, sure, but I think *requiring* randomness is a bad idea.
>> For example, I've been working with recent NetBSD at work, for
>> something for which the presence or absence of good random-seed data
>> makes absolutely
On Mon, Nov 09, 2020 at 11:15:52PM +0100, Vincent DEFERT wrote:
> On 09/11/2020 21:49, m...@netbsd.org wrote:
> > Unfortunately it leads to surprise failures if programs ever use
> > /dev/random. If not seeded, reads from it will block forever.
> If it has such consequences, the installer - or
On 09/11/2020 21:49, m...@netbsd.org wrote:
Unfortunately it leads to surprise failures if programs ever use
/dev/random. If not seeded, reads from it will block forever.
If it has such consequences, the installer - or maybe a 'first-run'
startup script? - should of course take care of it.
That
On Mon, Nov 09, 2020 at 09:53:50AM -0500, Mouse wrote:
> > So: happy to make it more userfriendly, simpler, rephrase messages,
> > whatever needed - but we should not end up with insecure installs.
>
> Lack of good randomness does not quite equal insecure install. Warn
> about it, sure, but I
On Mon, Nov 09, 2020 at 10:10:56AM +, nia wrote:
> i run into it on real hardware, thinkpad t60.
>
> my preference is:
>
> - when booting in a VM, if there is no RNG device attached,
> the system should print a warning with instructions on how
> to attach the device.
In practice this
> So: happy to make it more userfriendly, simpler, rephrase messages,
> whatever needed - but we should not end up with insecure installs.
Lack of good randomness does not quite equal insecure install. Warn
about it, sure, but I think *requiring* randomness is a bad idea. For
example, I've been
On Mon, Nov 09, 2020 at 11:03:31AM +, nia wrote:
> On Mon, Nov 09, 2020 at 11:18:31AM +0100, Martin Husemann wrote:
> > On Mon, Nov 09, 2020 at 10:10:56AM +, nia wrote:
> > > fwiw, i think the default options should be as close to Just Work as
> > > possible.
> > >
> > > i have installed
On Mon, Nov 09, 2020 at 11:18:31AM +0100, Martin Husemann wrote:
> On Mon, Nov 09, 2020 at 10:10:56AM +, nia wrote:
> > fwiw, i think the default options should be as close to Just Work as
> > possible.
> >
> > i have installed NetBSD irl with people who have only a little bit of unix
> >
On Mon, Nov 09, 2020 at 10:10:56AM +, nia wrote:
> fwiw, i think the default options should be as close to Just Work as possible.
>
> i have installed NetBSD irl with people who have only a little bit of unix
> knowledge, and watched them wince every time something doesn't go as planned.
>
fwiw, i think the default options should be as close to Just Work as possible.
i have installed NetBSD irl with people who have only a little bit of unix
knowledge, and watched them wince every time something doesn't go as planned.
often this is on older, spare hardware, that's just to play with
On Sun, Nov 08, 2020 at 05:32:16PM +, nia wrote:
> after several changes in 9.1 and -current, it's strange to me that the option
> that I expect is the most popular for installing NetBSD (start over, fresh
> partitions, use the whole disk) is no longer the default option:
It never was and I
On Sun, 8 Nov 2020 at 17:32, nia wrote:
>
> after several changes in 9.1 and -current, it's strange to me that the option
> that I expect is the most popular for installing NetBSD (start over, fresh
> partitions, use the whole disk) is no longer the default option:
>
> > d: Delete everything, use
after several changes in 9.1 and -current, it's strange to me that the option
that I expect is the most popular for installing NetBSD (start over, fresh
partitions, use the whole disk) is no longer the default option:
> d: Delete everything, use different partitions
it's option 4! that doesn't
13 matches
Mail list logo
