It probably has something to do with letting Rupert Murdoch and his cronies run the country, too. Seriously, he controls about 70% of the media there and Abbott would not be in power now if Murdoch hadn't declared war on the Labor party.
You forgot AppArmor, which is one of the most widely-used on Linux. Of course, I'd much rather have Qubes' isolation mechanisms so that my banking, work and leisure activities (and even my NICs) don't even share the same virtual machine -- My data sets are kept separate and the interfaces between those domains are simple and very strong.
When I am designing for "SECURITY" I want to simplify the critical protocols so that they can be described by a state machine and then implement them in silicon.
It would be interesting to see a Xen hypervisor implemented in silicon, as that is what Amazon EC2 and Qubes OS base their security on. Qubes doesn't even use kernel-based permissions for its single-user desktop model; It gives you the means to control dom0 and everything else resides in VMs.
'Denial' isn't just a river in Egypt.
You're missing the point.
Quadcopters are dangerous
Sure, just like countless other objects. But if the FAA was worried about safety, they'd be expecting the recreational users of them to also be subject to the regulations they're putting on commercial operators using exactly the same 3-pound plastic quadcopter in exactly the same way. A guy checking out his own roof gutters with a consumer-grade quad, and a roofing contractor using exactly the same device in exactly the same way present exactly the same safety risks
Easy. For both the homeowner checking his gutters as well as a airplane pilot flying overhead, self-preservation is a big factor.
OTOH, third parties flying vehicles around other people is an inherently callous (and cowardly) act.
This isn't about safety.
'Denial' isn't just a river in Egypt.
Quadcopters are dangerous, and those are just the toys that don't carry packages across town.
This is a question of public safety being sacrificed to suit Amazon's corporate goals and customers who will pay premiums for faster service.
Actually, no. Eventually you won't be able to go for a swim because the accompanying Canfield Ocean effect is leading to anoxia and eventually copious amounts of hydrogen sulphide gas being spewed from the oceans into the atmosphere....... You won't be able to breathe.
Its like putting those large golden padlock images on e-commerce pages: Over time, people will absorb them as trust indications and then scammers will increase their success rate by draping their spoof pages in these symbols.
A user has to understand what a browser or email client is, and learn to look for trust indicators in the areas that frame the content.
Adding a PGP interface inside a content area is just STUPID.
The real problem that needs solving isn't hacking PGP into web-mail, it's making certificate management user-friendly. And that's not even that hard to do!
I completely agree. I think cert and key management *would* be a lot simpler if operating systems presented keys and certs as first-class objects instead of little scraps of gobbldeygook texts with an empty-page or question-mark icon.
This is a security failing that is hard to overlook for projects with far-flung participants. Any time data is downloaded it could be subjected to MITM attack.
Core git coders appear oblivious to the problem. Even so, how hard can it be to replace SHA1 with SHA256?
Cases in point:
1. The ridiculous FAT long-filename patent
2. The subpixel rendering patent (despite prior art being shown)
3. Outright patent-troll behavior: Refusing to disclose a stack of patents its using to extort for-profit Linux distributors behind closed doors.
If MS comes out of the closet and enumerates #3 and opens a dialoge with the community about them, THEN I will believe their hype about being open-source friendly. Otherwise, they are in the business of growing their Android-derived revenue using submarine tactics.
Also, explain to us why MS shuts out FOSS AV and document formats (the consumer-oriented ones); Not only from their products but from standards-making processes.
Have a nice day, mods!
Cases in point:
1. The ridiculous FAT long-filename patent
2. The subpixel rendering patent (despite prior art being shown)
3. Outright patent-troll behavior: Refusing to disclose a stack of patents its using to extort for-profit Linux distributors behind closed doors.
If MS comes out of the closet and enumerates #3 and opens a dialoge with the community about them, THEN I will believe their hype about being open-source friendly. Otherwise, they are in the business of growing their Android-derived revenue using submarine tactics.
Also, explain to us why MS shuts out FOSS AV and document formats (the consumer-oriented ones); Not only from their products but from standards-making processes.
"Microsoft simply wants to support industry standard formats and not hobbyist formats like Ext4 or OGG Vorbis. You are not going to find Ext4 or OGG Vorbis support from your camcorder either."
So those massive datacentres powered by Linux are running a hobbyist filesystem?
And don't forget there are billions of Android devices that can understand Ext* disk formats.
So only MS gets to embrace and extend; Who would have guessed? Break a single rule in Microsoft's
The irony here is MS are using licenses that are thought to be the most libre as a cover to keep the developer community fenced-in to their platform with patent threats. Re-purpose any of the patented code and.....
Also, I'd like to remind you that MS still enforces at least two very silly patents against FOSS distributors: The FAT filename-length patent and the subpixel-rendering patent (which has prior art). And IIRC there is a raft of patents they are using to threaten Linux distributors which they still won't reveal, so they are still in the business of wielding shadowy threats which I'm told is actually illegal.
MS needs to make good on their past and current patent trolling. If they don't then we have no reason to believe they are doing "open source" in good faith.
I doubt it is trivial to add EXT2/3/4 support to the windows stack. Consider that ZFS has barely moved in linux space, even though it is fully BSD compatible, opensource, and awesome. Apparently it makes more sense to develop BTRFS.
Its trivial to get Windows to recognize a Linux partition and refrain from telling people to format those volumes.
8 Catfish = 1 Octo-puss