Spammers are despicable, and even more despicable for using Coronavirus scare to their advantage.
They misspelled “COVID-19” as “CONVID-19”.
Now pointlessly enhanced with AI
Spammers are despicable, and even more despicable for using Coronavirus scare to their advantage.
They misspelled “COVID-19” as “CONVID-19”.
The previously reported bug that caused a login loop for Google-hosted G-Suite accounts has been fixed, presumably on the server side.
The bug was first introduced in macOS 10.14.4 beta. Originally the bug affects any Google accounts with Two-Factor-Authentication (2FA) turned on; Gmail and G-Suite altogether. When macOS 10.14.4 was released, only G-Suite accounts with 2FA were affected. iOS 12.2 was also affected by this bug.
We checked on Saturday morning, March 30, 2019, and found out that the issue was fixed. Assuming that it was fixed on the server side by Google.
A lot of businesses and educational institutions are using G-Suite.
On Thursday evening, T-Mobile sent messages to their customers regarding a security incident that might have exposed customers’ informations.
On August 20, our cyber-security team discovered and shut down an unauthorized access to certain information, including yours, and we promptly reported it to authorities. None of your financial data (including credit card information) or social security numbers were involved, and no passwords were compromised. However, you should know that some of your personal information may have been exposed, which may have included one or more of the following: name, billing zip code, phone number, email address, account number and account type (prepaid or postpaid).
At this point we do not know which information was taken. Just to err on the side of caution, T-Mobile customer should check their account and add/update Customer PIN/Passcode.
According to firstnameatappledotcom, iOS 11.2.5 is ready and might be released as soon as Tuesday, January 23, 2018.
The update also includes the fix to address the crash caused by specially crafted malicious text that can cause iOS device to freeze.
January 4, 2018
Parking is hard, apparently.
Another day goes by and my colleague and I are still talking about “Meltdown and Spectre” exploits.
January 3, 2018
Some one at the office reminded me that the candy bucket is almost empty. In the mean time, I’ve been busy following the Meltdown and Spectre news. My colleague and I have been talking about this subject since we got together after work.
If you don’t have the time and patience to read the details, you can get a summary from Ars Technica.
P.S.
For some reasons I thought about James Bond’s SPECTRE when I first read the news.
January 2, 2018.
Back to work after a few days off; New Year’s Day and whatnot.
What a year to start with some big computing news, which is not a good one. Tip of the hat to my colleague for forwarding me the article.
From the original article:
tl;dr: there is presently an embargoed security bug impacting apparently all contemporary CPU architectures that implement virtual memory, requiring hardware changes to fully resolve. Urgent development of a software mitigation is being done in the open and recently landed in the Linux kernel, and a similar mitigation began appearing in NT kernels in November. In the worst case the software fix causes huge slowdowns in typical workloads. There are hints the attack impacts common virtualization environments including Amazon EC2 and Google Compute Engine, and additional hints the exact attack may involve a new variant of Rowhammer.
Yikes!