It's the law, you just don't live in the right place (;-))
Seriously, though, it's consistent with the U.S. constitution's protection of privacy, and is claimed to be the law in some states. It wasn't Minnesota law back when I lived in Minneapolis, but that was a while ago...
There is a principle in law (but not in all jurisdictions) that one can only keep personal information about one's customers during the time one is doing business with them. Libraries, one of the original examples, only keep "who has book X" records until the book is returned.
What business relationship does the Navy have with random people, and what are they doing with copies of their parking tickets? Personal information, and especially personally identifying information should be closely held. Therefor it should not be collected by businesses, police or the military except where the law specifically allows.
To make it a little harsher, is not possession of someone else's social security number in the U.S. prima facie evidence of an attempt to impersonate them? Of "identity theft"?
Sun, when it still shone, used containers heavily, because they made "dedicate a machine" trivial.
You could give a product or product suite a dedicated machine, and have netstat or vnstat report on just the behavior of the one program. You could clone a copy of production for the developers to base their next release on, you could hand a release to QA to test hand have them hand it back, and finally you could hand a tested machine to production to start exposure testing.
This allowed a much more agile cycle than having to re-install a product for development, install it again for test, then fail to reproduce a problem and have tor reinstall both, and finally reinstall the "fixed" config on prod and have the bug come back! Far better quality, and far less work.
I'm a capacity planner, so I liked it because I could give a "machine" a minimum guarantee of 20% of a 64-cpu machine, and know that it it would give back the capacity it didn't use, something that "hard" LPARS can't do.
If Red Hat or any of the other well-known distros had a spin I could burn to a thumb-drive that was XP-user-friendly, I could show it off and expect what my company's receptionist once asked: "That looks nice, what version of Windows is this?"
A colleague had installed Linux on the reception PC, and left a yellow stick to tell the receptionists to ask me for the password.
Courts overturn those with ease.
We once encountered a CP/M program whose license prohibited reverse engineering, but when examined appeared to be a blatant copy of another. After disassembly, it was found to indeed be stolen software. The reverse engineering clause was found unenforceable as contrary to long-standing public policy, as it would have prevented reporting it to the police.
You have "limited privilege" against legal action if you report it to the police. Consult a lawyer in your area if you see such a case, they will give you a fixed-price chunk of time in most cases.
We had a standing joke about a "prolong machine", that you could start running and transfer it to a rack in the back room, to be checked once a month to see if it terminated (;-))
After the first "new" language, it gets easier. In my university they did a course to get us past the bad p[art of the learning curve. They had us writing the same programs in FORTRAN, APL and LISP. Today they'd be doing C, Java and Prolong (:-))
Actually I studied Bayesian analysis under George Lasker in university (back when dinosaurs walked the earth), and it is a good way to deal with crappy, disorganized evidence. In effect, you find the ares to search, ordered by
- the likelihood of getting evidence from searching there
- the strength of each kind of evidence, and
- the difficulty of searching a given area.
After each search result comes in, you recompute and find the next best place to search.
Courts always have the power to require data be preserved, ever since an Assyrian vendor smashed his clay tablets with a hammer to keep the captain of the guard from seizing them (;-))
They also have to specify exactly what's to be preserved, to avoid causing an unintentional denial-of-service attack on the recipient of the order, and they can require they be sealed, preserved in particular forms, or handed over to the court.
The quote was initially attributed to Orwell, but it was not in his published writings. See http://quoteinvestigator.com/2... which identified the first usage as
1982, Partners in Ecocide: Australia’s Complicity in the Uranium Cartel by V. G. Venturini (Venturino Giorgio Venturini), (Epigraph facing the title page), Rigmarole Book Publishers, Clifton Hill, Australia. (Verified with scans; thanks to John McChesney-Young and the University of California, Berkeley library system)
I have heard that sysadmins here regularly take salable material home, but when I asked my boss, he said I was being silly. Can I really have a side business selling secrets so long as it's to Americans? Or do I have to leave all that money on the table...
France has examining judges, Canada and the U.S. have special prosecutors, in part to ensure that political pressure can't shut down a prosecution. Examining judges are mostly automatic of serious crimes, but special prosecutors are rare and unusual, and appointing one often take considerable political power.
Solved problem in jusrisprudence, just not our jurisprudence!
You approach closer and close to the "absolute truth", but never get there, and every pi microns there is an e chance that there will be a step function and the whole convergence has to start again.
The difference is that the repo company is using your information commercially, rather similarly to the photographic case, and you're required by law to display your license plate. The body requiring you to do the displaying has a duty of confidentiality toward you, and. for example, may be failing in it by not restricting what commercial entities do with the information.
It's technically a "vexed problem", but not necessarily an insoluble one.
Making it even harder is the question of scale. As Joseph Stalin once said, "quantity has a quality all it's own", a problem the courts have not been very forward in addressing.
--dave
Thinking about mostly legalistic issues, although this is really a public policy question. Our lawgivers haven't been terribly forward in addressing those, you understand!
Slashdot Mirror
It's the law, you just don't live in the right place (;-))
Seriously, though, it's consistent with the U.S. constitution's protection of privacy, and is claimed to be the law in some states. It wasn't Minnesota law back when I lived in Minneapolis, but that was a while ago ...
There is a principle in law (but not in all jurisdictions) that one can only keep personal information about one's customers during the time one is doing business with them. Libraries, one of the original examples, only keep "who has book X" records until the book is returned.
What business relationship does the Navy have with random people, and what are they doing with copies of their parking tickets? Personal information, and especially personally identifying information should be closely held. Therefor it should not be collected by businesses, police or the military except where the law specifically allows.
To make it a little harsher, is not possession of someone else's social security number in the U.S. prima facie evidence of an attempt to impersonate them? Of "identity theft"?
Sun, when it still shone, used containers heavily, because they made "dedicate a machine" trivial.
You could give a product or product suite a dedicated machine, and have netstat or vnstat report on just the behavior of the one program. You could clone a copy of production for the developers to base their next release on, you could hand a release to QA to test hand have them hand it back, and finally you could hand a tested machine to production to start exposure testing.
This allowed a much more agile cycle than having to re-install a product for development, install it again for test, then fail to reproduce a problem and have tor reinstall both, and finally reinstall the "fixed" config on prod and have the bug come back! Far better quality, and far less work.
I'm a capacity planner, so I liked it because I could give a "machine" a minimum guarantee of 20% of a 64-cpu machine, and know that it it would give back the capacity it didn't use, something that "hard" LPARS can't do.
Only slightly tongue-in-cheek, I fear the US is in the middle of a civil war they haven't noticed yet...
If Red Hat or any of the other well-known distros had a spin I could burn to a thumb-drive that was XP-user-friendly, I could show it off and expect what my company's receptionist once asked: "That looks nice, what version of Windows is this?"
A colleague had installed Linux on the reception PC, and left a yellow stick to tell the receptionists to ask me for the password.
--dave
The traditional fate of spies is death, so arrange to catch one and rendition him to Russia.
Courts overturn those with ease. We once encountered a CP/M program whose license prohibited reverse engineering, but when examined appeared to be a blatant copy of another. After disassembly, it was found to indeed be stolen software. The reverse engineering clause was found unenforceable as contrary to long-standing public policy, as it would have prevented reporting it to the police.
You have "limited privilege" against legal action if you report it to the police. Consult a lawyer in your area if you see such a case, they will give you a fixed-price chunk of time in most cases.
We had a standing joke about a "prolong machine", that you could start running and transfer it to a rack in the back room, to be checked once a month to see if it terminated (;-))
Paul Stachour describes fixing this (and other problems) back in the Mainframe era in the article http://cacm.acm.org/magazines/...
Whether the companies in question can read is a different question...
After the first "new" language, it gets easier. In my university they did a course to get us past the bad p[art of the learning curve. They had us writing the same programs in FORTRAN, APL and LISP. Today they'd be doing C, Java and Prolong (:-))
After each search result comes in, you recompute and find the next best place to search.
Er, I forget know what's in my itemized phone bill, so it doesn't mean much. My accountant, on the other hand, would freak .
Who you are, who you're talking to, where you are, where they are and how fast you're moving if you're changing cells.
Er, joke ends, laugh now...
Courts always have the power to require data be preserved, ever since an Assyrian vendor smashed his clay tablets with a hammer to keep the captain of the guard from seizing them (;-))
They also have to specify exactly what's to be preserved, to avoid causing an unintentional denial-of-service attack on the recipient of the order, and they can require they be sealed, preserved in particular forms, or handed over to the court.
After fixing the inevitable bugs, I want it on my wristwatch with a limited-distance, on-only-if-button-pressed communications link.
It's legal for them to provide it to CSE, but CSE says it''s illegal for them to ask... and it may be illegal to accept.
I have heard that sysadmins here regularly take salable material home, but when I asked my boss, he said I was being silly. Can I really have a side business selling secrets so long as it's to Americans? Or do I have to leave all that money on the table...
France has examining judges, Canada and the U.S. have special prosecutors, in part to ensure that political pressure can't shut down a prosecution. Examining judges are mostly automatic of serious crimes, but special prosecutors are rare and unusual, and appointing one often take considerable political power.
Solved problem in jusrisprudence, just not our jurisprudence!
I'm a cylon, of course I'm irrational! Oh, wait a micron, we're all cylons...
You approach closer and close to the "absolute truth", but never get there, and every pi microns there is an e chance that there will be a step function and the whole convergence has to start again.
And then the cylons show up (;-))
Erk! We still have it somewhat protected in Canada, but lots of tag/plate information has leaked, presumably courtesy of under-the-table payments.
The difference is that the repo company is using your information commercially, rather similarly to the photographic case, and you're required by law to display your license plate. The body requiring you to do the displaying has a duty of confidentiality toward you, and. for example, may be failing in it by not restricting what commercial entities do with the information.
It's technically a "vexed problem", but not necessarily an insoluble one.
Making it even harder is the question of scale. As Joseph Stalin once said, "quantity has a quality all it's own", a problem the courts have not been very forward in addressing.
--dave
Thinking about mostly legalistic issues, although this is really a public policy question. Our lawgivers haven't been terribly forward in addressing those, you understand!