Music has copyright on it. Get used to it. How would you feel if you produced a hit one day, it's played everywhere, but instead of a lot of money, you only receive a few pats on the back?
Every modern code has a way of encoding aribitary data. It has to be spelt out if it's not in the dictionary, but as long as it's not too many words, it's not a big deal.
Re:This has been going on for 30 years
on
Morals and Layoffs
·
· Score: 2
Actually, it's been going on for the entire industrial revolution. As soon as factories where invented, then there was an incentive for employers to adjust workforce to needs. If the shipment of cotton bales didn't arrive, then the employees wouldn't be working, or being paid, this week.
Exactly why I'm always hounding the people who work for me to get out the door when they've done their 40 hours. If the work isn't done, then it's my responsibility to hire more people, not to overwork the ones I've got.
The file is encrypted using IDEA, which is a symetric cipher (no public key), with a randomly chosen session key. This session key is encrypted using RSA, which is the public key cipher. You don't want to use RSA for the entire file, because it's too slow.
This is general way that all public key encryption systems work.
By including multiple key blocks, you can have a file which can be decrypted by more than one person.
Therefore, to include a backdoor, you would ensure that the session key is always included encrypted using the escrow's public key.
in Uzbekistan they had currency steps of 1 and 3 (so you get 1 cym notes, 3 cym notes, 10 cym notes, 30 cym notes and so on).
True 3 step is the one which mathematically gives the smallest number of notes in the largest number of transactions. Unfortunatly, we don't count too well in 3's, so the 1,3 stepping is a good compromise, still requiring less per transaction than the 1,5.
In 1980 everything was propriatary. If you bought a Nova, you'd probably be running AOS. If you bought a PDP-11, you've probably be running RT-11 or it's descendants. If you bought a Pr1me, you'd be running Pr1mos. If you decided that your Pr1me wasn't right, and wanted to run the Nova instead, then you'd be totally stuffed. There was no easy way to get from one to the other without throwing everything away and starting again.
By the late 80's and early 90's, every manufacturer had a version of Unix, or they were about to die. If you had a system running Solaris and decided that Sun weren't supporting you, you could run HP-UX on HP's instead.
PC's became commodities, so if you didn't like your Dell hardware you can buy Compaq instead.
While there is currently only one OS supplier for PC's, this is sitll markably better than the enviroment in 1980.
Good and evil are not relativeOf course they are. It's good if someone gives $1 to charity. It's better if someone gives $1000. It's evil if someone kills one person. It's worse if they kill 5000 people.
but unless they were involved in a large scale university project
Even then, I don't think it's applicable to the real world. Unless you've dealt with 10 year old source code, where everyone who originally designed it has left, and where there is a requirement to add new features which were never originally considered and which require really horrible hacks.
It takes experience to understand how to design programs & systems so that they will last for the long term, and no-one I've ever seen has it coming out of school.
To any business that's become reliant on MS technology, and thinks these price hikes might cost them dearly, I'd say this: This is what Richard Stallman warned you about 20 years ago. If you rely on proprietary software, belonging to a third party, you're putting yourself in a position where that third party has you by the nuts.
This was hardly a flash of insight. 20 years ago IBM was near the end of it's anti-trust case, and it was clear that they used the control of their mainframe software to control their competitors and customers. If he had said it 40 years ago, then it would be perceptive.
The Encyclopaedia Galactica defines a robot as a mechanical apparatus designed to do the work of a man. The marketing division of the Sirius Cybernetics Corporation defines a robot as "Your Plastic Pal Who's Fun To Be With".
The Hitch Hiker's Guide to the Galaxy defines the marketing division of the Sirius Cybernetic Corporation as "a bunch of mindless jerks who'll be the first against the wall when the revolution comes", with a footnote to the effect that the editors would welcome applications from anyone interested in taking over the post of robotics correspondent.
The Marketing and Legal departments are two very different evils.
Originally it would automatically repair all filesystems on startup,
simultaneously. Now you have to log in with a password and manually
invoke the filesystem checker for every filesystem.
This is a decision of whoever writes the startup scripts. Red Hat 7.1 automatically repairs each filesystem on startup, unless the damage requires manual intervention because fsck can't decide how to repair it. This is always the way that fsck has worked since fsck's began to have automatic repair facilities, which for me was about SVR3.
Originally passwords were stored in one passwd file. Now they're
stored in 3 password files.
I think everyone agrees that shadow password files are a good thing.
Originally telnet servers were enabled by
default.
Again a decision of whoever writes the inetd.conf or xinetd files. Most distributions have decided that the majority of people don't want or need telnet access.
Even tab completion now requires you to answer a prompt before getting
a directory listing.
This is varies by shell. The zsh asks if you want to see the possibilities if there are large number. This is simply to avoid flooding your screen with hundreds of choices. I don't belive that bash or tcsh have a similar prompt, though I'm not a user of either shell, so I can't say so for definate.
So 3 of your issues are packaging/design issues, and only one is a true security change.
I'll make the same argument I've made with many privacy advocates in the past few days: you wouldn't be griping if you were here. Seeing a plane crash into a building on TV is one thing. Seeing it across the river (I live in NJ) is another.
I have been much closer than that to terrorist actions. If I had been walking 30 seconds faster, I would have been blown up by an IRA bomb, but I do not agree with the moves to remove freedom. The major problem is that they simply will not work. Even Winston Smith, under almost total monitoring could still hide.
Also the banks had their seperate datastores, and worked together to interoperate. This is very different to Microsoft owning everything then allowing others to play too.
But if the API isn't documented, then I can't use the library at all. I'm not going to try to work out how to use a library by looking at the method signatures & source code, it's going to be incredibly tedious and error prone. I don't think many people would, it would probably be easier to write your own library if that was the only choice.
That "if" is a very big if. Quite frankly, even if we lived in a 1984 style state where we are constantly spied on, it would still be impossible to prevent terrorist attacks.
If you've documented the API, you can re-implement the functionality. The internal methods used may differ, but that's not going to affect a program using the documented API.
Slashdot Mirror
That's exactly what's happening to the artists.
Every modern code has a way of encoding aribitary data. It has to be spelt out if it's not in the dictionary, but as long as it's not too many words, it's not a big deal.
No I disagee, you have to assume that government powers WILL be abused, simply because that's the historical precident.
I imagine that most people interact with their spouse more frequently than their politicans.
Fraid not. I'm in Canada.
Actually, it's been going on for the entire industrial revolution. As soon as factories where invented, then there was an incentive for employers to adjust workforce to needs. If the shipment of cotton bales didn't arrive, then the employees wouldn't be working, or being paid, this week.
Exactly why I'm always hounding the people who work for me to get out the door when they've done their 40 hours. If the work isn't done, then it's my responsibility to hire more people, not to overwork the ones I've got.
The file is encrypted using IDEA, which is a symetric cipher (no public key), with a randomly chosen session key. This session key is encrypted using RSA, which is the public key cipher. You don't want to use RSA for the entire file, because it's too slow.
This is general way that all public key encryption systems work.
By including multiple key blocks, you can have a file which can be decrypted by more than one person.
Therefore, to include a backdoor, you would ensure that the session key is always included encrypted using the escrow's public key.
Actually precious metals & minerals were the second step. The first step is direct barter - I'll give you 2 sheep for that cow.
True 3 step is the one which mathematically gives the smallest number of notes in the largest number of transactions. Unfortunatly, we don't count too well in 3's, so the 1,3 stepping is a good compromise, still requiring less per transaction than the 1,5.
In 1980 everything was propriatary. If you bought a Nova, you'd probably be running AOS. If you bought a PDP-11, you've probably be running RT-11 or it's descendants. If you bought a Pr1me, you'd be running Pr1mos. If you decided that your Pr1me wasn't right, and wanted to run the Nova instead, then you'd be totally stuffed. There was no easy way to get from one to the other without throwing everything away and starting again.
By the late 80's and early 90's, every manufacturer had a version of Unix, or they were about to die. If you had a system running Solaris and decided that Sun weren't supporting you, you could run HP-UX on HP's instead.
PC's became commodities, so if you didn't like your Dell hardware you can buy Compaq instead.
While there is currently only one OS supplier for PC's, this is sitll markably better than the enviroment in 1980.
Mother Theresa did do some morally disputable things. She felt that suffering was morally good, so witheld painkillers to those in pain.
Good and evil are not relativeOf course they are. It's good if someone gives $1 to charity. It's better if someone gives $1000. It's evil if someone kills one person. It's worse if they kill 5000 people.
Even then, I don't think it's applicable to the real world. Unless you've dealt with 10 year old source code, where everyone who originally designed it has left, and where there is a requirement to add new features which were never originally considered and which require really horrible hacks.
It takes experience to understand how to design programs & systems so that they will last for the long term, and no-one I've ever seen has it coming out of school.
This was hardly a flash of insight. 20 years ago IBM was near the end of it's anti-trust case, and it was clear that they used the control of their mainframe software to control their competitors and customers. If he had said it 40 years ago, then it would be perceptive.
The Encyclopaedia Galactica defines a robot as a mechanical apparatus designed to do the work of a man. The marketing division of the Sirius Cybernetics Corporation defines a robot as "Your Plastic Pal Who's Fun To Be With". The Hitch Hiker's Guide to the Galaxy defines the marketing division of the Sirius Cybernetic Corporation as "a bunch of mindless jerks who'll be the first against the wall when the revolution comes", with a footnote to the effect that the editors would welcome applications from anyone interested in taking over the post of robotics correspondent. The Marketing and Legal departments are two very different evils.
The register has a story which stay that if it was Bin Laden, he's not been using ANY technology for several hears.
Most sensible people are happy to accept criticism, as it's the only way they'll learn their faults and improve.
This is a decision of whoever writes the startup scripts. Red Hat 7.1 automatically repairs each filesystem on startup, unless the damage requires manual intervention because fsck can't decide how to repair it. This is always the way that fsck has worked since fsck's began to have automatic repair facilities, which for me was about SVR3.
Originally passwords were stored in one passwd file. Now they're stored in 3 password files.
I think everyone agrees that shadow password files are a good thing.
Originally telnet servers were enabled by default. Again a decision of whoever writes the inetd.conf or xinetd files. Most distributions have decided that the majority of people don't want or need telnet access.
Even tab completion now requires you to answer a prompt before getting a directory listing.
This is varies by shell. The zsh asks if you want to see the possibilities if there are large number. This is simply to avoid flooding your screen with hundreds of choices. I don't belive that bash or tcsh have a similar prompt, though I'm not a user of either shell, so I can't say so for definate.
So 3 of your issues are packaging/design issues, and only one is a true security change.
I have been much closer than that to terrorist actions. If I had been walking 30 seconds faster, I would have been blown up by an IRA bomb, but I do not agree with the moves to remove freedom. The major problem is that they simply will not work. Even Winston Smith, under almost total monitoring could still hide.
Also the banks had their seperate datastores, and worked together to interoperate. This is very different to Microsoft owning everything then allowing others to play too.
But if the API isn't documented, then I can't use the library at all. I'm not going to try to work out how to use a library by looking at the method signatures & source code, it's going to be incredibly tedious and error prone. I don't think many people would, it would probably be easier to write your own library if that was the only choice.
That "if" is a very big if. Quite frankly, even if we lived in a 1984 style state where we are constantly spied on, it would still be impossible to prevent terrorist attacks.
If you've documented the API, you can re-implement the functionality. The internal methods used may differ, but that's not going to affect a program using the documented API.
Is anyone else thinking of the Greybook protocol?