Am 07.02.2013 08:01, schrieb Alexander Holler:
And the dream of every vendor, finally a working expiration date. And a
nice TV-B-Gone, just feed a wrong date once. ;)
Just in case someone missed what I wanted to hint: That date problem has
implications for devices with a RTC too. If they
Am 07.02.2013 08:01, schrieb Alexander Holler:
And the dream of every vendor, finally a working expiration date. And a
nice TV-B-Gone, just feed a wrong date once. ;)
Just in case someone missed what I wanted to hint: That date problem has
implications for devices with a RTC too. If they
Am 11.02.2013 20:44, schrieb Alexander Holler:
Am 07.02.2013 19:44, schrieb Olaf Titz:
Another option would be to make a configure option to just ignore the
date. I'm not sure if I would like to use MODSIGN when I have to fear
that the machine wouldn't start when the RTC fails or got set to a
Am 11.02.2013 20:44, schrieb Alexander Holler:
Am 07.02.2013 19:44, schrieb Olaf Titz:
Another option would be to make a configure option to just ignore the
date. I'm not sure if I would like to use MODSIGN when I have to fear
that the machine wouldn't start when the RTC fails or got set to a
Am 07.02.2013 19:44, schrieb Olaf Titz:
Another option would be to make a configure option to just ignore the
date. I'm not sure if I would like to use MODSIGN when I have to fear
that the machine wouldn't start when the RTC fails or got set to a wrong
date.
Or just ignore the date
Am 07.02.2013 19:44, schrieb Olaf Titz:
Another option would be to make a configure option to just ignore the
date. I'm not sure if I would like to use MODSIGN when I have to fear
that the machine wouldn't start when the RTC fails or got set to a wrong
date.
Or just ignore the date
> Another option would be to make a configure option to just ignore the
> date. I'm not sure if I would like to use MODSIGN when I have to fear
> that the machine wouldn't start when the RTC fails or got set to a wrong
> date.
Or just ignore the date unconditionally. After all, when a certificate
Am 07.02.2013 08:01, schrieb Alexander Holler:
Am 07.02.2013 07:42, schrieb Geert Uytterhoeven:
On Thu, Feb 7, 2013 at 2:06 AM, Alexander Holler wrote:
Am 07.02.2013 00:42, schrieb Alexander Holler:
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
[1.346445]
Another option would be to make a configure option to just ignore the
date. I'm not sure if I would like to use MODSIGN when I have to fear
that the machine wouldn't start when the RTC fails or got set to a wrong
date.
Or just ignore the date unconditionally. After all, when a certificate
Am 07.02.2013 08:01, schrieb Alexander Holler:
Am 07.02.2013 07:42, schrieb Geert Uytterhoeven:
On Thu, Feb 7, 2013 at 2:06 AM, Alexander Holler hol...@ahsoftware.de wrote:
Am 07.02.2013 00:42, schrieb Alexander Holler:
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
Am 07.02.2013 07:42, schrieb Geert Uytterhoeven:
> On Thu, Feb 7, 2013 at 2:06 AM, Alexander Holler wrote:
>> Am 07.02.2013 00:42, schrieb Alexander Holler:
>>> I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
>>>
>>> [1.346445] X.509: Cert
On Thu, Feb 7, 2013 at 2:06 AM, Alexander Holler wrote:
> Am 07.02.2013 00:42, schrieb Alexander Holler:
>> I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
>>
>> [1.346445] X.509: Cert 6a23533cec71c4c52a1618fb4d830e06aa90474e is
>> not yet valid
>>
>> The reason is
Am 07.02.2013 00:42, schrieb Alexander Holler:
Hello,
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
[1.346445] X.509: Cert 6a23533cec71c4c52a1618fb4d830e06aa90474e is
not yet valid
The reason is likely that the (ARM) device in question doesn't have a
RTC (oh,
Hello,
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
[1.346445] X.509: Cert 6a23533cec71c4c52a1618fb4d830e06aa90474e is
not yet valid
The reason is likely that the (ARM) device in question doesn't have a
RTC (oh, that topic again ;) ) and gets it's time on boot
Hello,
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
[1.346445] X.509: Cert 6a23533cec71c4c52a1618fb4d830e06aa90474e is
not yet valid
The reason is likely that the (ARM) device in question doesn't have a
RTC (oh, that topic again ;) ) and gets it's time on boot
Am 07.02.2013 00:42, schrieb Alexander Holler:
Hello,
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
[1.346445] X.509: Cert 6a23533cec71c4c52a1618fb4d830e06aa90474e is
not yet valid
The reason is likely that the (ARM) device in question doesn't have a
RTC (oh,
On Thu, Feb 7, 2013 at 2:06 AM, Alexander Holler hol...@ahsoftware.de wrote:
Am 07.02.2013 00:42, schrieb Alexander Holler:
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
[1.346445] X.509: Cert 6a23533cec71c4c52a1618fb4d830e06aa90474e is
not yet valid
The reason
Am 07.02.2013 07:42, schrieb Geert Uytterhoeven:
On Thu, Feb 7, 2013 at 2:06 AM, Alexander Holler hol...@ahsoftware.de wrote:
Am 07.02.2013 00:42, schrieb Alexander Holler:
I wanted to try out MODSIGN with kernel 3.7.6 and I've just got hit by:
[1.346445] X.509: Cert
18 matches
Mail list logo
