Short of getting advisories from vendors, just putting something on the calendar is probably best.

@dbeato said in Anyone running SonicOS 6.5.0.2-8n?: @dave247 said in Anyone running SonicOS 6.5.0.2-8n?: We run a SonicWall NSA 3600 where I work and I am staring to look into upgrading to the new 6.5 firmware (6.5.0.2-8n). I have heard of some issues with the last two updates, and wanted to get more input if anyone has any to give.. I am not, I am using the 6.2.9 on the production Sonicwalls we have. I would recommend to test it out if possible. Unfortunately I can't realistically test it out. Even if I had an extra, non-production unit, I doubt I could effectively detect issues since production factors would not be present enough to fully test. I suppose I could just always roll back if necessary... but I think I will probably be waiting a few more releases.. that or just move to a different UTM all together..

FFS that is when I was planning to tag all my old threads.

My money on error 1603. Which means nothing but is usually the error in Windows Update logs.

@black3dynamite said in Meltdown Shows Why to Avoid LTS Releases: What makes Red Hat and SUSE exempt compare to CentOS and OpenSUSE leap? Because we are paying for the support? Nothing makes them exempt, they ARE CentOS and Leap, just paid for instead of free. They suffer just the same.

Have not seen any patching issues in the real world yet. Yet....

@wls-itguy said in Windows laptops stuck at 1709.192 update.: What in the #&# Great! BTW, I read a while ago that WSUS was going away? Yet today in my searches for this issue I see that it is indeed still alive and well on 2012 servers? Did I dream that WSUS was going away? It often should go away, but I don't know that MS is taking it away.

@stacksofplates said in Some macOS Updates Cause Foot Bug to Resurface After Patching: I'm assuming this was supposed to be root but, not foot bug. LOL hahha

@jmoore said in Linux vulnerability found - effecting Debian and RedHat: @stacksofplates Oh that is interesting, I didn't know that. Ya it forces it to use the legacy mmap layout which isn't vulnerable. Once you are able to reboot then you should be able to remove it.

@stus Thanks. Was just reading about it here.

Never used this but take a look... http://www.smikar.com/

Not much pity for people not bothering to update.

https://www.theregister.co.uk/2017/04/13/microsoft_kills_support_old_windows_on_new_chips/

My answer to the OP. I mean I am not saying MS is good or bad, or Linux OS's are good or bad. But the OP was just a whiny bitch.

@olivier NP... I know it's isn't within your control.

Security advisories from our July 5th release are online, be sure to be up to date! See https://nextcloud.com/security/advisories/

@aaronstuder said in Moving to a New WSUS server: @BBigford No Problem. Once I realized that the port numbers change, I realized the issue right away. Clients are being seen by the WSUS server now Sweet!

Top Android development frameworks, many of them are cross platform... http://linuxgizmos.com/top-10-open-source-android-app-development-frameworks/

Yeah I read that the same way @Kelly . That's like being paranoid about catching some tropical rain forest virus when you live in the tundra, so you just stay home all day and night.

This one bit me today. Wish I had seen this thread, but I was I. The middle of 3 other things when this user called. It was pure firefighting at that point. Kudos to @TechnicalAngel for googling for me while I vented and leading me to the resolution.

@Dashrender said in What would you use to replace WSUS from SBS: @Shuey said in What would you use to replace WSUS from SBS: @JaredBusch said in What would you use to replace WSUS from SBS: @DustinB3403 said: Ah.... Sorry for the confusion then. Do they have the resources to run another WSUS server and proper licensing? It really is quite a simple solution. PDQ Deply has options for 3rd party app updates etc, but requires annual renewal. Oh, I can easily setup WSUS on one of their existing VMs. Just not really sure I want to with the size overhead for this many users. Hey Jared, sorry if I sound a little lost, but what is the overhead you're referring to? You pretty much only have two options: Deploy a WSUS server and use a GPO (or regedit) to make the workstations talk to it, or you can manually install updates once per month (or per quarter). I would think you could easily deploy a very small WSUS server (either on 2008 or 2012) using WID and about a 60-80gb hard drive. You could even make it one of the guest VMs. When I was supporting Office 2010 and Office 2013, Windows 7 and 8.1 I needed more like 120 GB to hold all of the updates, and monthly had to do the cleanup or I would run out of disk space. Obviously there will be some variables to consider. I was basing my recommendation off our current WSUS setup (over 200 workstations, and 30 servers) vs his environment (8 desktop, 2 laptops and some unnumbered servers). Up until recently when MS changed the way the update cycle works, I cleaned our db every month and we've been doing completely fine with an 80GB hard drive on the server.

Thanks. Off to do some patching....

@nadnerB said: I wonder how many times this has already been exploited? We'll never know. Possibly a lot.

@scottalanmiller said: I just use the console too. Few clicks and you are done. Yup. Backup, Update, go back to sleep. that's my process.