Slashdot Mirror
Microsoft's Guidelines for Customer Privacy
jcatcw writes "Microsoft has released its 'Privacy Guidelines for Developing Software Products and Services.' According to Peter Cullen, chief privacy strategist, Microsoft has learned about protecting user's data from such endeavors as Hailstorm and WGA. 'Certainly that and other things have contributed to us thinking deeply with how we provide security and privacy, as well as respect and control with how their information is used,' he said. 'We think others should join in this discussion.'"
First schools banning tag, and now the Evil Empire values privacy?
What is this, April Fools come early?
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
... don't collect (and keep and share and sell) crap just because you can - show some backbone and leadership and collect as little as is necessary to serve your customer.
"WGA. "Certainly that and other things have contributed to us thinking deeply with how we provide security and privacy"
Is that why you have to sell your first born to Microsoft if you install Windows Media Player 11, and break the EULA? I bet you didn't know that was in there! It pays to read EULAs, unless you want rid of that kid.
And if they've learned from the WGA fiasco, why are they still requiring XP users to install it to get all updates?
Oh You POS
Was it a good idea to name a program that stores people's names and credit card information after an egyptian plague?
What's the smallest page on the web?
I thought WGA didn't keep any data on the user only the machine. I guess that "anonymous" data collection isn't so anonymous after all.
FTFA: "The document outlines recommendations for software developers that will help them protect customer privacy"
Bolded emphasis mine. MS and their legions of developers won't do anything differently.
"Discussion." Indeed. This is MS working their coordinated PR effort to make them seem serious about "security." Talk all you want, no one is listening.
Keep in mind, I have to babysit these things for a living. So I am quite happy they don't actually address the issue directly because there will be no shortage of work.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
... is not to collect it in the first place.
you are the producer of the product they provide to their customer. What on earth gave you the idea that you were the customer?
Slashdot Burying Stories About Slashdot Media Owned
"We didn't spend enough time to make sure [the feature] met our standards," he said.
Or enough time to make sure their standards met their features?
*Still* negative function...
"We think others should join in this discussion."
Like Claria maybe?
Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
Symantec is offering guidelines to developers of antivirus solutions to use minimal resources.
Richard Stallman is offering guidelines for developers wanting to release proprietary code.
The Pope is offering guidelines on peaceful and friendly methods of talking about other religions.
Isn't this a good example of the blind leading the blind and dumb?
You will be baked, and there will be cake.
i would trust microsoft with my personal information about like i would trust a heroin addict to hold my wallet full of cash and credit cards...
Politics is Treachery, Religion is Brainwashing
Spill and/or sell first, pretend it didn't happen, and apologize only when the media calls.
7865 6689 1670
8265 6098 1847
5633 2979 2857
7284 8236 3827
1234 4478 2683
8817 7967 5024
...has released a 49-page document entitled "The Big Bad Wolf's Guidelines for Protecting Little Red Riding Hood." In a prepared statement, the wolf said:
"We'd like others to join the conversation. A long, long time ago, several weeks ago in fact, we were a little insensitive about the way we implemented our last henhouse raid. Critics complained that wearing grandmother's clothing was deceptive, and that what we were doing posed a risk to Little Red Riding Hood. While we want to emphasize that Little Red Riding Hood was not harmed, that and other things have contributed to us thinking deeply with how we provide security and privacy, as well as respect for those we eat, for the use humane slaughtering practices. We also wish to assure the consumed that we target only henhouses, and that any collateral loss of innocent human life is accidental and deeply regretted."
"Our new guidelines protect the consumed by prohibiting the use of cloaks intended to resemble human beings. From now on, we will cloak ourselves only in the garb of sheep. We've devised technology in the form of a new chalk filter that guarantees that any traces of our individual voice identity will be erased, and that there is no possibility of causing psychological harm to our victims by the use of harsh vocalizations."
"We have asked our colleagues the Fox and the Coyote to join with us and to follow only best predatory practices."
"Because of this increased protection, we no longer recommend that home users build firewalls of brick. Instead, they should enjoy the economy, light, and airy comfort of porous straw walls, perforated by dozens of Windows."
"How to Do Nothing," kids activities, back in print!
For a more user-side view of privacy from a technical standpoint, the National Association of Theater Owners Digital Cinema Requirements document is valuable. Digital cinema at the movie theater level has DRM, and the theater owners have organized to tell (not ask) the studios exactly how intrusive the DRM can be. Stuff like
- "The System shall not compromise the security of the theatre's in-house
network, including the security of digital cinema systems, point-of-sale
systems, and other data systems owned and/or operated by the exhibitor." (i.e. no Sony-type rootkits)
- "The system shall be designed to push data to outside business entities per
the needs of the exhibitor, and shall not allow outside business entities to
pull data from the exhibitor's equipment or from the premises without the
express written permission of the exhibitor on a case-by-case basis. All such
communications shall be recorded and shall be auditable by the Exhibitor." (i.e. no spyware; the user has to explicitly send the log data, and can look at it first)
- "System components (servers, projectors) shall be capable of being moved
from auditorium to auditorium within the same facility in any combination
without limitation and without requiring receipt of new decryption keys." (you can swap components around without DRM problems)
- "Systems shall allow the movement and playback of shows among all
auditorium systems within a complex." (you can move the movie from one room to another without DRM problems)
- "New Security Keys shall be delivered within 15
minutes of the time of request." (no long downtime because the DRM people screwed up)
-
"Systems shall employ the standard interchange method for security log
reports
.... Systems shall
employ tools that allow the exhibitor to filter security log reports logs prior to
sharing." (it's all in XML, and you can see what the DRM owner sees.)
Compare that with Windows Vista.MS and their legions of developers won't do anything differently.
Apologies to all MSDev's out there that -want- to design and implement more security. It is tough when requirements/management/resource restraints prevent it. I've seen it first hand.
I typed too quickly.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
What he said.
"How to Do Nothing," kids activities, back in print!
"That is a problem, and we are working on it!"
Looking for something to do? http://www.grinion.com
any time a company or country defines security or privacy, it isn't to ensure their customers/citizens have more but to put limits on how much they need ro provide.
Here will be an old abusing of God's patience and the king's English.
I though I would never say this, but in a sense, I want Microsoft to know who I am when it comes to WGA. That way, when WGA screws up, I can prove that I'm the owner.
Something like when I activate windows, I have the option to login to my passport to associate my windows ID with that Windows Serial Key. that way, if my key is stolen by some hacker and WGA decides to lock my computer down, I can contact MS and prove that I'm the original owner of that key and get it either unlocked or a new key resubmitted.
If I have to deal with WGA on windows, at least allow me to protect myself from being screwed out of my purchase by the next key stealing Trojan or eventual random keygen.
In Soviet Russia, Trojan exploits YOU!
As an advocate of privacy, I applaud this document. Software developers have a duty and an obligation to consider the privacy of their users. This document helps to uncover some of the issues surrounding privacy, how to avoid risks to privacy, and how to mitigate those privacy risks that are unavoidable.
It's time for software professionals to start taking responsibility for their work.
Most of it read like any PR release would read. They promise this time that they will guard data more carefully. They're sorry about all the other times that they didn't. If anything WGA showed that they didn't learn their lesson. Their excuse for WGA?
What standards? According the article, they didn't have any guidelines in place until recently, much less standards.
Well, there's spam egg sausage and spam, that's not got much spam in it.
They have guidelines?????
Did anyone else read this as.. 'Microsoft's Guidelines for Customer Piracy'
"I bow to no man" - Riddick
11,000 pages of:
This page is intentionally left blank.
Calling someone a "hater" only means you can not rationally rebut their argument.
Keep in mind that MS thinks that the customer is NOT only the computer user who buys the operating system. The "customer" refers mostly to the advertizer who pushes adds to the pc user !
They should start by stopping the use of audio surveillance at large customer sites and not attaching GPS trackers to purchasing reps of customers.