Very true. But before we get into Nanotubes, we probably should take a look at Fiberglass; it is a
class 2B material according to the IARC. This concerns mainly specialty products like electrical and heat insulation, not so much general home insulation, where, as far as I know, it is the most commonly used insulating material around the world. (but insulating fiber glass is only class 3, so no need to be overly scared). Still, there are saver replacements, high bio soluble fibers. (Wikipedia knows everything)
Just for the sake of discussion, do you think this would work?
- Server (S) has a new patch.
- S sends tokens containing some form of authorization scheme to clients (C). These tokens contain the type of vulnerability, i.e. the type of access needed to the computer in order to exploit it.
- Upon receiving token from S, C checks if tokens are authorized. If yes, it gets paranoid, blocking access to everything specified in the token entirely. This can only be overridden by downloading (or by the local superuser for each single time a blocked access is required, otherwise this would probably be too annoying...)
- C downloads updates from S and releases access.
Slashdot Mirror
Very true. But before we get into Nanotubes, we probably should take a look at Fiberglass; it is a class 2B material according to the IARC. This concerns mainly specialty products like electrical and heat insulation, not so much general home insulation, where, as far as I know, it is the most commonly used insulating material around the world. (but insulating fiber glass is only class 3, so no need to be overly scared). Still, there are saver replacements, high bio soluble fibers. (Wikipedia knows everything)
We do not sell the MicroServer series directly to consumers. D'OOOOHH! Whatamigonnado? I NEED this!!
Just for the sake of discussion, do you think this would work?
- Server (S) has a new patch.
- S sends tokens containing some form of authorization scheme to clients (C). These tokens contain the type of vulnerability, i.e. the type of access needed to the computer in order to exploit it.
- Upon receiving token from S, C checks if tokens are authorized. If yes, it gets paranoid, blocking access to everything specified in the token entirely. This can only be overridden by downloading (or by the local superuser for each single time a blocked access is required, otherwise this would probably be too annoying...)
- C downloads updates from S and releases access.