Microsoft have announced a “pricing realignment” in October intended to “highlight the benefits of our pricing for a cloud-first world”. We think this means continuing the squeeze on those resisting the move to the cloud! Unfortunately we will see 10% increase in the price of Office and various on-premises editions. Get your upgrades in early!
Just a reminder that from October 2018 Microsoft will be blocking weak security traffic. Your systems need to have TLS 1.2 or above enabled or you will no longer be able to access your Office 365 services online.
If you use any of these versions start planning your upgrade NOW!
- Android 4.3 and earlier versions
- Firefox version 5.0 and earlier versions
- Internet Explorer 8-10 on Windows 7 and earlier versions
- Internet Explorer 10 on Win Phone 8.0
- Safari 6.0.4/OS X10.8.4 and earlier versions
There may be others so do check carefully.
Once all the dust has settled we will be asking all our clients to sign our current terms and conditions as a matter of good form. Some of you have been clients for 20+ years from the days when paper was a thing so it is due a formal refresh but right now is not the time!
Twitter have recommended a password change for 330m users because they inadvertently logged them in plain text. Full disclosure is great but it would be better not to make basic errors like this!
LIS recommends you change twitter passwords and remind all staff why passwords should not be used across multiple services.
The twitter email reads like this:
When you set a password for your Twitter account, we use technology that masks it so no one at the company can see it. We recently identified a bug that stored passwords unmasked in an internal log. We have fixed the bug, and our investigation shows no indication of breach or misuse by anyone.
Out of an abundance of caution, we ask that you consider changing your password on all services where you’ve used this password. You can change your Twitter password anytime by going to the password settings page.
About The Bug
We mask passwords through a process called hashing using a function known as bcrypt, which replaces the actual password with a random set of numbers and letters that are stored in Twitter’s system. This allows our systems to validate your account credentials without revealing your password. This is an industry standard.
Due to a bug, passwords were written to an internal log before completing the hashing process. We found this error ourselves, removed the passwords, and are implementing plans to prevent this bug from happening again.
Tips on Account Security
Again, although we have no reason to believe password information ever left Twitter’s systems or was misused by anyone, there are a few steps you can take to help us keep your account safe:
1. Change your password on Twitter and on any other service where you may have used the same password.
2. Use a strong password that you don’t reuse on other services.
3. Enable login verification, also known as two factor authentication. This is the single best action you can take to increase your account security.
4. Use a password manager to make sure you’re using strong, unique passwords everywhere.
We are very sorry this happened. We recognize and appreciate the trust you place in us, and are committed to earning that trust every day.