> On Sep 29, 2017, at 7:18 PM, Florian Fainelli wrote:
>
>
>
> On 09/29/2017 06:01 PM, Philip Prindeville wrote:
>>
>> [snip]
>> Tested on x86_64. Seems to work.
>
> To avoid patching mored packages in the future, would it make sense to
> LD_PRELOAD a library which overrides the SYS_getrand
It seems security is ignored completely. getrandom() makes sure it
gets initialized before reading any random numbers.
The correct way is to backport new random facilities to old kernels or
just switch all old kernels to the new one.
Prevent getrandom() is a dangerous workaround to bypass the rea
On 09/29/2017 06:01 PM, Philip Prindeville wrote:
>
>> On Sep 29, 2017, at 4:39 AM, Felix Fietkau wrote:
>>
>> On 2017-09-29 12:20, Felix Fietkau wrote:
>>> On 2017-09-11 02:33, Philip Prindeville wrote:
Changing the subject from the previous thread as it turned out to not have
to do
> On Sep 29, 2017, at 4:39 AM, Felix Fietkau wrote:
>
> On 2017-09-29 12:20, Felix Fietkau wrote:
>> On 2017-09-11 02:33, Philip Prindeville wrote:
>>> Changing the subject from the previous thread as it turned out to not have
>>> to do with sysupgrade at all.
>>>
>>> What I can tell is this,
On 29.09.2017 14:07, Felix Fietkau wrote:
On 2017-09-29 13:04, Daniel Golle wrote:
On Fri, Sep 29, 2017 at 12:20:08PM +0200, Felix Fietkau wrote:
On 2017-09-11 02:33, Philip Prindeville wrote:
Changing the subject from the previous thread as it turned out to not have to
do with sysupgrade at
On 2017-09-29 13:04, Daniel Golle wrote:
> On Fri, Sep 29, 2017 at 12:20:08PM +0200, Felix Fietkau wrote:
>> On 2017-09-11 02:33, Philip Prindeville wrote:
>> > Changing the subject from the previous thread as it turned out to not have
>> > to do with sysupgrade at all.
>> >
>> > What I can tell
On Fri, Sep 29, 2017 at 12:20:08PM +0200, Felix Fietkau wrote:
> On 2017-09-11 02:33, Philip Prindeville wrote:
> > Changing the subject from the previous thread as it turned out to not have
> > to do with sysupgrade at all.
> >
> > What I can tell is this, having added some tracing to fstools.
>
On 2017-09-29 12:20, Felix Fietkau wrote:
> On 2017-09-11 02:33, Philip Prindeville wrote:
>> Changing the subject from the previous thread as it turned out to not have
>> to do with sysupgrade at all.
>>
>> What I can tell is this, having added some tracing to fstools.
>>
>> We get to the call
On 2017-09-11 02:33, Philip Prindeville wrote:
> Changing the subject from the previous thread as it turned out to not have to
> do with sysupgrade at all.
>
> What I can tell is this, having added some tracing to fstools.
>
> We get to the call to system() in rootdisk_volume_init():
>
> https:
On 11.09.2017 03:33, Philip Prindeville wrote:
Changing the subject from the previous thread as it turned out to not have to
do with sysupgrade at all.
What I can tell is this, having added some tracing to fstools.
We get to the call to system() in rootdisk_volume_init():
https://git.lede-pro
Changing the subject from the previous thread as it turned out to not have to
do with sysupgrade at all.
What I can tell is this, having added some tracing to fstools.
We get to the call to system() in rootdisk_volume_init():
https://git.lede-project.org/?p=project/fstools.git;a=blob;f=libfstoo
11 matches
Mail list logo