Comment Re: "SJW" (Score 1) 398
Shut up, Toby.
His name is Kunte Kinte.
Shut up, Toby.
His name is Kunte Kinte.
I hold out hope that the two of them are getting air time not because they could win, but because they are more interesting than Clinton v. Bush. Plenty of time for that boring crap later.
Vendors cannot be held responsible for stupid (or non-existent) engineering and policy.
Without knowing the GS/contractor divide at OPM, it's hard to say who is ultimately to blame. If OPM gave carte blanche to the contractor, the latter is generally the one at fault. If the government micro managed the contract and ignored suggestions, the blame is back with them.
Jim Webb doesn't strike me as particularly interested in the office.
That Goldwater girl was never liberal enough to want it.
The other difference is that Yahoo and Google have locked down email so that legitimate email isn't getting delivered. Now other providers are following the same rules. When you block a lot of email, it never gets delivered.
There are certain people I just can't mail anymore.
Windows XP prior to SP1 had a very nasty update. Even SP1 had some bugs when it first came out. Vista had a few bad drivers that weren't 64bit clean that caused me total data loss. (File system corrupted)
It has happened in the past. Microsoft has a good track record with recent updates. I'd also point out that as recent as the Windows 8.1 update failed because of my MOUSE DRIVER. Granted, I had a gaming mouse with firmware for profiles and LEDs but still...
That's not true. Script kiddies have to wait for someone to write a tool for them to use to actually exploit it. It takes a few days for these things to get out there in mass.
When an upstream has a security advisory, I have to run around in circles to get the patch out to my users and then they have to run around patching everything. That's just how it works. When you don't get enough information to make a decision, it makes it hard to know if you should risk patching. For some folks, they're in system freeze for a busy time of year or have a lot of other risks by patching something. You really need as much info as possible to make this decision sometimes.
For example, at work we have a vendor who recently told us they had a huge security issue. Anyone on the internet can change a setting and that in turn can change a link to an admin area of our product. The catch is that we never use the admin link it changes. They threatened to drop support of their product for us if we didn't patch immediately. However, we don't use that admin link. Further, the number of users in our org that uses it are on one team of 10 people. A huge risk in general does not mean a huge risk for one org.
The OpenSSL team did the right thing on their end, but there are two dimensions to vulnerabilities, the severity in terms of the software and the number of users impacted. The latter in this case, was small.
Did your credit card "used" credit amount go up. If it's more than 25% of your credit line, it will cause a drop.
This can't be accurate. My boss at the time had an NT4 server running SQL Server that he left on for a year. It only had SP1 installed. No security updates.
It was kind of a nightmare to patch when we finally did. Did I mention it was the billing database and that was back when we didn't have the PCI compliance standards of today.
You never owned an iomega zip drive then. The NT4 kernel would BSOD constantly with an external parallel version of that. I've experienced a BSOD on every OS through Windows 7. In windows 8, it's now a
Windows tends to crash now due to hardware problems. Most BSODs in NT are from bad hardware or bad drivers.
Look at the massive amount of IPs that Amazon and Microsoft use for their cloud solutions. If AWS actually supported IPv6 properly, people could start migrating. Last I checked, Amazon didn't even offer IPv6 as an option for their DNS services.
ISPs are starting to move on IPv6, and now we need the big hosting companies to step up. Today, that's mostly cloud providers.
QA is another option. I think it's the goto for people that are logical and don't actually enjoy writing software. Instead, they get to try to break it.
Today is a good day for information-gathering. Read someone else's mail file.