I would die for the day where I could get a chance to program 40 hours a week. I think I get about an hours worth of actual programming done during the week. The rest is spent dealing / haggling with process related overheads, testers, test managers, managers and meetings.
tc basically allows you to activate netem (a network emulator in linux). I dont know about now, but when I had used it for a project a year ago, you had to compile your kernel with netem enabled. tc then allowed you to modify your link properties to emulate wan links.
Had used this with tcpprobe to analyze the performance of an Inverse Increase Additive Decrease congestion control algorithm that we had written for academic purposes (adapted from http://nms.lcs.mit.edu/papers/binomial-infocom01.pdf) and compare its performance with newreno. Fun stuff.
This was a helpful reference:
http://linuxgazette.net/135/pfeiffer.html
Internet Census Taking,
We believe we have taken the first census contacting each address of the visible Internet since 1982 (RFC-832). A census is an enumeration of all allocated addresses. We probed all 2.7 billion allocated addresses (compared to 315 in 1982). We are able to probe only the visible Internet: all addresses that use public addresses and choose to respond.
Accuracy,
No census of billions of addresses will be perfect; we underestimate occupancy for three reasons: A few percent of probes and replies are lost due to congestion. Addresses such as those behind firewalls choose not to receive or reply to our requests. Other computers use private addresses. We evaluate loss in our technical report; evaluation of the other cases, the invisible Internet, is future work.
It takes a normal person more than 60 seconds on an average to search all of his/her pockets and bags and for a ballpoint pen before he/she realizes that another one has disappeared.
Right said Fred. It has been used for quite a few sensornet applications where eventual delivery of data is essential. Another example could be for connectivity on highways. For example, an email app running over a DTN bundle layer could schedule bundles for future delivery while you were using your laptop in a car. You could then have geographically dispersed access points which provide intermittent connectivity to the Internet. Whenever you cross one of these access points the DTN protocol stack on your laptop could transfer as many bundles (including partial bundles) as it could during that short period. Whenever you reach another access point, your machine could start transmitting from exactly where it left off (the convergence layers running below the bundle layer would help in figuring out the right point) without having to start the data transfer from the beginning as you would have to without DTN. This is only possible because DTN allows for in-network storage and custody transfers (where one or more intermediate node in the network accepts responsibility for the delivery of bundles to the destination). DTN has some very useful applications although it was originally conceived for the Interplanetary Internet.
Re:you can't stop the doomsayers
on
LHC Success!
·
· Score: 1
what you really meant to say is that they have black holes in their heads...
Yes, you missed the point somewhat. Im not sure that I follow your question completely but Ill try to answer it and I hope that I dont end up repeati
ng what you already followed. Sorry if I do:-)
First of all, you dont need to register anything.
The basic idea behind TC is to build a trusted computing base (TCB) i.e. a trusted hardware and software environment that you are communicating with. There is no "certifying authority" per se. The only certifying authority is your own system or the TPM. Each lower level component generates checksums (or requests the TPM to generate them) for the next higher level component. The TPM encrypts these checksums. Now when such a machine communicates with say a digital content provider's server, it first sends the checksums across to the other end. The other end validates these checksums to determine whether you are running on a platform (hardware and software) that it trusts and knows to be correct (the checksums wouldnt match if your OS was infected for instance) and only allows you access to the content if it trusts your platform including the application which you will use to view the content.
The basic idea as trusted computing was envisioned was to have trust with what hardware and software you communicate with in a distributed computing environment. The idea in itself is very ingenious but the industry has taken it and given it an ugly turn in the form of DRM and yes, it will be enforced on you. The industry will decide what it wants to trust and what it does not want to trust.
The industry will decide what applications you can use to view their content. The industry will decide what OS you will have to run if you need access to their content (because accomodating every OS and every possible patch/mod is going to be extremely hard). So yes, it is evil in a way.
However one should realize that trusted computing in itself as far as the idea goes is not evil - the way it is and will be used by the corporates is definitely evil.
Think of DRM for example when you think of applications. The TC architecture was designed for use in distributed systems (actually the paper that laid the groundwork for it is here:
http://research.microsoft.com/lampson/41-DigitalDSSA/41-DigitalDSSAAsPub.pdf)
The reason why it can work despite not having every application be certified is that if an application modifies your OS, your OS checksum will fail which means that the TPM will prevent your system from booting (if i remember right - been a few months since I reviewed TC related material). To what extent and what extreme these restrictions on applications are to be placed is exactly what makes TC controversial.
Actually, its already taken off. Many new laptops today ship with a TPM. Vista has a significant amount of TPM implemented in it, which although if Im not mistaken, can currently be turned off - correct me on this(this wont be allowed eventually). The digital content industry is looking very seriously into TC and so is the security research community. I studied under a professor who was doing a lot of TC related work in his research. It will not completely fail to take off because it already has to some extent and it has many really big corporates really pushing hard for it, but theres still significant work left.
TC is another reason for the open source community to hate the closed source community. You basically wont be able to run a self modded kernel unless it is present in the checksum database with the certifying authority.
Slashdot Mirror
I would die for the day where I could get a chance to program 40 hours a week. I think I get about an hours worth of actual programming done during the week. The rest is spent dealing / haggling with process related overheads, testers, test managers, managers and meetings.
It's still a great field with good salary, sane work hours and prospects for advancements
I'll have one of what this guy is smoking please.
tc basically allows you to activate netem (a network emulator in linux). I dont know about now, but when I had used it for a project a year ago, you had to compile your kernel with netem enabled. tc then allowed you to modify your link properties to emulate wan links. Had used this with tcpprobe to analyze the performance of an Inverse Increase Additive Decrease congestion control algorithm that we had written for academic purposes (adapted from http://nms.lcs.mit.edu/papers/binomial-infocom01.pdf) and compare its performance with newreno. Fun stuff. This was a helpful reference: http://linuxgazette.net/135/pfeiffer.html
The researchers do address your points:
http://www.isi.edu/ant/address/
Internet Census Taking,
We believe we have taken the first census contacting each address of the visible Internet since 1982 (RFC-832). A census is an enumeration of all allocated addresses. We probed all 2.7 billion allocated addresses (compared to 315 in 1982). We are able to probe only the visible Internet: all addresses that use public addresses and choose to respond.
Accuracy,
No census of billions of addresses will be perfect; we underestimate occupancy for three reasons: A few percent of probes and replies are lost due to congestion. Addresses such as those behind firewalls choose not to receive or reply to our requests. Other computers use private addresses. We evaluate loss in our technical report; evaluation of the other cases, the invisible Internet, is future work.
It takes a normal person more than 60 seconds on an average to search all of his/her pockets and bags and for a ballpoint pen before he/she realizes that another one has disappeared.
Right said Fred. It has been used for quite a few sensornet applications where eventual delivery of data is essential. Another example could be for connectivity on highways. For example, an email app running over a DTN bundle layer could schedule bundles for future delivery while you were using your laptop in a car. You could then have geographically dispersed access points which provide intermittent connectivity to the Internet. Whenever you cross one of these access points the DTN protocol stack on your laptop could transfer as many bundles (including partial bundles) as it could during that short period. Whenever you reach another access point, your machine could start transmitting from exactly where it left off (the convergence layers running below the bundle layer would help in figuring out the right point) without having to start the data transfer from the beginning as you would have to without DTN. This is only possible because DTN allows for in-network storage and custody transfers (where one or more intermediate node in the network accepts responsibility for the delivery of bundles to the destination). DTN has some very useful applications although it was originally conceived for the Interplanetary Internet.
what you really meant to say is that they have black holes in their heads...
"satisfied girlfriend" is an oxymoron
I thought AlpineKat already taught us all about the LHC.
I just read the title and double checked to see if Id overslept for 20 years.
It seems that its kind of clouded what cloud computing really means.
Actually Frank Costanza's Butler
umm... Fahrenheit.
or use the fanboi solution... blame Microsoft for the influenza virus and then buy a new replacement Mac.
I never clean my laptop. Helps me build up my resistance. Sure you may get sick in the beginning but you only get stronger as time passes.
Waiting for the fanbois to start blaming microsoft.
can i have my stapler back please ?
what and make him expect me to have the same amount of energy as him? Nothxbye
Maybe I could hack my boss' coffee maker and weaken his daily dose.
1. http://citeseer.ist.psu.edu/
2. If you have an ACM membership:
http://portal.acm.org/portal.cfm
3. If your university gives you access to engineering village:
http://www.engineeringvillage2.org/controller/servlet/Controller
IEEE transactions on software engineering
4. http://csdl2.computer.org/persagen/DLPublication.jsp?pubtype=t&acronym=ts
5. Google:
http://www.google.com/
Beyond this, its upto you to do your own research.
So Microsoft is supposed to fix something that it might be doing right but the router's shitty firmware cannot support?
In the long run TPMs are going to be integrated onto your CPU itself and will not be on the motherboard.
Yes, you missed the point somewhat. Im not sure that I follow your question completely but Ill try to answer it and I hope that I dont end up repeati ng what you already followed. Sorry if I do :-)
First of all, you dont need to register anything.
The basic idea behind TC is to build a trusted computing base (TCB) i.e. a trusted hardware and software environment that you are communicating with. There is no "certifying authority" per se. The only certifying authority is your own system or the TPM. Each lower level component generates checksums (or requests the TPM to generate them) for the next higher level component. The TPM encrypts these checksums. Now when such a machine communicates with say a digital content provider's server, it first sends the checksums across to the other end. The other end validates these checksums to determine whether you are running on a platform (hardware and software) that it trusts and knows to be correct (the checksums wouldnt match if your OS was infected for instance) and only allows you access to the content if it trusts your platform including the application which you will use to view the content.
The basic idea as trusted computing was envisioned was to have trust with what hardware and software you communicate with in a distributed computing environment. The idea in itself is very ingenious but the industry has taken it and given it an ugly turn in the form of DRM and yes, it will be enforced on you. The industry will decide what it wants to trust and what it does not want to trust.
The industry will decide what applications you can use to view their content. The industry will decide what OS you will have to run if you need access to their content (because accomodating every OS and every possible patch/mod is going to be extremely hard). So yes, it is evil in a way.
However one should realize that trusted computing in itself as far as the idea goes is not evil - the way it is and will be used by the corporates is definitely evil.
Think of DRM for example when you think of applications. The TC architecture was designed for use in distributed systems (actually the paper that laid the groundwork for it is here: http://research.microsoft.com/lampson/41-DigitalDSSA/41-DigitalDSSAAsPub.pdf) The reason why it can work despite not having every application be certified is that if an application modifies your OS, your OS checksum will fail which means that the TPM will prevent your system from booting (if i remember right - been a few months since I reviewed TC related material). To what extent and what extreme these restrictions on applications are to be placed is exactly what makes TC controversial. Actually, its already taken off. Many new laptops today ship with a TPM. Vista has a significant amount of TPM implemented in it, which although if Im not mistaken, can currently be turned off - correct me on this(this wont be allowed eventually). The digital content industry is looking very seriously into TC and so is the security research community. I studied under a professor who was doing a lot of TC related work in his research. It will not completely fail to take off because it already has to some extent and it has many really big corporates really pushing hard for it, but theres still significant work left. TC is another reason for the open source community to hate the closed source community. You basically wont be able to run a self modded kernel unless it is present in the checksum database with the certifying authority.