> > Hello tech@,
> >
> > Here is a minor diff to do a little more strict checking on the device id
> > for
> > urandom. It would be a shame if someone replaced a genuine urandom with a
> > /dev/null or some other predictable device.
>
> that's what the ioctl is for
Actually, the ioctl does not
On Wed, 25 Jun 2014, Martijn van Duren wrote:
> Hello tech@,
>
> Here is a minor diff to do a little more strict checking on the device id for
> urandom. It would be a shame if someone replaced a genuine urandom with a
> /dev/null or some other predictable device.
that's what the ioctl is for
> On 06/25/14 21:15, Theo de Raadt wrote:
> >> Here is a minor diff to do a little more strict checking on the device
> >> id for urandom. It would be a shame if someone replaced a genuine
> >> urandom with a /dev/null or some other predictable device.
> >>
> >> if a file is not special st_rdev wil
On 06/25/14 21:15, Theo de Raadt wrote:
Here is a minor diff to do a little more strict checking on the device
id for urandom. It would be a shame if someone replaced a genuine
urandom with a /dev/null or some other predictable device.
if a file is not special st_rdev will be 0 so S_ISCHR isn'
> Here is a minor diff to do a little more strict checking on the device
> id for urandom. It would be a shame if someone replaced a genuine
> urandom with a /dev/null or some other predictable device.
>
> if a file is not special st_rdev will be 0 so S_ISCHR isn't needed anymore.
So you are tr
Hello tech@,
Here is a minor diff to do a little more strict checking on the device
id for urandom. It would be a shame if someone replaced a genuine
urandom with a /dev/null or some other predictable device.
if a file is not special st_rdev will be 0 so S_ISCHR isn't needed anymore.
Sincere
