From TFA: "the Puffin can lift a person with just 60 horsepower."
Again, I'm not saying this specific vehicle is what would be used. I asked if it could be a precursor to future designs. What is to prevent someone from putting higher HP electric motors? The scale on this one is tiny. Imagine putting a little muscle into this.
I'm not implying they could get into orbit with this vehicle as it obviously will require atmosphere for the rotor blades to be effective, but in a general sense. Specifically getting a launch vehicle as far into the atmosphere as possible before switching to a different means of propulsion like a typical rocket.
This is odd that someone hasn't already cashed in on this. Is this a possible precursor to a simple earth to orbit vehicle? From what I read in TFA, the limit quoted is simply due to the capacity of the batteries, however this uses a simple rotary blade system similar to a helicopter for lift. It would definitely fail when the atmosphere thinned out.
Can someone familiar with this type of design give an idea of exactly how high this could be expected to fly if the batteries were not the limiting factor?
Not at all. Your only looking at the end result as evaluating risk from that, and not the vector of infection.
The flash update wasn't 'dismissed' and I noted it was a serious issue, but the fault lies with Flash. It is an abomination.
The MP4 vulnerability would require someone actually get their hands on a specifically crafted MP4. The typical user either creates their own MP4's from their own audio CD's, or downloads them from iTunes on a Mac. If they are getting them from seedy sources, then they pretty much get what they deserve
The last one I wouldn't consider a huge risk simply for the fact that I had never heard of the format. It would require someone that works with raw image data who happens to get an Adobe DNG image that has this vulnerability. This isn't like some drive by hijacking. I don't see this as a likely path to infection.
This is actually a valid complaint, although this link is actually referring to hacking done under Leopard, not Snow Leopard. Snow Leopard is still missing a full implementation of ASLR, and that leaves it vulnerable to some exploits.
Vista was the first Windows OS to implement ASLR, and it was assumed that Snow Leopard would do the same, but that didn't happen, or at least not fully. They have prevented 'data' from being executed as arbitrary code (DEP), but they still don't randomize all of the OS components. Only some key pieces, but not all.
You mean the one with cheaper/slower celeron with less L2 cache, slower DDR2 800 Mhz memory, a cheaper/slower integrated graphics solution, no firewire, a cheaper battery, mono audio speaker, VGA Out Only, no bluetooth standard, no Cam standard, and no optical digital audio output?
Massive Holes? I wouldn't consider any of these critical vulnerabilities, except for the ever so popular Flash sponge.
* CoreAudio (CVE-2010-0036) -- A buffer overflow exists in the handling of mp4 audio files. Playing a maliciously crafted mp4 audio file may lead to an unexpected application termination or arbitrary code execution.
Seems this could crash your audio player.
* CUPS (CVE-2009-3553) -- A use-after-free issue exists in cupsd. By issuing a maliciously crafted get-printer-jobs request, an attacker may cause a remote denial of service. This is mitigated through the automatic restart of cupsd after its termination.
A remote attacker may cause an unexpected application termination of cupsd. I don't see this happening on a home network, and unlikely on a firewalled work network. In any case, an irritant and nothing more.
* Flash Player plug-in (7 vulnerabilities) -- Multiple issues exist in the Adobe Flash Player plug-in, the most serious of which may lead to arbitrary code execution when viewing a maliciously crafted web site. The issues are addressed by updating the Flash Player plug-in to version 10.0.42.
This one unfortunately is serious. Its also due to a flaw in the Adobe Flash Player plug-in.
* ImageIO (CVE-2009-2285) -- A buffer underflow exists in ImageIO's handling of TIFF images. Viewing a maliciously crafted TIFF image may lead to an unexpected application termination or arbitrary code execution.
Crashes your Preview or whatever image viewing app your using.
* Image RAW (CVE-2010-0037) -- A buffer overflow exists in Image RAW's handling of DNG images. Viewing a maliciously crafted DNG image may lead to an unexpected application termination or arbitrary code execution.
I seriously had to look this one up. DNG is apparently an Adobe raw image format. I don't see this one as massive either.
* OpenSSL (CVE-2009-3555) -- A man-in-the-middle vulnerability exists in the SSL and TLS protocols. A change to the renegotiation protocol is underway within the IETF. This update disables renegotiation in OpenSSL as a preventive security measure. The issue does not affect services using Secure Transport as it does not support renegotiation.
This one appears to affect everyone, from OS X, to Windows, to Apache: The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a "plaintext injection" attack, aka the "Project Mogul" issue.
"Anyone within 30 to 50 meters from the cannon will feel like he's standing in front of a firing squad," he said. "He'll feel and hear the blast, but he won't be hurled to the ground. He'll be able to run away unharmed and that's the point of this application."
It seems this will not have much physical force, but will indeed have potential for causing hearing loss.
I had a similar problem with the 27" iMac (ATI Radeon 4850). The fix is actually pretty simple. You just have to delete the vendor specific drivers related to your card so that it gets the generic vga driver instead. After your install is complete you can download and install whatever vendor drivers you need.
I accomplished this in OS X by using NTFS-3G and MacFuse, but you can also just boot into a safe mode command prompt and delete the necessary ATI*.sys drivers from %windir%\system32\drivers (or whatever specific hardware drivers you need to delete).
As to ease of installation, I would say Linux has made huge strides in catching up with the others. The actual install itself is relatively easy, although I would say that OS X and Windows still edges it out, if only barely. Post install, it easily trounces Windows for post install driver support for things like wireless cards and whatnot. The drawback on Linux is if you get into an unknown or unusual hardware configuration, brace yourself, because your about to get a hard lesson in Linux;)
OS X has an advantage here since it uses a closed system, it doesn't typically have to deal with hardware surprises. Of the three, I liked the OS X install the best, followed closely by Windows 7, and then even closer by Linux. This is a huge win for OSS, as it shows what dedication and the love of something can do, without the incentive of money.
"In the interest of interoperability, the display port connection is capable of supporting HDMI/DVI signals.[8] DisplayPort has issued guidelines on the construction of active DisplayPort-to-VGA, DisplayPort-to-SVIDEO/Composite/Other, DisplayPort-to-Dual-Link-DVI/HDMI, and Dual-Link-DVI/HDMI-to-DisplayPort Converters.[citation needed] In addition to active converters, the same guideline document also describes a way for devices supporting both DisplayPort and DVI 1.0 or HDMI to use a single DisplayPort connector for both, using a relatively simple adapter that adjusts for the lower voltages required by the DisplayPort connector. A notable limitation is that this is limited to Single Link DVI/HDMI, and that an active Converter is needed for Dual-Link communication."
The reference for that specific piece of info is here:
I don't see the two as Apples to Apples (no pun intended). Firewire had limited acceptance, mostly in Apple hardware, where DisplayPort seems to be seeing a much larger adoption rate by both GPU manufacturer's and display vendors.
H.264 is simply newer, and supports a wider range of profiles and levels within those profiles, from iPods to far beyond 1080p (4096×2304 if I recall). DivX is also an old format. Your example is kind of like saying MP3 is awesome because your players all support it. It's supported because it's an old established standard.
There is no justification for an $18,000 price difference for what amounts to the same fundamental technology. I don't need a formula, or theories as to why this is. The medical industry is full of a bunch of crooked greedy bastards. They use the same basic technology to accomplish the same result, probably with the very same components, all of which can obviously be had for very cheap. Costs are applied at the component level. If you can buy the same components for a Wii as in this other piece of equipment, their prices should be a bit closer. Our medical system has been gamed so badly for so many years, that a hospital doesn't even blink when they see $18,000 for a piece of equipment. They will happily pass the costs on to the patient, and the patients health insurance.
If this isn't a case of price fixing then I don't know what is.
What we really need is transparency is pricing for all medical costs. Force manufacturer's to provide their component costs for everything like eqiupment, drugs, and consumables, so that the consumer can see exactly what kind of markup their paying for.
This article didn't make sense. It says the student broken no laws, but he was in violatino of school policy? What kind of policy prevents them from bringing in harmless science projects?
"The student will not be prosecuted, but authorities were recommending that he and his parents get counseling, the spokesman said. The student violated school policies, but there was no criminal intent, Luque said."
Why the hell would they recommend counseling for a non-violent and non-criminal act?
Speaker wiring should be at a minimum, shield from external signals and crosstalk. I used to 100+ feet of speaker wire in my home. It used to pick up transmissions of some sort, meaning I could hear audio from the speakers with the stereo turned off. I never could figure out exactly what I was hearing, but it was clearly words of some sort (actually if some one could shed some light on this I would be grateful).
All that said, you can buy decent speaker wire for a few bucks, not $500;)
Not necessarily a rail gun, but specifically the fact that this can produce enough physical force to actually punch through the metal. what happens if you unhinged this 'punch' so that it wasn't anchored and ramped up the force at a slower pace?
I realize this specific implementation would need metal to interact with, but I have to wonder if they can and will eventually learn to interact with gravitational fields from objects like the earth itself.
Someone help me out here as I'm not a physicist, but if this machine produces enough physical force to punch a hole through steel, does it offer any possibility of being used as a propulsive force?
If this launcher is anchored at the surface, how will they compensate for the motion of the waves at the surface? Does that eventually become a non-issue due to the weight of the launcher? How would they 'catch' the cargo once it was launched into orbit? How rigid would such a structure need to be, and are there currents in the ocean that would cause bending stress issues between surface and the deepest parts of the structure?
Slashdot Mirror
Yes, but not all methods are created equal, and quite a few are cheaper than solid rocket fuel.
"The orbital velocity of a satellite depends on its altitude above Earth. The nearer Earth, the faster the required orbital velocity."
Is this accurate?
From TFA: "the Puffin can lift a person with just 60 horsepower."
Again, I'm not saying this specific vehicle is what would be used. I asked if it could be a precursor to future designs. What is to prevent someone from putting higher HP electric motors? The scale on this one is tiny. Imagine putting a little muscle into this.
I'm not implying they could get into orbit with this vehicle as it obviously will require atmosphere for the rotor blades to be effective, but in a general sense. Specifically getting a launch vehicle as far into the atmosphere as possible before switching to a different means of propulsion like a typical rocket.
This is odd that someone hasn't already cashed in on this. Is this a possible precursor to a simple earth to orbit vehicle? From what I read in TFA, the limit quoted is simply due to the capacity of the batteries, however this uses a simple rotary blade system similar to a helicopter for lift. It would definitely fail when the atmosphere thinned out.
Can someone familiar with this type of design give an idea of exactly how high this could be expected to fly if the batteries were not the limiting factor?
Not at all. Your only looking at the end result as evaluating risk from that, and not the vector of infection.
The flash update wasn't 'dismissed' and I noted it was a serious issue, but the fault lies with Flash. It is an abomination.
The MP4 vulnerability would require someone actually get their hands on a specifically crafted MP4. The typical user either creates their own MP4's from their own audio CD's, or downloads them from iTunes on a Mac. If they are getting them from seedy sources, then they pretty much get what they deserve
The last one I wouldn't consider a huge risk simply for the fact that I had never heard of the format. It would require someone that works with raw image data who happens to get an Adobe DNG image that has this vulnerability. This isn't like some drive by hijacking. I don't see this as a likely path to infection.
This is actually a valid complaint, although this link is actually referring to hacking done under Leopard, not Snow Leopard. Snow Leopard is still missing a full implementation of ASLR, and that leaves it vulnerable to some exploits.
Vista was the first Windows OS to implement ASLR, and it was assumed that Snow Leopard would do the same, but that didn't happen, or at least not fully. They have prevented 'data' from being executed as arbitrary code (DEP), but they still don't randomize all of the OS components. Only some key pieces, but not all.
You mean the one with cheaper/slower celeron with less L2 cache, slower DDR2 800 Mhz memory, a cheaper/slower integrated graphics solution, no firewire, a cheaper battery, mono audio speaker, VGA Out Only, no bluetooth standard, no Cam standard, and no optical digital audio output?
Comparable specs?
Massive Holes? I wouldn't consider any of these critical vulnerabilities, except for the ever so popular Flash sponge.
* CoreAudio (CVE-2010-0036) -- A buffer overflow exists in the handling of mp4 audio files. Playing a maliciously crafted mp4 audio file may lead to an unexpected application termination or arbitrary code execution.
Seems this could crash your audio player.
* CUPS (CVE-2009-3553) -- A use-after-free issue exists in cupsd. By issuing a maliciously crafted get-printer-jobs request, an attacker may cause a remote denial of service. This is mitigated through the automatic restart of cupsd after its termination.
A remote attacker may cause an unexpected application termination of cupsd. I don't see this happening on a home network, and unlikely on a firewalled work network. In any case, an irritant and nothing more.
* Flash Player plug-in (7 vulnerabilities) -- Multiple issues exist in the Adobe Flash Player plug-in, the most serious of which may lead to arbitrary code execution when viewing a maliciously crafted web site. The issues are addressed by updating the Flash Player plug-in to version 10.0.42.
This one unfortunately is serious. Its also due to a flaw in the Adobe Flash Player plug-in.
* ImageIO (CVE-2009-2285) -- A buffer underflow exists in ImageIO's handling of TIFF images. Viewing a maliciously crafted TIFF image may lead to an unexpected application termination or arbitrary code execution.
Crashes your Preview or whatever image viewing app your using.
* Image RAW (CVE-2010-0037) -- A buffer overflow exists in Image RAW's handling of DNG images. Viewing a maliciously crafted DNG image may lead to an unexpected application termination or arbitrary code execution.
I seriously had to look this one up. DNG is apparently an Adobe raw image format. I don't see this one as massive either.
* OpenSSL (CVE-2009-3555) -- A man-in-the-middle vulnerability exists in the SSL and TLS protocols. A change to the renegotiation protocol is underway within the IETF. This update disables renegotiation in OpenSSL as a preventive security measure. The issue does not affect services using Secure Transport as it does not support renegotiation.
This one appears to affect everyone, from OS X, to Windows, to Apache: The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a "plaintext injection" attack, aka the "Project Mogul" issue.
I was actually wondering if your browser or dns had been hijacked ;)
No worries...
http://www.networksolutions.com/whois/results.jsp?ip=65.55.207.0
According to TFA:
"Anyone within 30 to 50 meters from the cannon will feel like he's standing in front of a firing squad," he said. "He'll feel and hear the blast, but he won't be hurled to the ground. He'll be able to run away unharmed and that's the point of this application."
It seems this will not have much physical force, but will indeed have potential for causing hearing loss.
I had a similar problem with the 27" iMac (ATI Radeon 4850). The fix is actually pretty simple. You just have to delete the vendor specific drivers related to your card so that it gets the generic vga driver instead. After your install is complete you can download and install whatever vendor drivers you need.
I accomplished this in OS X by using NTFS-3G and MacFuse, but you can also just boot into a safe mode command prompt and delete the necessary ATI*.sys drivers from %windir%\system32\drivers (or whatever specific hardware drivers you need to delete).
As to ease of installation, I would say Linux has made huge strides in catching up with the others. The actual install itself is relatively easy, although I would say that OS X and Windows still edges it out, if only barely. Post install, it easily trounces Windows for post install driver support for things like wireless cards and whatnot. The drawback on Linux is if you get into an unknown or unusual hardware configuration, brace yourself, because your about to get a hard lesson in Linux ;)
OS X has an advantage here since it uses a closed system, it doesn't typically have to deal with hardware surprises. Of the three, I liked the OS X install the best, followed closely by Windows 7, and then even closer by Linux. This is a huge win for OSS, as it shows what dedication and the love of something can do, without the incentive of money.
Not exactly. The converters are needed only for dual-link communications.
"In the interest of interoperability, the display port connection is capable of supporting HDMI/DVI signals.[8] DisplayPort has issued guidelines on the construction of active DisplayPort-to-VGA, DisplayPort-to-SVIDEO/Composite/Other, DisplayPort-to-Dual-Link-DVI/HDMI, and Dual-Link-DVI/HDMI-to-DisplayPort Converters.[citation needed] In addition to active converters, the same guideline document also describes a way for devices supporting both DisplayPort and DVI 1.0 or HDMI to use a single DisplayPort connector for both, using a relatively simple adapter that adjusts for the lower voltages required by the DisplayPort connector. A notable limitation is that this is limited to Single Link DVI/HDMI, and that an active Converter is needed for Dual-Link communication."
The reference for that specific piece of info is here:
http://www.displayport.org/consumer/?q=content/faq
I don't see the two as Apples to Apples (no pun intended). Firewire had limited acceptance, mostly in Apple hardware, where DisplayPort seems to be seeing a much larger adoption rate by both GPU manufacturer's and display vendors.
Version 1.1 of DisplayPort added HDCP support.
Then you would simply need a Displayport to HDMI adapter. You can get one for about $5 - $15 bucks.
H.264 is simply newer, and supports a wider range of profiles and levels within those profiles, from iPods to far beyond 1080p (4096×2304 if I recall). DivX is also an old format. Your example is kind of like saying MP3 is awesome because your players all support it. It's supported because it's an old established standard.
Divx Profiles
H.264 Profiles
In time H.264 will have the same wide support, and moves like this bring that closer. It's a necessary step.
There is no justification for an $18,000 price difference for what amounts to the same fundamental technology. I don't need a formula, or theories as to why this is. The medical industry is full of a bunch of crooked greedy bastards. They use the same basic technology to accomplish the same result, probably with the very same components, all of which can obviously be had for very cheap. Costs are applied at the component level. If you can buy the same components for a Wii as in this other piece of equipment, their prices should be a bit closer. Our medical system has been gamed so badly for so many years, that a hospital doesn't even blink when they see $18,000 for a piece of equipment. They will happily pass the costs on to the patient, and the patients health insurance.
If this isn't a case of price fixing then I don't know what is.
What we really need is transparency is pricing for all medical costs. Force manufacturer's to provide their component costs for everything like eqiupment, drugs, and consumables, so that the consumer can see exactly what kind of markup their paying for.
This article didn't make sense. It says the student broken no laws, but he was in violatino of school policy? What kind of policy prevents them from bringing in harmless science projects?
"The student will not be prosecuted, but authorities were recommending that he and his parents get counseling, the spokesman said. The student violated school policies, but there was no criminal intent, Luque said."
Why the hell would they recommend counseling for a non-violent and non-criminal act?
Is there a better link regarding this article?
Speaker wiring should be at a minimum, shield from external signals and crosstalk. I used to 100+ feet of speaker wire in my home. It used to pick up transmissions of some sort, meaning I could hear audio from the speakers with the stereo turned off. I never could figure out exactly what I was hearing, but it was clearly words of some sort (actually if some one could shed some light on this I would be grateful).
All that said, you can buy decent speaker wire for a few bucks, not $500 ;)
Not necessarily a rail gun, but specifically the fact that this can produce enough physical force to actually punch through the metal. what happens if you unhinged this 'punch' so that it wasn't anchored and ramped up the force at a slower pace?
I realize this specific implementation would need metal to interact with, but I have to wonder if they can and will eventually learn to interact with gravitational fields from objects like the earth itself.
Someone help me out here as I'm not a physicist, but if this machine produces enough physical force to punch a hole through steel, does it offer any possibility of being used as a propulsive force?
If this launcher is anchored at the surface, how will they compensate for the motion of the waves at the surface? Does that eventually become a non-issue due to the weight of the launcher?
How would they 'catch' the cargo once it was launched into orbit?
How rigid would such a structure need to be, and are there currents in the ocean that would cause bending stress issues between surface and the deepest parts of the structure?
I'm sorry, but I find it very hard to believe that a typical /. user would ever believe such tripe. I believe a sound *WOOSH* is in order? ;)