by E.I.T. Author | Jan 3, 2018 | Blog, Computers, programming, Security
This is huge…if you have ever followed updates you know that the kernel often has holes plugged, but apparently this vulnerability is huge. Clearly to properly fix a hardware vulnerability properly requires a hardware upgrade. But operating system updates can address it. But the kernel is addressed so frequently that this type of fix will significantly slow down all computers. This new vulnerability, which is being kept hush-hush until it’s all been patched, affects ALL computers and laptops with Intel processors, whether they are Windows, Mac, or Linux based. Yes, that’s right…since Apple always has what has previously been the best hardware, they are also affected on this one. This vulnerability affects all Intel-based PC’s going back 10 years. I’ve read in some places that some newest processors may not be as affected “quite” as much, i.e. the slowdown won’t be as dramatic, but they are all affected. This is a sad day. I know I’m sad. I can’t afford to upgrade hardware, I just built my current rig about a year ago. Upgrading a processor usually requires a new motherboard also, unless you just got one maybe. Anyway, if you look on the web, you will see many articles on this subject, all them current news. I’ll give you some for some reading if you are concerned. Even though the specifics of the vulnerability won’t be released until the patch is out, they have said that it’s a memory leak…so basically it would give hackers the ability to read data, but not to write, delete, or modify it. (whatever comfort that may be) …I’m wondering if simple encryption helps in this case. ??? What say you?
Tech Republic
PC World
Tech Crunch
PC Word gets Intel’s Response to the news
by E.I.T. Author | Dec 30, 2017 | general
How lack are you in your password creation? If you have one of these worst passwords ever, a hacker can gain access in minutes. (like 1 or 2). And if you even use any word that is found in a common dictionary, a computer program (called a brute force hacker) can go through the entire dictionary in a very short time, and still gain access.
For a password to be secure, it should have capital letters (not just the 1st one) lower case, numbers, and if permitted, characters, and it should be at least 16 characters long to be secure. It’s not that hard, as the Chrome browser can remember all your passwords for you, and if you log in to your google account on any Chrome browser, your passwords will be there for you. (just don’t forget to log off when you’re done) …that way, the only hard one you have ot remember and keep secure, is your Google password.
Ready for the list? Here’s the worst of the bunch: (if you have one, you are dead in the water!)
1. 123456
2. password
3. 12345678
4. qwerty
5. 12345
6. 123456789
7. letmein
8. 1234567
9. football
10. iloveyou
11. admin
12. welcome
13. monkey
14. login
15. abc123
16. starwars
17. 123123
18. dragon
19. passw0rd
20. master
Remember, make sure your password can’t be located in a Dictionary! 🙂
by E.I.T. Author | Dec 21, 2017 | Blog, Computers, Email, general, internet stuff, Security, viruses, Web Development, wordpress
The office will be closed from December 22nd until Jan 2nd, although I could be available as early as December 30th. Leaving town for Christmas. Although ALL remote services will still be available. I’m just not taking any jobs that require me “physically” being there, or any equipment/laptop drop-offs. I will however have a computer with me, and will answer all emails and texts, and will be able to perform any remote services, like Windows issues, Website issues, etc. …any of the things I would normally do remotely. So please don’t hesitate to call just because the hours say closed, there was no field to add an explanation on Yelp or Facebook.
FROM EVERYTHING I.T.!
by E.I.T. Author | Dec 2, 2017 | Blog, Computers, internet stuff, programming, Safari, Web Development
If you have a website, or you are involved in web development, you know that things are constantly changing, right? Do you remember not too long ago before HTML 5 and CSS 3 came out and brought along all the wonderful responsive website technology that made things so nice for cell phones and tablets? Do you remember that once upon a time, we had to have a .mobile TLD (top level domain) for your URL so you could have an entire separate website for cell phones? And then came along HTML5 and CSS3 and all this wonderful new stuff that removed the scroll bar from the bottom of the webpage, and now things just AUTOMATICALLY resize depending on screen size? It seems like ages ago, but really it wasn’t that many years ago. Things change rapidly when it comes to internet technology. Sometimes, for those of us who work in it, it’s difficult to keep up with.
Anyway, today I have some information about the WebKit engine. WebKit engine is the technology used for Safari browsers, and the Kindle browser. (why can’t they just use the same HTML as everyone else, right?) Anyway, there are some new changes that have to do how AUTOPLAY on videos works. So if you have video on your website, you are probably going to want to study this issue. I have read that the changes that Apple made, Chrome will also be making in early 2018. The main thing is that AUDIO will not autoplay any more. If you want sound, you have to have controls enabled. Only videos without sound will autoplay. If you want to read about the OSX and iOS Webkit changes, you can read about them here: https://webkit.org/blog/7734/auto-play-policy-changes-for-macos/
by E.I.T. Author | Nov 29, 2017 | general
UPGRADE to WordPress 4.9.1
This update is a Security and Maintenance release, fixing 11 bugs and 4 security holes, so go get it now. If you want to read what the specific changes are, read the changlog: https://make.wordpress.org/core/2017/11/28/wordpress-4-9-1-scheduled-for-november-29th/ basically, this is the list:
- #42573: File caching affecting users’ ability to use the plugin and theme file editors.
- #42574: MediaElement upgrade causing JS errors when certain languages are in use.
- #42579: Incorrect logic in
extract_from_markers()
.
- #42454: Unable to translate Codex URL in theme editor.
- #42609: Theme editor cannot edit files when running on a Windows server.
- #42628:
flatten_dirlist()
doesn’t play nice with folders with numeric names.
- #42634:
DB_HOST
socket paths with colons not parsed correctly.
- #42641: On multisite upgrade the
wp_blog_versions
table doesn’t get updated
- #42673: Themes page throws console error when there is only one installed theme.
In addition, one fix for a bug introduced in WordPress 4.7 will be included in 4.9.1:
- #42242:
lang
attribute in the admin area doesn’t reflect a user’s language setting.
Recent Comments