"If IPv6 is properly administered, DNS (per se) will cease to exist. IP addresses will be dynamically assigned, be transitory, and be mobile.
In consequence, there will be no real point in a DNS system, as it exists today. There would be no way a centralized system could keep up with the changes."
On the contrary! It makes DNS more important than ever. However, we will certainly see more dynamically updated DNS records. On the other hand, real servers will still use constant IPv6 addresses.
"Sorry, but this is the exact opposite of my experience.
SuSE is a parasite. They live of proprietary configuration tools (YaST, Sax) and a proprietary installer. If you're a developer, SuSE is definitely the worst distribution out there.
Red Hat, Debian, Mandrake etc. are all ok - but SuSE? No thanks, I don't want Microsoft Linux."
And Red Hat, Debian, Mandrake etc. don't feature proprietary configuration tools?
Many HAM associations consider Power Line Communicatiosn (PLC) harmful due to the interferences it causes. They claim that even the limits imposed by the Regulierungsbehörde für Telekommunikation und Post (German FCC) cause problems for television, radio broadcasts and HAM radio. If they succeed with more tight limits this could be the end for PLC.
Further, many PLC installations in the test regions did not even adhere to the existing limits, they say. If this proves true, it might be that PLC can never into widespread use.
Another point is that many people (at least here) are very sensitive in respect to electromagnetic pollution. The emissions caused by PLC are higher and much more present (they come out of every wall outlet) than those caused by cell phones, which are already believed to cause diseases.
More information (mostly in German-language, use fish) has been gathered by DARC e.V. (German HAM Radio Club).
The T is considered a non-registered trademark (German only, sorry) by Deutsche Telekom. Don't let yourself being caught using this letter without authorization.
"I spoke the Telecom people and they told me becouse they own all the lines in Germany..."
It's not that other companies don't own lines, the Deutsche Telekom is far from owning all lines. However, being the ex-monopolist, they have to lease these lines to their competitiors and it often proves cheaper to lease an existing line for the "last mile" instead of laying another one next to it. This is why many competitors are using alternative access methods such as Cable TV (in some places even for ISDN) or are experimenting with power lines, wireless,...
"The NS 4.x codebase was fucked almost beyond repair (partly I believe because NS was trying to keep up with all the proprietary changes that MS were making to HTML)."
Actually, Netscape introduced more and the more horrid "proprietary extensions" to what they called HTML, even before there was an Internet Explorer. Having a pure tag soup interpreter instead of a parser that understands at least a bit of true HTML, the codebase was "fucked beyond repair" right from the first version.
Not to say that this wasn't true for other browsers, especially MSIE, which was written to be bug-to-bug compatible...
"Well, this probably won't help convince your boss, but IIRC subselects are mathematically unnecessary. You can flatten any query down to a single select and what you get is much more efficient."
Actually, no: There are many situaions where doing a subselect first and then only select a few tuples from the second table is much more efficient then doing a join and selecting a few joined tuples.
On the other hand, finding a mathematically equivalent request that is more efficient is the task of the RDMS, not the database user.
"Or entering passwords for things on the remote host (like things on the serial devices). However the attacker needs to somehow know when you are entering this other password. It won't normally be easy for them to know"
Wrong. Haven't you read the articles about this? According to reports describing this security hole, it's actually quite easy to guess when a password is typed. For one thing, they're a small number of single characters - often even without an echo sent back! - typed in a certain pattern which is different from normal commands typed on the command line.
If you make an anology, you gotta make a correct one:
Hi. I just wanted to let you know that I stopped by your house the other day, and I saw that your front door was standing wide open. The next day it still was wide open. So I went in to see whether there was anything wrong. Everything looked ok except that I found what looked like a key for your safe lying open on the table. Just curious how stupid you really are I tested it and it was really fitting. I think that you have a security problem.
(Note: In real life, thie might constitute trespas. However, there's no such thing as digital trespas. In real life, you'd probably just call the police.)
"So it starts again, with bbs's, then a couple of nearby bbs's link with a cat 5 cable, or a leased line, or a wireless ethernet."
"Someone who does this is obviously interested in illegal activities. So we have to make it illegal to build networks that are not under the supervision of a trusted provider."
"In all honesty though, this -could- be a good thing for us regarding laws. [...] This student, OTOH, broke this w/o profit and without breaking any copyrights."
If you're thinking about the DMCA, you're mistaken. Breaking encryption schemes is not illegal, even not under the DMCA. It's only breaking the encryption of "copy protection schemes" that is illegal, which Wireless Ethernet is not.
However, the patents should not be licenced for free to everyone, only to those who release their source code under the GPL or other Open Source Licences.
Commercial organizations would have to pay for it - or trade in their patents.
This way, patents could be used to boost Open Source software.
No, they can't vote. But many large corporations have enough money to sponsor election campaigns, which is even more effective.
The real problem with corporations is, however, that everything is based on the so-called shareholder value. Whatever they do, they only do it to increase the corporations revenues, even if it eventually hurts society at a whole.
There are a lot of another security problems than buffer overflows and format-string bugs:
Calling shells with untested user-provided parameters (e.g. 'filename; rm -rf/').
Constructing filenames out of untested user-provided parameters (e.g. '../etc/passwd' - there should be more of '../' but Slashdot does not like that).
Providing access to other users' data (e.g. relying on users not doing URL hacking).
Not limiting ressources (=> DoS Attacks); note that 'secure' languages are much more prone to that error because programmers usually don't care sbout size...
Trigger bugs in the environment (interpreter, compiler's RTL).
Scripting languages: Constructing programme code including user-provided data (e.g. with perl's eval statement).
Now if these programmes even run as root because 'they are secure anyway'...
The real solutions have to be different:
Divide everything into small programmes that do simple tasks.
Run every task in a sandbox (chroot environment, user account,...) that gives no more access than absolutely necessary.
Don't trust input be it from the user or another part of the system.
Oh, you mean the text THEY refer to as "licensing agreement" when in fact it has no legally binding effect at all (modulo some contries/states with a screwed legal system)...
In fact, conservatives interpret (rightly IMHO) the constitution literally, as it was written,...
No, you should interpret legal texts according to their meaning and purpose. The wording can be a hint to that. (After a quick check on the Web it seems to me that the methods of statuatory interpretation in the US and other Common Law countries seems to be a bit behind wrt this.)
If you do this with the second amendement, you will have to reduce the right to a point where it only allows you to bear weapons unless the government can provide sufficient protection (which it can nowadays)...
This actually forces users to violate RFC 822, the mail format standard: The From header field must contain the author or authors of the message, not the actual sender. So whenever a Verizon user wants to send a message that was not written by her or him, he is forced to violate RFC 822. The correct solution would be to force a valid account in the From or Sender field (but maybe that's what Verizon ios doing anyway).
Slashdot Mirror
But IPv4 is broken already. It's only that HTTP/1.1 and NAT cover the worst cracks. But it certainly is not a long-term solution.
NAT is harmful because it delays the use of IPv6. NAT sort of works most of the time and where it does not work IPv6 is not yet a real alternative.
And Red Hat, Debian, Mandrake etc. don't feature proprietary configuration tools?
Many HAM associations consider Power Line Communicatiosn (PLC) harmful due to the interferences it causes.
They claim that even the limits imposed by the Regulierungsbehörde für Telekommunikation und Post (German FCC) cause problems for television, radio broadcasts and HAM radio. If they succeed with more tight limits this could be the end for PLC.
Further, many PLC installations in the test regions did not even adhere to the existing limits, they say. If this proves true, it might be that PLC can never into widespread use.
Another point is that many people (at least here) are very sensitive in respect to electromagnetic pollution. The emissions caused by PLC are higher and much more present (they come out of every wall outlet) than those caused by cell phones, which are already believed to cause diseases.
More information (mostly in German-language, use fish) has been gathered by DARC e.V. (German HAM Radio Club).
The T is considered a non-registered trademark (German only, sorry) by Deutsche Telekom. Don't let yourself being caught using this letter without authorization.
It's not that other companies don't own lines, the Deutsche Telekom is far from owning all lines. However, being the ex-monopolist, they have to lease these lines to their competitiors and it often proves cheaper to lease an existing line for the "last mile" instead of laying another one next to it. ...
This is why many competitors are using alternative access methods such as Cable TV (in some places even for ISDN) or are experimenting with power lines, wireless,
This is simply wrong.
Actually, Netscape introduced more and the more horrid "proprietary extensions" to what they called HTML, even before there was an Internet Explorer.
Having a pure tag soup interpreter instead of a parser that understands at least a bit of true HTML, the codebase was "fucked beyond repair" right from the first version.
Not to say that this wasn't true for other browsers, especially MSIE, which was written to be bug-to-bug compatible...
Actually, no: There are many situaions where doing a subselect first and then only select a few tuples from the second table is much more efficient then doing a join and selecting a few joined tuples.
On the other hand, finding a mathematically equivalent request that is more efficient is the task of the RDMS, not the database user.
With the first DeCSS version being for Windows, this can hardly be right.
Wrong. Haven't you read the articles about this? According to reports describing this security hole, it's actually quite easy to guess when a password is typed. For one thing, they're a small number of single characters - often even without an echo sent back! - typed in a certain pattern which is different from normal commands typed on the command line.
If you make an anology, you gotta make a correct one:
(Note: In real life, thie might constitute trespas. However, there's no such thing as digital trespas. In real life, you'd probably just call the police.)
"Someone who does this is obviously interested in illegal activities. So we have to make it illegal to build networks that are not under the supervision of a trusted provider."
According to this article from Heise Online (German only), the sophisticated equipment consists of:
You might have missed the headline:
Sec. 1201. Circumvention of copyright protection systems
If you're thinking about the DMCA, you're mistaken. Breaking encryption schemes is not illegal, even not under the DMCA. It's only breaking the encryption of "copy protection schemes" that is illegal, which Wireless Ethernet is not.
Sorry, this won't be a test case for the DMCA.
Maybe not by your definition and not in your country.
But there are countries where it is explicitly allowed and there are countires where the legal situation is unclear.
http://slashcode.com/faq.shtml#SlashAdministration 3
That's an idea I've thought about, too.
However, the patents should not be licenced for free to everyone, only to those who release their source code under the GPL or other Open Source Licences.
Commercial organizations would have to pay for it - or trade in their patents.
This way, patents could be used to boost Open Source software.
No, they can't vote. But many large corporations have enough money to sponsor election campaigns, which is even more effective.
The real problem with corporations is, however, that everything is based on the so-called shareholder value. Whatever they do, they only do it to increase the corporations revenues, even if it eventually hurts society at a whole.
There are a lot of another security problems than buffer overflows and format-string bugs:
Now if these programmes even run as root because 'they are secure anyway'...
The real solutions have to be different:
And finally:
For example, look at qmail's secutiry scheme.
Which licensing agreement?
Oh, you mean the text THEY refer to as "licensing agreement" when in fact it has no legally binding effect at all (modulo some contries/states with a screwed legal system)...
No, you should interpret legal texts according to their meaning and purpose. The wording can be a hint to that. (After a quick check on the Web it seems to me that the methods of statuatory interpretation in the US and other Common Law countries seems to be a bit behind wrt this.)
If you do this with the second amendement, you will have to reduce the right to a point where it only allows you to bear weapons unless the government can provide sufficient protection (which it can nowadays)...
This actually forces users to violate RFC 822, the mail format standard: The From header field must contain the author or authors of the message, not the actual sender.
So whenever a Verizon user wants to send a message that was not written by her or him, he is forced to violate RFC 822.
The correct solution would be to force a valid account in the From or Sender field (but maybe that's what Verizon ios doing anyway).