roject and RPI 4
> documentation claims to support network boot. Some posts suggest that
> booting over PXE is supported.
>
> Before I dump money on hardware, does anyone have experience with
> autoinstall on RPi 4 (or Compute Module 4) over network and could
> confirm that it
Hi,
I'm considering a netbootable device for a project and RPI 4
documentation claims to support network boot. Some posts suggest that
booting over PXE is supported.
Before I dump money on hardware, does anyone have experience with
autoinstall on RPi 4 (or Compute Module 4) over networ
On 08/17/14 15:35, Clint Pachl wrote:
Christian Weisgerber wrote, On 08/16/14 08:54:
On 2014-08-16, Christian Weisgerber wrote:
How about making etc/random.seed a named pipe and feeding chunks
of /dev/random to it?
I've now put this into my /etc/rc.local:
--->
# Provide fres
Christian Weisgerber wrote, On 08/16/14 08:54:
On 2014-08-16, Christian Weisgerber wrote:
How about making etc/random.seed a named pipe and feeding chunks
of /dev/random to it?
I've now put this into my /etc/rc.local:
--->
# Provide fresh random.seed for pxeboot
if cd /tftpb
This is starting to remind me of Ubuntu's pollen/pollinate services.
On Sat, Aug 16, 2014 at 11:31 AM, Theo de Raadt
wrote:
> I wonder if there would be some benefit to faking these files from inside
> the tftp daemon itself..
I wonder if there would be some benefit to faking these files from inside
the tftp daemon itself..
On 2014-08-16, Christian Weisgerber wrote:
> How about making etc/random.seed a named pipe and feeding chunks
> of /dev/random to it?
I've now put this into my /etc/rc.local:
--->
# Provide fresh random.seed for pxeboot
if cd /tftpboot/etc; then
rm -f random.seed
On 2014-08-16, Clint Pachl wrote:
>> # cd /tftpboot
>> # mkfifo etc/random.seed
>> # while true; do dd if=/dev/random count=1 >etc/random.seed 2>/dev/null;
>> done &
>
> # cd /tftpboot
> # mkfifo test.seed
> # while :; do dd if=/tmp/counter of=test.seed 2>/dev/null; done &
Careful!
"dd ... >fi
Christian Weisgerber wrote, On 08/15/14 18:36:
On 2014-08-15, Paul de Weerd wrote:
What you could do is use the -r option to tftpd(8) to hand out a new
file to each client that connects. Or just periodically (like, every
hour or every minute, depending on the load of your tftp server)
replace
Paul de Weerd wrote, On 08/15/14 14:51:
At any rate, this changes that to allow world readable files (still
not taking world writable files). We can't check S_IWOTH over tftp,
we should probably assume 0777 for files transferred that way. But,
if you're trusting the kernel you're getting over t
On August 16, 2014 12:09:32 AM CEST, Paul de Weerd wrote:
>On Fri, Aug 15, 2014 at 11:51:53PM +0200, Paul de Weerd wrote:
>| At any rate, this changes that to allow world readable files (still
>| not taking world writable files). We can't check S_IWOTH over tftp,
>| we should probably assume 0777
On August 15, 2014 11:51:53 PM CEST, Paul de Weerd wrote:
>On Fri, Aug 15, 2014 at 06:55:49PM +0200, Alexander Hall wrote:
>| On 08/15/14 16:22, Paul de Weerd wrote:
>| >On Fri, Aug 15, 2014 at 04:07:21PM +0200, Alexander Hall wrote:
>| >| On August 15, 2014 2:04:56 PM CEST, Theo de Raadt
> wrote:
On 2014-08-15, Paul de Weerd wrote:
> What you could do is use the -r option to tftpd(8) to hand out a new
> file to each client that connects. Or just periodically (like, every
> hour or every minute, depending on the load of your tftp server)
> replace it with a new random file.
How about mak
On Fri, Aug 15, 2014 at 11:51:53PM +0200, Paul de Weerd wrote:
| At any rate, this changes that to allow world readable files (still
| not taking world writable files). We can't check S_IWOTH over tftp,
| we should probably assume 0777 for files transferred that way. But,
| if you're trusting the
On Fri, Aug 15, 2014 at 06:55:49PM +0200, Alexander Hall wrote:
| On 08/15/14 16:22, Paul de Weerd wrote:
| >On Fri, Aug 15, 2014 at 04:07:21PM +0200, Alexander Hall wrote:
| >| On August 15, 2014 2:04:56 PM CEST, Theo de Raadt
wrote:
| >| >> Is it safe to generate some randomness in /tftpboot/et
On 08/15/14 16:22, Paul de Weerd wrote:
On Fri, Aug 15, 2014 at 04:07:21PM +0200, Alexander Hall wrote:
| On August 15, 2014 2:04:56 PM CEST, Theo de Raadt
wrote:
| >> Is it safe to generate some randomness in /tftpboot/etc/random.seed
| >for
| >> clients that PXE boot?
| >
| >I do not even kno
On Fri, Aug 15, 2014 at 04:07:21PM +0200, Alexander Hall wrote:
| On August 15, 2014 2:04:56 PM CEST, Theo de Raadt
wrote:
| >> Is it safe to generate some randomness in /tftpboot/etc/random.seed
| >for
| >> clients that PXE boot?
| >
| >I do not even know if that file will be read... is it?
|
On August 15, 2014 2:04:56 PM CEST, Theo de Raadt
wrote:
>> Is it safe to generate some randomness in /tftpboot/etc/random.seed
>for
>> clients that PXE boot?
>
>I do not even know if that file will be read... is it?
IIRC, it is tried but deemed unsafe (0555) and therefore isn't used, but cause
On 2014-08-15, Theo de Raadt wrote:
>> Is it safe to generate some randomness in /tftpboot/etc/random.seed for
>> clients that PXE boot?
>
> I do not even know if that file will be read... is it?
I would hope so since pxeboot complains about its absence:
>> OpenBSD/amd64 PXEBOOT 3.23
boot>
ca
On Fri, Aug 15, 2014 at 06:04:56AM -0600, Theo de Raadt wrote:
| > Is it safe to generate some randomness in /tftpboot/etc/random.seed for
| > clients that PXE boot?
|
| I do not even know if that file will be read... is it?
Yes, it is. Twice, in fact:
Aug 15 14:13:34 tuna tftpd[14711]: 192.16
> Is it safe to generate some randomness in /tftpboot/etc/random.seed for
> clients that PXE boot?
I do not even know if that file will be read... is it?
> My concern is that this file will be available to everyone on the
> network via TFTP. So does knowing this randomness help "predict" the
>
On Fri, Aug 15, 2014 at 01:24:02AM -0700, Clint Pachl wrote:
| Is it safe to generate some randomness in /tftpboot/etc/random.seed for
| clients that PXE boot?
|
| My concern is that this file will be available to everyone on the network
| via TFTP. So does knowing this randomness help "predict" t
Is it safe to generate some randomness in /tftpboot/etc/random.seed for
clients that PXE boot?
My concern is that this file will be available to everyone on the
network via TFTP. So does knowing this randomness help "predict" the
PRNG output of the clients that use it?
I read in a de Raadt i
On May 30 05:08 PM, Alari Kask wrote:
> I have a vision of something like this :
>
> My OpenBSD machine acts as a pxe boot server, clients on the lan boot
> pxe and get a choice of booting the operating system on the clients hard
> drive, or boot openbsd kernel for installation or diagnostics and
Hi
On 05/30, Alari Kask wrote:
> I have a vision of something like this :
>
> My OpenBSD machine acts as a pxe boot server, clients on the lan boot
> pxe and get a choice of booting the operating system on the clients hard
> drive, or boot openbsd kernel for installation or diagnostics and for
>
I have a vision of something like this :
My OpenBSD machine acts as a pxe boot server, clients on the lan boot
pxe and get a choice of booting the operating system on the clients hard
drive, or boot openbsd kernel for installation or diagnostics and for
example boot memtest86 or some other diagnos
26 matches
Mail list logo
