On 11/3/2016 3:26 PM, Brian E Carpenter wrote:
Yes, I agree it's possible to do better, but what's the incentive for a
bottom-feeding vendor
of cheap devices to bother?
Lawsuits, regulation, well respected security branding (awarded after
certification testing).
Any or all of the above.
It
> > Yes, I agree it's possible to do better, but what's the incentive for
> > a bottom-feeding vendor of cheap devices to bother?
>
> I hate to say this, but how about legal solutions?
My reading of the tea leaves: either the industry creates its own certification
plan, or the regulators will d
On 3 Nov 2016, at 21.26, Brian E Carpenter wrote:
> Yes, I agree it's possible to do better, but what's the incentive for a
> bottom-feeding vendor
> of cheap devices to bother?
I hate to say this, but how about legal solutions? If you sell e.g. guns that
explode if you use them, you are going
Barbara,
On 04/11/2016 04:00, STARK, BARBARA H wrote:
>>> I could be wrong, but I believe that Dyn was DDoSed by the Mirai
>>> botnet, which propagates by exploiting devices configured with default
>> credentials.
>>> This has nothing to do with outdated firmwares.
>>
>> The problem is that you ca
ddos attack like against Dyn
>> I could be wrong, but I believe that Dyn was DDoSed by the Mirai botnet,
>> which propagates by exploiting devices configured with default credentials.
>> This has nothing to do with outdated firmwares.
> The problem is that you cannot realistically update tho
> >I could be wrong, but I believe that Dyn was DDoSed by the Mirai
> >botnet, which propagates by exploiting devices configured with default
> credentials.
> >This has nothing to do with outdated firmwares.
>
> The problem is that you cannot realistically update those firmwares.
Many companies p
>>> ddos attack like against Dyn
>
>I could be wrong, but I believe that Dyn was DDoSed by the Mirai botnet,
>which propagates by exploiting devices configured with default credentials.
>This has nothing to do with outdated firmwares.
The problem is that you cannot realistically update those firmw
> This started with a need for somewhat accurate system time for
> certificate validation, right? I have to deal with stuff lacking
> a RTC battery. I save system time every now and then in flash.
> During startup, clock jumps forward to RTC when warm start occurs
> (main power was not interrupted)
