go to sections menu

Making sure we give out accurate information from blog The Technology blog and podcast

This is for the technology blog and podcast Commentary, articles, and podcasts

header picture for Ingegno theme

You are here: accessibility newsand issues > Making sure we give out accurate information

Go to Homepage, contents or to navigation menu

Making sure we give out accurate information

Hello folks, I hope you’re enjoying the blog, and I’ll be releasing a podcast real soon, it just needs to be finalized. Today, while I have thought about this post, I’m going to be upfront, and as accurate as possible.

Remember in January when we published Urgent issue with AI squared access technology and the page in question had support hours over the weekend to help people through the issue they said was urgent and that things were compromised? Well, it isn’t that bad to begin with, according to what I found out today.

My actual call to the VFO group was totally unrelated to this, but when the gentleman said to go to the certificate fix page, I told him why I was calling and that I had installed Window-Eyes to this PC already but the issue i was calling about needed a full installation zip file.

He told me that the people who needed to help me were gone, and I thanked him, I happened to ask him about the whole certificate fix issue we encountered since he braught it up.

The gentleman said there was never a compromise at all. They had published it was compromised, but the cert in question was only expired, never compromised. I asked why they put it was compromised, because that means things more serious, and he said it was simply mislabeled.

When enquiring on whether they were to fix it, he indicated they wouldn’t because it was a long time ago.

If I was running the page, I would have personally changed it, and released a new press release indicating this.

With the amount of breaches that we have on a monthly basis, it is very important that companies get as much information out there, and if it changes, update it.

I’ll release an article I read via Krebs that actually impressed me, and I’ll talk about that more in debth, as it deals with a particular breach and links to others. I’m surprised that AI Squared did not update this page to simply state that it was expiring, and made it sound like something extreme was going on when it was just an expired cert which was expiring on the date mentioned, and they were patching everyone before it expired.

If the certificate was truly compromised, we would have to patch immediately, and the certificate would be immediately revoked. If we were running the software, we’d be OK, but if we rebooted, we could be in trouble.

AI Squared, please make sure you put the accurate information next time, so that people are not confused like I was. I didn’t think it was compromised, and E-mails asking whether it was, was told to look at the Cert page they published. That page seemed to not make me pleased since the deadline was a week or so away, but yet, compromised certs are revoked immediately upon discovery if I have been paying to Security Now’s teachings. Bad move, AI Squared, please learn from this next time.

I was told the cert is good for awhile yet, so there should not be a problem for at least 20 years.

Thanks for reading, and make it a great day.

Informazioni sull'articolo

Making sure we give out accurate information was released on February 10, 2017 at 7:00 pm by tech in accessibility newsand issues.
Last modified: February 10, 2017.

Comments (0)

No comments yet.

Leave a comment

You must be logged in to post a comment.

go to sections menu

navigation menu

go to sections menu