1. Buy the honeypot from this Van Strien fellow, packaged as "a security tool for corporate Wi-Fi users" with "a beautiful user interface". Estimated cost: _____ 2. Maintain it. Estimated cost: ______ per month. 3. Keep someone on the payroll to watch for suspicious activity. Estimated cost: _____ per month. 4. When suspicious activity is found.... um... what exactly do you do then?
Alternative 2: 1. Let laptop users connect through Wi-Fi to the company's VPN server, just like the road warriors. Nothing except this server is accessible through the wireless network. Estimated cost: _____
Would anyone fill in the blanks for me? I want to see which one is more cost-effective.
I've seen comments about pacemakers and safety of this technology. Quoted from the page above: The current used is one-billionth of an amp (one nanoamp), which is lower than the natural currents already in the body. In fact, the electrical field created by running a comb through hair is more than 1,000 times greater than that being used by PAN technology.
About a third of the population of Swaziland is muslim. I'm pretty sure the name Sakila comes to SiSwati from the Arabic word Shakila which means beautiful or handsome (Shaquille is the masculine form of the same name).
Let NASA commercialize their cutting-edge stuff but for crissake get NASA out of the launching business. Let them deploy probes to other planets, study the Earth and environment, develop advanced interplanetary propulsion concepts, build space habitats, study space medicine - but don't let them anywhere near the drawing board of a launch vehicle. Ground to LEO transport should be off-limits for NASA.
Cargo launch vehicles don't need to be cutting edge. They don't need to be advanced - they need to be dumb, big, reliable andcheap. Crew space taxis need to be ultra-reliable, small and relatively cheap. NASA is apparently incapable of achieving any of these goals.
Subsidizing shuttle payloads has nearly killed the private space industry. Instead of competing with it with tax dollars NASA should promote it by buying launch services.
See this report by Lt. Col. John R. London III to find the historical reasons for the cost of launching and how it can be drastically reduced.
There is a lot of interest recently in stratosphereric platforms as an alternative to satellites, both heavier and lighter than air.
Geostationary satellites are too far to support high data rates to mobile terminals and also suffer from high latency. LEO satellites require an entire constellation covering most of the Earth before there is continous coverage in any part of the Earth. This all-or-nothing property makes it a dangerous business proposition.
This kind of system may be more resistant to technical problems like DoS, but I think that it's much more important for it to be resistant to political problems.
No, I am not talking about legal problems like court orders. If the system as any central point there is the problem of who gets to control it. With no center it will be much easier for everyone to agree on the protocol without endless politicking.
In 1500, Europe was a shithole. It would still be a shithole today if Europeans didn't colonize the rest of the world, steal the resources, and bring the resources back to Europe.
And they used these stolen resources to get a lot of people hooked on all kinds of luxuries and a higher standard of living. They used the stolen resources and slavery to create a middle class where before there was only a small high class and the rest of the population were extremely poor.
Lots of poor people are not consumers. A small number of very rich people are not consumers either. Only the middle class make effective consumers and made it possible to bootstrap an industrial revolution.
Without the fruits of this industrial revolution the countries robbed by colonization could not have fed their exponentially growing populations so in a way they are getting some compensation for the cruelty and injustice inflicted upon them by colonization.
The KDE equivalent of the open command is kfmclient. Unfortunately, it takes URLs as arguments, not filenames or urls with no protocol prefix. Here's a little script called 'k' that wraps kfmclient with a more friendly interface.
It may be cleaner than gasoline powered cars - but is it safe?
Four tanks of compressed air at 4500psi contain a lot of potential energy. If they rupture in a car crash this energy will be released in an instant, spraying their surroundings with shrapnel. Sure, a tank full of gasoline isn't exactly benign, either, but outside of Hollywood cars generally do not explode in a fireball.
You must be confusing "voice over IP" with "crappy free telephone calls over the public internet". Voice over IP in a controlled private network can have strict QoS guarantees on latency, jitter and packet loss. VoIP is actually used by many millions of people, most of them don't even know it.
Cellular networks use voice compression codecs that must accumulate a complete block of samples before compressing and transmitting it. They also use heavy error correction. Both of these factors introduces a very significant latency. If the voice compression blocks, error correction blocks and VoIP packets are all in sync some of these latencies overlap instead of adding up and it may not add any significant additional latency.
There's an interesting use of 802.11b technology at Vocera. It's a small device you can hang on your shirt like a Star-Trek communicator that uses wireless network infrastructure and voice recognitioh.
A TCP implementation that generates initial sequence numbers using a trivial time dependency may be secure against sequence number guessing attacks if it implements RFC 1948.
The idea is to add a bias to the sequence numbers that depends on the source address. A client will be able to predict his own sequence numbers but not the sequence numbers of others. The bias is calculated using a cryptographic hash of the connection ID and a secret value.
A TCP implementation that uses RFC 1948 may still get a very poor rating for initial sequence number predictability from tools like nmap.
Does anyone know any TCP stack that actually implements it?
Remember that methane is one of the most common gasses in the solar system - the gas giants are largely made of methane. During the formation of the Earth a lot of gasses got trapped in it and it is constantly outgassing.
"...the great earthquake in San Francisco in 1906 was accompanied by large fires, and it was said at the time that this was due to the fracture of gas pipes in the ground. That may well have been the case; however flames were also seen on hills nearby that had no gas pipes and also on roads and fields in nearby San Jose. The Armenian earthquake of 1990 showed a line of burnt bushes along a visible faultline."
When this happens on the ocean floor the methane may combine with water under high pressure and low temperatures to make "methane ice" and chemosynthetic bacteria and methane ice worms live in it!
What I see very well is products that don't satisfy their intended audience because their embedded software sucks. This is happening more often than 12 years ago.
Why is this happening? My guess is that since the hardware is much more powerful engineers are tempted to try to do much more in each product. The problem is that quality software development management hasn't caught up with the increase in hardware capacity.
In other words, engineers have lost the ability to think simple.
What was "state of the art" in the '80s is now ubiquitous and hidden from the end user.
It's apparently so well hidden that it does not affect overall customer satisfaction.
Has your car ever shut down because its computer crashed?
No, but it has been doing really wierd things with the idle RPMs on cold start and in five visits to the garage the mechanic has never been able to pinpoint the problem. Resetting the computer helps for while, though.
These are all cases of coding like you described - Fitting as much as possible into as little space as possible.
Sure there are, but there are also many cases where an embedded device gets a 32 bit RISC cpu with a few megabytes of flash ROM, a few hundred ks of RAM, a realtime operating system, multiple threads, multiple programmers, bloatware, bugs, endlessly stretching schedules, etc when a 8 bit micro with 32k of of ROM would have been enough..
I'd like to see an audio encoding comparison test conducted this way:
Source material: About 50 clips, 20 seconds each representing a variety of musical styles. Two thirds should be normal music and the rest will be material that is known to be difficult to encode using psychoacoustic encoding.
Bit rates: each encoding will be tested at multiple bit rates. The purpose is to find the threshold at which the codec is indistinguishable from PCM. Another interesting threshold is the bit rate at which the codec can be distinguished from PCM but the artifacts are not annoying.
Media: Material will be encoded and decoded back to PCM and recorded onto CD-Rs. Listeners will listen to them on their favorite high-quality audio gear, not through a sound card and PC speakers.
CD-Rs are numbered and individually customized. All disks will have the same order of sound clips, but each one will be encoded with a different encoder/bitrate. Disks may be mailed to listeners and the results gathered by a web form.
The clips will be divided into two groups. The first group is designed to detect the bitrate threshold for each codec where the result is indistinguishable from the PCM source. Each clip will appear three times on the disk using the R/A/B methodology: R is the reference (original PCM), one of A or B is the encoded/decoded clip and the other is identical to the reference. The listeners will need to answer whether A or B is the original.
The result for each codec will be the bitrate at which listeners were not able do discern with any statistical significance the difference between the encoded and original PCM.
The second set of tests is for rating bitrates below the threshold of indistinguishability. Each clip will appear twice: first the reference then the same clip encoded by some unknown codec/bitrate combination. The listeners will rate them on a subjective scale of 1 to 5:
1. The quality of the encoded clip is inadequate. 2. The encoded has noticable annoying artifacts but it is still adequate for enjoying the music in situations where a higher rate is not practical. 3. The encoded clip has a noticably lower quality but is not annoying in any way. 4. Different, but it is not possible to really tell which one is better. 5. Indistinguishable from the source.
Results for each codec/bitrate will be averaged for all clips and presented as a graph. Results for normal and known-hard clips may also be displayed separately.
I used to work with military electronics and found that the best gear was always from the 80s. The stuff from the 60s and 70s (yes, some of that is still in service) was too primitive. The 90s hardware was too complicated and suffered from unreliable software.
In the 80s the microcontroller technology was just good enough to embed a processor with 64k of ROM full of finely crafted code written by a single programmer and it always just worked, perfectly, every time.
There is an important difference between my SCSI chain and an IP network - you won't find many SCSI chains with the kinds of security threats that are quite common on networks these days. Remember that block devices live below the OS permissions level - it's deeper than root access.
I hope that iSCSI has good security measures *enabled by default*. I remember some discussion on iSCSI mailing lists about using SRP and potential intellectual property problems. I hope it's in the final standard.
I was wondering whether the sad news made it in time for the WorldCon, considering the fact that the helicopter crash took place on the last day of ConJose.
If you got the chance to know filkers you'll know that the filksings in his memory must have been a very moving experience. I always found it amazing how filk can combine the utmost in sarcasm, cynicism and irony with the most romantic, sentimental and heroic.
A remote control that sends a narrow beam to a long distance with the "turn off" codes of most popular TV models. If it has good sights and a narrow beam I bet it could do it from a distance of well over 100 meters.
Slashdot Mirror
Alternative 1:
1. Buy the honeypot from this Van Strien fellow, packaged as "a security tool for corporate Wi-Fi users" with "a beautiful user interface". Estimated cost: _____
2. Maintain it. Estimated cost: ______ per month.
3. Keep someone on the payroll to watch for suspicious activity. Estimated cost: _____ per month.
4. When suspicious activity is found.... um... what exactly do you do then?
Alternative 2:
1. Let laptop users connect through Wi-Fi to the company's VPN server, just like the road warriors. Nothing except this server is accessible through the wireless network. Estimated cost: _____
Would anyone fill in the blanks for me? I want to see which one is more cost-effective.
ZIRE: an extinct language of New Caledonia
SIL code: SIH
Region: Bourail, coastal plain.
Alternate names: ZIRA, SIRHE, SICHE, SÎSHËË, NERË
Classification: Austronesian, Malayo-Polynesian, Central-Eastern, Eastern Malayo-Polynesian, Oceanic, Central-Eastern Oceanic, Remote Oceanic, New Caledonian, Southern, South, Zire-Tiri.
Comments: Zire is reported to be extinct. No mother tongue speakers. There are apparently a few who learned it as second language. Grammar. Extinct.
Personal Area Networks.
I've seen comments about pacemakers and safety of this technology. Quoted from the page above:
The current used is one-billionth of an amp (one nanoamp), which is lower than the natural currents already in the body. In fact, the electrical field created by running a comb through hair is more than 1,000 times greater than that being used by PAN technology.
On vacation.
About a third of the population of Swaziland is muslim. I'm pretty sure the name Sakila comes to SiSwati from the Arabic word Shakila which means beautiful or handsome (Shaquille is the masculine form of the same name).
Let NASA commercialize their cutting-edge stuff but for crissake get NASA out of the launching business. Let them deploy probes to other planets, study the Earth and environment, develop advanced interplanetary propulsion concepts, build space habitats, study space medicine - but don't let them anywhere near the drawing board of a launch vehicle. Ground to LEO transport should be off-limits for NASA.
Cargo launch vehicles don't need to be cutting edge. They don't need to be advanced - they need to be dumb, big, reliable andcheap. Crew space taxis need to be ultra-reliable, small and relatively cheap. NASA is apparently incapable of achieving any of these goals.
Subsidizing shuttle payloads has nearly killed the private space industry. Instead of competing with it with tax dollars NASA should promote it by buying launch services.
See this report by Lt. Col. John R. London III to find the historical reasons for the cost of launching and how it can be drastically reduced.
There is a lot of interest recently in stratosphereric platforms as an alternative to satellites, both heavier and lighter than air.
Geostationary satellites are too far to support high data rates to mobile terminals and also suffer from high latency. LEO satellites require an entire constellation covering most of the Earth before there is continous coverage in any part of the Earth. This all-or-nothing property makes it a dangerous business proposition.
Some links:
StratSat
CargoLifter and Boeing
Yokosuka
AeroVironment
This kind of system may be more resistant to technical problems like DoS, but I think that it's much more important for it to be resistant to political problems.
No, I am not talking about legal problems like court orders. If the system as any central point there is the problem of who gets to control it. With no center it will be much easier for everyone to agree on the protocol without endless politicking.
In 1500, Europe was a shithole. It would still be a shithole today if Europeans didn't colonize the rest of the world, steal the resources, and bring the resources back to Europe.
And they used these stolen resources to get a lot of people hooked on all kinds of luxuries and a higher standard of living. They used the stolen resources and slavery to create a middle class where before there was only a small high class and the rest of the population were extremely poor.
Lots of poor people are not consumers. A small number of very rich people are not consumers either. Only the middle class make effective consumers and made it possible to bootstrap an industrial revolution.
Without the fruits of this industrial revolution the countries robbed by colonization could not have fed their exponentially growing populations so in a way they are getting some compensation for the cruelty and injustice inflicted upon them by colonization.
The KDE equivalent of the open command is kfmclient. Unfortunately, it takes URLs as arguments, not filenames or urls with no protocol prefix. Here's a little script called 'k' that wraps kfmclient with a more friendly interface.
It may be cleaner than gasoline powered cars - but is it safe?
Four tanks of compressed air at 4500psi contain a lot of potential energy. If they rupture in a car crash this energy will be released in an instant, spraying their surroundings with shrapnel. Sure, a tank full of gasoline isn't exactly benign, either, but outside of Hollywood cars generally do not explode in a fireball.
You must be confusing "voice over IP" with "crappy free telephone calls over the public internet". Voice over IP in a controlled private network can have strict QoS guarantees on latency, jitter and packet loss. VoIP is actually used by many millions of people, most of them don't even know it.
Cellular networks use voice compression codecs that must accumulate a complete block of samples before compressing and transmitting it. They also use heavy error correction. Both of these factors introduces a very significant latency. If the voice compression blocks, error correction blocks and VoIP packets are all in sync some of these latencies overlap instead of adding up and it may not add any significant additional latency.
There's an interesting use of 802.11b technology at Vocera. It's a small device you can hang on your shirt like a Star-Trek communicator that uses wireless network infrastructure and voice recognitioh.
LINE runs a single linux executable under Windows while UML runs an entire Linux kernel.
BIOS == Built In Obsolete Software
A TCP implementation that generates initial sequence numbers using a trivial time dependency may be secure against sequence number guessing attacks if it implements RFC 1948.
The idea is to add a bias to the sequence numbers that depends on the source address. A client will be able to predict his own sequence numbers but not the sequence numbers of others. The bias is calculated using a cryptographic hash of the connection ID and a secret value.
A TCP implementation that uses RFC 1948 may still get a very poor rating for initial sequence number predictability from tools like nmap.
Does anyone know any TCP stack that actually implements it?
(quoted from Thomas Gold)
When this happens on the ocean floor the methane may combine with water under high pressure and low temperatures to make "methane ice" and chemosynthetic bacteria and methane ice worms live in it!
You just don't see it.
What I see very well is products that don't satisfy their intended audience because their embedded software sucks. This is happening more often than 12 years ago.
Why is this happening? My guess is that since the hardware is much more powerful engineers are tempted to try to do much more in each product. The problem is that quality software development management hasn't caught up with the increase in hardware capacity.
In other words, engineers have lost the ability to think simple.
What was "state of the art" in the '80s is now ubiquitous and hidden from the end user.
It's apparently so well hidden that it does not affect overall customer satisfaction.
Has your car ever shut down because its computer crashed?
No, but it has been doing really wierd things with the idle RPMs on cold start and in five visits to the garage the mechanic has never been able to pinpoint the problem. Resetting the computer helps for while, though.
These are all cases of coding like you described - Fitting as much as possible into as little space as possible.
Sure there are, but there are also many cases where an embedded device gets a 32 bit RISC cpu with a few megabytes of flash ROM, a few hundred ks of RAM, a realtime operating system, multiple threads, multiple programmers, bloatware, bugs, endlessly stretching schedules, etc when a 8 bit micro with 32k of of ROM would have been enough..
I'd like to see an audio encoding comparison test conducted this way:
Source material: About 50 clips, 20 seconds each representing a variety of musical styles. Two thirds should be normal music and the rest will be material that is known to be difficult to encode using psychoacoustic encoding.
Bit rates: each encoding will be tested at multiple bit rates. The purpose is to find the threshold at which the codec is indistinguishable from PCM. Another interesting threshold is the bit rate at which the codec can be distinguished from PCM but the artifacts are not annoying.
Media: Material will be encoded and decoded back to PCM and recorded onto CD-Rs. Listeners will listen to them on their favorite high-quality audio gear, not through a sound card and PC speakers.
CD-Rs are numbered and individually customized. All disks will have the same order of sound clips, but each one will be encoded with a different encoder/bitrate. Disks may be mailed to listeners and the results gathered by a web form.
The clips will be divided into two groups. The first group is designed to detect the bitrate threshold for each codec where the result is indistinguishable from the PCM source. Each clip will appear three times on the disk using the R/A/B methodology: R is the reference (original PCM), one of A or B is the encoded/decoded clip and the other is identical to the reference. The listeners will need to answer whether A or B is the original.
The result for each codec will be the bitrate at which listeners were not able do discern with any statistical significance the difference between the encoded and original PCM.
The second set of tests is for rating bitrates below the threshold of indistinguishability. Each clip will appear twice: first the reference then the same clip encoded by some unknown codec/bitrate combination. The listeners will rate them on a subjective scale of 1 to 5:
1. The quality of the encoded clip is inadequate.
2. The encoded has noticable annoying artifacts but it is still adequate for enjoying the music in situations where a higher rate is not practical.
3. The encoded clip has a noticably lower quality but is not annoying in any way.
4. Different, but it is not possible to really tell which one is better.
5. Indistinguishable from the source.
Results for each codec/bitrate will be averaged for all clips and presented as a graph. Results for normal and known-hard clips may also be displayed separately.
I used to work with military electronics and found that the best gear was always from the 80s. The stuff from the 60s and 70s (yes, some of that is still in service) was too primitive. The 90s hardware was too complicated and suffered from unreliable software.
In the 80s the microcontroller technology was just good enough to embed a processor with 64k of ROM full of finely crafted code written by a single programmer and it always just worked, perfectly, every time.
There is an important difference between my SCSI chain and an IP network - you won't find many SCSI chains with the kinds of security threats that are quite common on networks these days. Remember that block devices live below the OS permissions level - it's deeper than root access.
I hope that iSCSI has good security measures *enabled by default*. I remember some discussion on iSCSI mailing lists about using SRP and potential intellectual property problems. I hope it's in the final standard.
I was wondering whether the sad news made it in time for the WorldCon, considering the fact that the helicopter crash took place on the last day of ConJose.
If you got the chance to know filkers you'll know that the filksings in his memory must have been a very moving experience. I always found it amazing how filk can combine the utmost in sarcasm, cynicism and irony with the most romantic, sentimental and heroic.
i think this technique is for the geel of it, not really for the practicality.
Never heard this one before. If it's a typo you may have just coined new jargon.
But the retaining wires sure beat the tiny screws!
Oren
A remote control that sends a narrow beam to a long distance with the "turn off" codes of most popular TV models. If it has good sights and a narrow beam I bet it could do it from a distance of well over 100 meters.