Think of the big breaches, which I tracked until about five years ago... In the Zappos breach, hackers broke into their system and stole their database. They didnt guess passwords, just stole them.
When CardSystems Solutions (a payment processor) was hacked and 40 million credit card numbers stolen, it was by SQL Injection. Fust full names, addresses and passwords exposed without any password guessing.
TJX (TJ Maxx, a retailer) lost 45 million credit card records in a hack... by unprotected WiFi and unencrypted records.
Google's AdWords system by surrupticious files being installed. User passwords were stolen.
About ten years ago, Internet Explorer (yeah, I know...) facilitated look-alike sites to steal Hotmail (Microsoft), GMail and Yahoo passwords... but complexity or guessing were not the issue.
When Epsilon Data Management was hacked, it wasn't via guessed passwords, but they were stolen, compromisingcustomer accounts on Citibank, Chase, Target, Walgreen and Best Buy.
LinkedIn, the professional networking site, had six million passwords cracked-and-leaked in June 2012. The process was an attack on the server storage encryption, not on password strength.
The stupid thing was, when Zappos was hacked (again, not via password theft), they then decided to impose stringent password requirements. Amazon doesn't have such stringent requirements, so just for ease I've switched most of the purchases (about four a year) I used to do from Zappos over to Amazon.
I admire your passion, but the world of media doesn't work that way. If the content distributors (Netflix, Amazon, HBO GO/NOW and the also-rans) weren't able to use standardized DRM, they would use... and standardize... on a non-standard platform. One that, being non-standard, would probably be very closed-source and proprietary. And consumers would flock to it Resulting in a huge, unverified surface for exploits and attacks.
This has happened before. Remember Flash?
Channel George Santayana.
I don't think that. For several years I was "randomly" picked for a thorough search every time I boarded a flight back from Europe... which was every other month. I'm blue-eyed, white, clean-shaven, born in the U.S. and was usually in a nice business suit. We used to joke that it was because it's safer to search someone like me, as you know you won't find anything and you won't be accused of bias.
You are making an accusation based on a single incident. It could have been an agent responding to Sidd being, e.g., belligerent, or some other country on his passport, or even just misinterpreting a recent memo.
VeraCrypt/True were already secure -enough-. Cracking through the holes is usually more effort than local law enforcement, your boss or the local mob will care about. If you're on the radar of worse people, they can toss you in jail or threaten your family. So while I consider better security a good thing when it doesn't increase cost or inconvenience, it's not really an essential move forward.
The bigger problem is common passwords, leaving the volume open, having open drives automatically backed up to "the cloud", emailing documents... things these security code fixes cannot address. We don't hear often that the Feds have used a security hole to extract data from a user's system.
Umm... no. The real number is about 25%. Real world tests. But you have to do REAL world tests.
A few years ago I was at the VP8 conference. Google was touting how much bandwidth VP8 could save over H.264. They said they could give identical quality with a 5Mbps VP8 1080p stream as with a 10Mbps H.264 stream. Well, yes... you get about the same quality with a 4Mbps H.264 stream at 1080p as with the 10Mbps. But they did freeze when asked if they would pit the quality of VP8 doing a 1.2Mbps stream against H.264 doing a 2.4Mbps stream.
You've got to know the context. For our tested real world content, same quality, against optimized H.264, it's about 25%, pretty consistently.
For a company! The average
I've seen a lot of style wars - tabs vs spaces, braces starting same line vs next line vs omitted when possible, commented enums required (especially by European companies using StyleCop), etc.
All of that is unnecessary from a compiler perspective. But the style you are accustomed to aids your efficiency and effectiveness. Code doesn't care if it's consistently indented, but finding that unbalanced loop is much easier with it.
Use what makes you personally across all your development, and more importantly your entire team, faster and better.
I'm not sure, but the image at http://www.nullisland.com/geog... looks a lot like Aogashima Island in Japan.
There is so much wrong with that as to be comical.
When do you ever hear about insecure passwords being compromised? That doesn't happen. They get leaked. Constantly. But not guessed, not when they can be leaked or stolen.
So how does a super-ultra-secure password help?
And then we have this odd bit of math, that 18% of the >51 age range had compromised accounts, while less than double that, 35%, of the youngest range had. Probably, but unclear because the report requires providing PII, while having four times more accounts. I'd certainly bet that the 18-to-34 age bracket has more than double the account count of the compu-geysers. (I say as someone just squeaking below that bar.)
Which would imply that, mathematically, insecure passwords are more secure. Go figure.
The on-chip FM radio requires a WIRED headset. Not bluetooth, not using the phone speaker or earpiece. The headset lead is used as an antenna. Without it, the radio doesn't work. Generally won't even turn on, just gives a warning.
So it won't work for most users. And was probably costing too much in support calls about why it wasn't working.
"For everyone who is going to respond to this in a "Fuck you, I can say and do whatever I want" fashion, can you please explain why it is so difficult to refrain from inappropriate jokes in an office environment?"
Did you even READ the OP? This wasn't about an office environment. And, if you really have been around that long, you know that the definition of "appropriate" changed a lot in 25 years. You could claim that we should have been this sensitive, this advanced, 25 years ago, but that was then and, for then, it was pretty advanced. More so than 25 years before that.
All of which makes you sound a bit immature.
That's not entirely fair. That's still a pretty recent version - if you purchase from Amazon or NewEgg you have a good bet of getting it even on an x14 model, and certainly will get that or older on any other model - and there's no "Automatic Update" mechanism on Synology systems. Plus they're essentially storage appliances; users aren't expected to log into and manage them frequently. And the feature that seems to put people at risk is a selling point of the device.
I'm not bashing Synology; I have two Syns running in my system (both current, both firewalled, neither has the rumored susceptible port open, neither infected.) But you're not spending enough time around regular people if you think people expect to be logging into the admin screen of their external hard drive - or their fridge, toaster oven or coffee maker - frequently to check for updates.
Money is better than poverty, if only for financial reasons.