Miscellaneous Tech News
-
-
@nadnerB said in Miscellaneous Tech News:
Dell h4xed?
https://www.itnews.com.au/news/dell-resets-all-customer-passwords-after-cyber-attack-516224It may be true in Australia, but is it true in America? Huh? Ever think of that?
Pfft, idiot.
-
@tonyshowoff said in Miscellaneous Tech News:
@nadnerB said in Miscellaneous Tech News:
Dell h4xed?
https://www.itnews.com.au/news/dell-resets-all-customer-passwords-after-cyber-attack-516224It may be true in Australia, but is it true in America? Huh? Ever think of that?
Pfft, idiot.
America? Never heard of her.
-
@nadnerB said in Miscellaneous Tech News:
@tonyshowoff said in Miscellaneous Tech News:
@nadnerB said in Miscellaneous Tech News:
Dell h4xed?
https://www.itnews.com.au/news/dell-resets-all-customer-passwords-after-cyber-attack-516224It may be true in Australia, but is it true in America? Huh? Ever think of that?
Pfft, idiot.
America? Never heard of her.
I've never heard of her either. At least not this version. A thread of images from a Japanese illustrated history of America from 1861.
and OMG the comments...
-
@JaredBusch I see nothing inaccurate in those images. George Washingtonsan was Japanese, no duh
-
@NerdyDad said in Miscellaneous Tech News:
This week Amazon announced their new A1 arm64 EC2 Instances powered by their arm64 based Graviton Processors and, with a minor delay, the shiny new Fedora 29 for aarch64 (arm64) is now available to run there too!
Details on getting running on AWS is in this good article on using AWS tools on Fedora article and over all using Fedora on the AWS arm64 EC2 is the same as x86_64.
Now that is pretty exciting. I want to try that out!
-
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
"
