Miscellaneous Tech News
-
End of Life for Fedora 27
https://fedoramagazine.org/fedora-27-end-of-life/ -
-
@dbeato said in Miscellaneous Tech News:
https://weather.com/news/news/2018-11-30-anchorage-alaska-earthquake-impacts
Wow, that's a big one.
-
@dbeato said in Miscellaneous Tech News:
https://weather.com/news/news/2018-11-30-anchorage-alaska-earthquake-impacts
Wyze cam for the first video heh.
-
@JaredBusch said in Miscellaneous Tech News:
@dbeato said in Miscellaneous Tech News:
https://weather.com/news/news/2018-11-30-anchorage-alaska-earthquake-impacts
Wyze cam for the first video heh.
Is there a logo somewhere? I can't see the logo on my phone if there is one.
-
@DustinB3403 said in Miscellaneous Tech News:
@JaredBusch said in Miscellaneous Tech News:
@dbeato said in Miscellaneous Tech News:
https://weather.com/news/news/2018-11-30-anchorage-alaska-earthquake-impacts
Wyze cam for the first video heh.
Is there a logo somewhere? I can't see the logo on my phone if there is one.
They updated the video. It is 30 seconds in now.
-
@JaredBusch said in Miscellaneous Tech News:
@DustinB3403 said in Miscellaneous Tech News:
@JaredBusch said in Miscellaneous Tech News:
@dbeato said in Miscellaneous Tech News:
https://weather.com/news/news/2018-11-30-anchorage-alaska-earthquake-impacts
Wyze cam for the first video heh.
Is there a logo somewhere? I can't see the logo on my phone if there is one.
They updated the video. It is 30 seconds in now.
Eh.
-
@JaredBusch said in Miscellaneous Tech News:
@dbeato said in Miscellaneous Tech News:
https://weather.com/news/news/2018-11-30-anchorage-alaska-earthquake-impacts
Wyze cam for the first video heh.
Damn, Wyze cam was working its ass off tracking?
-
-
@dbeato said in Miscellaneous Tech News:
But unlike Lenovo, they attempted to patch it. They failed, but at least they tried.
Also, they didn’t deny anything, or actually inject anything.
The end result was bad, but not with intent.
-
FYI - I ran into this last week -
When starting Veeam Backup and Replication console, you get an error "Failed to check certificate expiration date"
Fix is to create a new certificate.
-
@wrx7m said in Miscellaneous Tech News:
FYI - I ran into this last week -
When starting Veeam Backup and Replication console, you get an error "Failed to check certificate expiration date"
Fix is to create a new certificate.
Recent email from Veeam states that they are going to implement a 10-year certificate in Update 4.
-
@NerdyDad said in Miscellaneous Tech News:
@wrx7m said in Miscellaneous Tech News:
FYI - I ran into this last week -
When starting Veeam Backup and Replication console, you get an error "Failed to check certificate expiration date"
Fix is to create a new certificate.
Recent email from Veeam states that they are going to implement a 10-year certificate in Update 4.
The first bug is very annoying, because it will impact everyone who's using the default self-signed certificates, which is unfortunately the majority. As a reminder, we use those certificates to implement secure communication between backup infrastructure components, as well as with managed backup agents. And while we do provide the ability to select or import your own certificate, most don't worry about this and just keep the default certificate that is automatically generated when you install Veeam Backup & Replication. This certificate is set to expire in 1 year from its creation date, and due to some bugs you will see artifacts of its expiration 1 year after your Update 3 installation date. Which means, this will hit many of you in the next few weeks, and may make it a not very merry Christmas, unless you act now!
Assuming you have Update 3a installed, first thing you will see at 11 months after Update 3 installation time will be the "Failed to check certificate expiration date" error message upon opening the backup console. The UI is trying to tell you that the certificate is about to expire, but the logic of this falls through to the universal message for all unhandled exceptions (which is why it does not make much sense). If you ignore this message, everything will continue to work fine for another month, after which the agent management functionality, as well as all granular restores will start failing. Luckily, the issue is super easy to fix by simply generating a new certificate, which takes just a few clicks. So don't wait, and do it at your earliest convenience. Needless to say, we've fixed the related bugs in the Update 4 (and also bumped the self-signed certificate expiration date to 10 years). Here's the official Veeam support KB article for this issue > KB2806
-
@NerdyDad Yes sir. I saw that last night.
They didn't have that KB article when I experienced the issue. I saw on their forums that someone had been advised by tech support to create a new cert. Then I saw the email and the explanation behind what had happened. It all makes sense.Per the email update:
"The first bug is very annoying, because it will impact everyone who's using the default self-signed certificates, which is unfortunately the majority. As a reminder, we use those certificates to implement secure communication between backup infrastructure components, as well as with managed backup agents. And while we do provide the ability to select or import your own certificate, most don't worry about this and just keep the default certificate that is automatically generated when you install Veeam Backup & Replication. This certificate is set to expire in 1 year from its creation date, and due to some bugs you will see artifacts of its expiration 1 year after your Update 3 installation date. Which means, this will hit many of you in the next few weeks, and may make it a not very merry Christmas, unless you act now!
Assuming you have Update 3a installed, first thing you will see at 11 months after Update 3 installation time will be the "Failed to check certificate expiration date" error message upon opening the backup console. The UI is trying to tell you that the certificate is about to expire, but the logic of this falls through to the universal message for all unhandled exceptions (which is why it does not make much sense). If you ignore this message, everything will continue to work fine for another month, after which the agent management functionality, as well as all granular restores will start failing. Luckily, the issue is super easy to fix by simply generating a new certificate, which takes just a few clicks. So don't wait, and do it at your earliest convenience. Needless to say, we've fixed the related bugs in the Update 4 (and also bumped the self-signed certificate expiration date to 10 years). Here's the official Veeam support KB article for this issue > KB2806
" -
@NerdyDad LOL - You beat me to posting the the email excerpt. I had to reboot the server to get agent for windows to backup after changing the cert. Just figured that out after a week of troubleshooting the agent from the client side.
-
Google expands eSIM support on the Pixel 3 to Sprint and several international carriers
Google became the first smartphone company to support built-in eSIMs with its Project Fi (now Google Fi) network last year. Now, it’s expanding that even further with the announcement of several new carriers around the world that will support the feature.
In addition to Google Fi, Google is adding support for Sprint in the US, EE in the UK, Airtel and Reliance Jio in India, and Truphone and Gigsky in various other countries over the next few months. In Germany, Deutsche Telekom and Vodafone will actually join Fi in offering the option to buy a Pixel 3 with an eSIM for those carriers sometime “soon.”
-
Linux Mint 19 Beta 1
https://www.omgubuntu.co.uk/2018/12/linux-mint-19-1-beta-download -
-
Hackers breach Quora.com and steal password data for 100 million users
Other stolen personal data includes names, email addresses, and direct messages.
Brace yourself for yet another massive data breach. Quora.com, a site where people ask and answer questions on a range of topics, said hackers breached its computer network and accessed a variety of potentially sensitive personal data for about 100 million users.
-
iOS apps used Touch ID feature to trick users into paying hefty fees
Apple gives two scam apps the boot after they come to light.
The offending “Fitness Balance app” and “Calories Tracker app” promised to calculate body mass index, monitor calorie intake, and provide other health-related services. With no advanced warning, according to Reddit posts here and here, the apps charged users fees of $99.99, $119, or 139 Euros, depending on the country of the user. Users who had a credit or debit card connected to their Apple account were immediately billed.
The scam worked by displaying a message as soon as the app was opened. It told users to scan their fingerprint to view a calorie tracker or receive another personal service. When users complied, the apps displayed a popup window that said they had been charged a fee. Less than two seconds later, the popup disappeared, but by then it was too late for many users. Anyone with a card linked to their Apple account was already charged.
“So what it does is ask you to keep your finger at the fingerprint, and then the popup for paying for the app shows up,” a Reddit user with the handle kristikoroveshi94 reported. “Since you have already your finger there, the payment continues. And damn what a price this shitty app has. Luckily I don’t have a linked card or paying account.”
