These EULAs are quite long, but often times they can be skimmed. Generally, I look for any arbitration clauses, warranty disclaimers, use restrictions, claims of ownership, data collection policies, and any big scary sections in all caps. More often than not, the rest is pretty standard, such as sections about export controls, copyright notices, and notes regarding the TOS.
Many pieces of software and hardware used in Healthcare are required to pass FDA certification, especially in areas like radiology. Often times, these vendors report that because they are certified on a certain patch level, these systems cannot be patched without losing that certification. Do you see any solutions to the current state of industry-specific software's seeming lack of quality, updates and security?
One needs to balance the needs of the many vs. the needs of the few or the one. You cannot take the skydiver at face value, as you have not taken the emotional state of the skydiver into account, or you have weighed each stakeholder's emotional needs equally. Perhaps the potential skydiver wanted nothing more than to skydive once in his/her life. To deprive the skydiver of this could potentially send them into a depressive state, and they may potentially blame their friends/loved ones to the point of resentment. There are admittedly many assumptions being made in this example, but I wanted to counter your counterpoint. People are certainly not islands, but one's consciousness does not extend beyond one's self. One also cannot underestimate the emotional needs of an individual person.
Having said that, a person becoming depressed because they can't skydive probably has other more serious issues...
Wouldn't that be an issue with anything using AD authentication? I thought Kerberos required the client's time to be within five minutes of the authentication server.
I don't think innovation is dead at Microsoft. I simply think they have trouble bringing marketable innovations to market. I personally would love to see everything in Microsoft's R&D department.
They probably already have some form of Wifi along their side of the DMZ, though not necessarily 200m high towers with directional antennae. I doubt any but the highest ranking NK officers have anything resembling a mobile phone, and those that do would not connect to an outside Wifi network for fear of being sent to the gulag. The open internet is reserved for those closest to the few in power in Pyongyang, or at least from what I have read. Kim Jong-un needs his entertainment, right?
The registry system already exists, so the bulk associated with it can't be trimmed. The Registry editor only takes 10K on Windows 7; I can't see it taking much more on Windows.
Once again, the DirectX framework already exists and I doubt the diagnostic tools take much more space than the framework itself.
Just looking at my space analyzer on Windows 7*, the things taking up the most space are the winsxs folders (which hold a million different library versions and probably is not that large on Windows RT as it doesn't have legacy support), the Installer cache, assembly (probably.NET), System32 (drivers, registry, etc), SysWOW64 (probably doesn't exist on WinRT, so [citation needed]), the Microsoft.NET folder, Fonts, and Help. I'd imagine IE also takes a huge chunk, but that lives elsewhere. In fact, I wouldn't be surprised if.NET (after things are compiled and optimized, not the installer packages) took most of the space on WinRT outside of Microsoft Office. Since that's a foundation of the "Not Metro" application stack, there's no reducing space there.
A consumer can and definitely should if they're using free antivirus. A business with more than 10 PCs cannot. It's against the EULA. They're supposed to get Forefront.
Not the apps I need. What about a virtual machine test environment on a shoestring budget? I don't want to have to boot up my old Inefficient PowerEdge up everytime I need a playground, nor do I wish to purchase compute time from The Cloud®. I just need my x86 PC to boot up some low-footprint x86 VMs. I can't really run those on a tablet (yet). I'm no luddite, either; I look forward to the day where my superpowered mobile device can dock into my desktop environment for some hardcore work. It must be said, however, that larger machines will always necessarily be able to provide greater complexity (and theoretically, compute power) than a mobile device, at least until either some physical barrier is reached, or a breakthrough that increases compute power without increasing IC complexity.
You're absolutely right, and I definitely lean toward a hardened licensing process. I also support higher fines/penalties. Unfortunately, these will not realistically happen.
I agree that there's a huge lack of decent responsible drivers on the road. Unfortunately, I can't help but feel like this is the wrong approach. Instead of fixing the drivers and punishing the ones who don't improve, this simply enables those who can't drive well to stay on the road. I will admit that I'm heavily biased, and an idealist, so my opinions on this matter should be taken with a grain of salt.
That's probably what the SAN vendor charged them for the additional space on their EM3Pellent VDataBlackHole SuperSAN that's guaranteed* to meet HIPAA requirements.
*Don't call 'em if you lose data. It's not their fault. That installer guy totally didn't mean to jump-rope with that FC cable. Totally.
The medical device vendor sets up the "Windows Firewall" more often than not. Not IT. And yes, I'm talking about the OS's built-in firewall on the (often times) Windows XP PC embedded in the device. We're not even talking XPe here, but full-blown Windows XP.
It admittedly took me a while to find that setting as I mistakenly assumed it would be in the settings app, as opposed to a setting with the Play store itself. I clearly was not thinking that day.
I've heard conflicting statements on updates and FDA certifications. Some vendors say that you can't patch due to having to recertify with the FDA. Other times, I've dealt with vendors who will advise you to patch, but will provide a patch certification list to use; a list that's unfortunately constantly behind.
While this should be true, these devices are increasingly being connected to networks to offer integration with EHR/HIS for polling information, and especially in radiology, where images are being sent digitally to PACS. These machines often stay unpatched, yet get connected to the network for transfers. It's important to maintain a separate "medical device" network, but this only goes so far, especially when vulnerabilities bypass the Windows firewall on the medical device, allowing some infected PC/device/server to broadcast worms all over the place.
5) I'd expect an auto-driver system to be seperate from any other computing devices in the car, and connected to the internet or any other vector for hacking. I'd expect them to be as immune to hacking as an auto-pilot system in a plane.
While you'd expect it to be separate, the track record for the security of vehicle electronics is not good at the moment. Unless there's some regulation on the matter (be it government mandated or industry self-regulated), the bean counters may not see the benefit of doing so until Consumer Reports does some exposé on the matter and everybody starts to panic over it.
Slashdot Mirror
These EULAs are quite long, but often times they can be skimmed. Generally, I look for any arbitration clauses, warranty disclaimers, use restrictions, claims of ownership, data collection policies, and any big scary sections in all caps. More often than not, the rest is pretty standard, such as sections about export controls, copyright notices, and notes regarding the TOS.
Many pieces of software and hardware used in Healthcare are required to pass FDA certification, especially in areas like radiology. Often times, these vendors report that because they are certified on a certain patch level, these systems cannot be patched without losing that certification. Do you see any solutions to the current state of industry-specific software's seeming lack of quality, updates and security?
I don't know why, but I had to laugh at Indian Business Machines. It has the same ring to it as a tv from Somy or Samfung.
I can do the last part with our MDM software from a leading vendor®. Partial wipes work very well on Android and iOS devices.
One needs to balance the needs of the many vs. the needs of the few or the one. You cannot take the skydiver at face value, as you have not taken the emotional state of the skydiver into account, or you have weighed each stakeholder's emotional needs equally. Perhaps the potential skydiver wanted nothing more than to skydive once in his/her life. To deprive the skydiver of this could potentially send them into a depressive state, and they may potentially blame their friends/loved ones to the point of resentment. There are admittedly many assumptions being made in this example, but I wanted to counter your counterpoint. People are certainly not islands, but one's consciousness does not extend beyond one's self. One also cannot underestimate the emotional needs of an individual person. Having said that, a person becoming depressed because they can't skydive probably has other more serious issues...
No, but I do believe it's the default authentication method for Windows systems.
Wouldn't that be an issue with anything using AD authentication? I thought Kerberos required the client's time to be within five minutes of the authentication server.
That seems like a project that will take longer than a month. Full disk encryption on a large scale is a PITA.
I don't think innovation is dead at Microsoft. I simply think they have trouble bringing marketable innovations to market. I personally would love to see everything in Microsoft's R&D department.
It probably would violate some status quo and the NK would feel compelled to retaliate in some way, shape or form.
They probably already have some form of Wifi along their side of the DMZ, though not necessarily 200m high towers with directional antennae. I doubt any but the highest ranking NK officers have anything resembling a mobile phone, and those that do would not connect to an outside Wifi network for fear of being sent to the gulag. The open internet is reserved for those closest to the few in power in Pyongyang, or at least from what I have read. Kim Jong-un needs his entertainment, right?
The registry system already exists, so the bulk associated with it can't be trimmed. The Registry editor only takes 10K on Windows 7; I can't see it taking much more on Windows. Once again, the DirectX framework already exists and I doubt the diagnostic tools take much more space than the framework itself. Just looking at my space analyzer on Windows 7*, the things taking up the most space are the winsxs folders (which hold a million different library versions and probably is not that large on Windows RT as it doesn't have legacy support), the Installer cache, assembly (probably .NET), System32 (drivers, registry, etc), SysWOW64 (probably doesn't exist on WinRT, so [citation needed]), the Microsoft.NET folder, Fonts, and Help. I'd imagine IE also takes a huge chunk, but that lives elsewhere. In fact, I wouldn't be surprised if .NET (after things are compiled and optimized, not the installer packages) took most of the space on WinRT outside of Microsoft Office. Since that's a foundation of the "Not Metro" application stack, there's no reducing space there.
A consumer can and definitely should if they're using free antivirus. A business with more than 10 PCs cannot. It's against the EULA. They're supposed to get Forefront.
Not the apps I need. What about a virtual machine test environment on a shoestring budget? I don't want to have to boot up my old Inefficient PowerEdge up everytime I need a playground, nor do I wish to purchase compute time from The Cloud®. I just need my x86 PC to boot up some low-footprint x86 VMs. I can't really run those on a tablet (yet). I'm no luddite, either; I look forward to the day where my superpowered mobile device can dock into my desktop environment for some hardcore work. It must be said, however, that larger machines will always necessarily be able to provide greater complexity (and theoretically, compute power) than a mobile device, at least until either some physical barrier is reached, or a breakthrough that increases compute power without increasing IC complexity.
You're absolutely right, and I definitely lean toward a hardened licensing process. I also support higher fines/penalties. Unfortunately, these will not realistically happen.
I agree that there's a huge lack of decent responsible drivers on the road. Unfortunately, I can't help but feel like this is the wrong approach. Instead of fixing the drivers and punishing the ones who don't improve, this simply enables those who can't drive well to stay on the road. I will admit that I'm heavily biased, and an idealist, so my opinions on this matter should be taken with a grain of salt.
That's probably what the SAN vendor charged them for the additional space on their EM3Pellent VDataBlackHole SuperSAN that's guaranteed* to meet HIPAA requirements. *Don't call 'em if you lose data. It's not their fault. That installer guy totally didn't mean to jump-rope with that FC cable. Totally.
The medical device vendor sets up the "Windows Firewall" more often than not. Not IT. And yes, I'm talking about the OS's built-in firewall on the (often times) Windows XP PC embedded in the device. We're not even talking XPe here, but full-blown Windows XP.
It admittedly took me a while to find that setting as I mistakenly assumed it would be in the settings app, as opposed to a setting with the Play store itself. I clearly was not thinking that day.
I've heard conflicting statements on updates and FDA certifications. Some vendors say that you can't patch due to having to recertify with the FDA. Other times, I've dealt with vendors who will advise you to patch, but will provide a patch certification list to use; a list that's unfortunately constantly behind.
While this should be true, these devices are increasingly being connected to networks to offer integration with EHR/HIS for polling information, and especially in radiology, where images are being sent digitally to PACS. These machines often stay unpatched, yet get connected to the network for transfers. It's important to maintain a separate "medical device" network, but this only goes so far, especially when vulnerabilities bypass the Windows firewall on the medical device, allowing some infected PC/device/server to broadcast worms all over the place.
10% of class time? Where did you get a number like that? It shouldn't take 3.5 to 5 minutes to count 30-40 kids.
5) I'd expect an auto-driver system to be seperate from any other computing devices in the car, and connected to the internet or any other vector for hacking. I'd expect them to be as immune to hacking as an auto-pilot system in a plane.
While you'd expect it to be separate, the track record for the security of vehicle electronics is not good at the moment. Unless there's some regulation on the matter (be it government mandated or industry self-regulated), the bean counters may not see the benefit of doing so until Consumer Reports does some exposé on the matter and everybody starts to panic over it.
Not really. You should try driving a vehicle with a manual transmission. The most mundane of drives can feel exciting - without speeding.
Is it Fridge Day already?