Not without a real reason necessarily. I mean you may not be able to hear sub 20hz (most people can't hear below 30, especially as the age group gets older), but you can definitely feel it. The feeling of the lower frequencies can add a lot to the music, because it can add the real "boom" to certain things like cannon fire (used in on some classical concerts before you ask). Though I've never built a system sub 20hz (my current system peaks around 44hz and dips way down in the 30's) myself, I've heard a lower and they are really amazing. Just don't get going on kimber cables...
Thats why I specifically referred to laws that are put together with haste as being riddled with problems, and while not necessarily technologically specific, the PATRIOT act makes an excellent example of this. I'm no lawyer but I'd make a guess that proper laws (or really anything) that has a lot of time and debate put into it will make a better law than something pushed out the door in a few days.
That law has a hard time keeping up with technology. It takes a long time for laws to be made, changed, proven, and stand up in court. It doesn't take nearly as long in the technological world for attacks, defenses, and things in general to change. This is where a lot of the problems are coming from, since most of the time when you get things that are pushed out quickly there are all sorts of acts or laws such as the DMCA or Canadian Do-Not-Call list) which contain all sorts of problems in one way or another. It's just a shame it will take so long for things to really shape up.
Really quite a predicament when too fast means you get poorly written laws, and too slow means the bad guys can work "legally" for a while...
1) Wait for *AA's to make new software announcement
2) Post story with direct link to software on front page
3) Sip coffee as their server crumbles
4) Profit!
I've done only initial programming in MPI for a distributed systems course I took, so keep that in mind. What I think MPI is big for is how popular it is. MPI is a very open standard, has been adopted for a long time, and is used in quite a few research projects because some implementations are heavily optimized. Some of the bonuses of MPI include the ability to make groupings and do group-messages (with all sorts of abilities to combine/redirect group messages), blocking/nonblocking sending receiving (standard really), and its pretty easy to program in. It took me about two days to get a good feel for it and start designing some built-in features the hard way for the assignment, and it worked very well.
You should also note that Wikipedia calls it the "de facto standard", which I agree with (at least from a research pov).
What I was trying to get at is that security really is a tiered setup, your application is only as secure as your system, your system is only as secure as the people working on/around it, etc. Application security helps a lot, but really there are some great things out there that can help plug a lot of holes that attackers can use, and greatly reduce the damage they can cause in the first place. I've taken a particular liking to Hardened Gentoo and similar setups which take a very proactive approach at preventing break-ins. I do agree that people don't seem to be too concerned about it, which was sort of the point I was trying to get at. I don't mind the job security either:)
The article really fails to address any real issue with security. What the article really read like was something more along the lines of, "Six Things Dumb Management Sometimes Do In Relations to Computer Security". The real problem with technical computer security is the poor quality of software (software designed without security, or without enough security in mind), and the general lack of general system protection (NoExec memory, Stack Smashing/Active Bounds Checking, Targetted/Strict ACLs, etc). The damage worms/viruses/hackers can cause on a much stricter system is really far less than a normal system, if the penetration can even be achieved in the first place.
Even though nearly everyone on/. is against this erosion, at least there is some high official somewhere thats being honest about this. Since the governments probably arn't going to listen to rights advocates, I would much prefer to have somebody being straight honest to us. So kudos for that at least.
I believe that the way it works is that you must distribute source to those people that you distribute binaries to. So if say you use something for internal use only within a company, you arn't required to publish the source. And it probably isn't a big deal for them to have a source cd or source download available. Let us also not forget that not everything used in most distros is GPL, as there are plenty of Public Domain/BSD/LGPL licenses out there.
So they are releasing a beta, big whoop? The same thing happens in open source, hell in fact a lot of distros are holding back official reiser4 support until its released in the mainstream kernel. For some people it makes sense to try it out, or to look at what features are available for it that can be developed on. There is a reason it was released on MSDN (Keyword *DEVELOPER NETWORK*) and not to the general public (ie "casual-to-serious users"). As far as I see it, the eventual general usage of WinFS is basically them playing catch up to the fact that NTFS really isn't any good, given XFS/ReiserFS/a million other fs's that are much more efficient and targetted.
What I've encounted with Python is the overwhelming lack of crypto, not necessarily a lack of "security" (I use that term loosely here). What stems from the lack of good default crypto is a sense of a lack of security. For example, the Python SSL implementation has no certificate verification, which is a huge problem for anybody who wants to do any client work. There is also a complete lack of support in most libs for servers (https server? secure xmlrpc server?). This means that you can only half-ass the client side, and the server side is non-existant. While I havn't looked at the framework, I'm hoping that they implemented extra features into the system that makes it a bit better of a choice for security reasons. Right now I'm having a hell of a time trying to get some basic solid crypto security going over xmlrpc.
I mean, I'm sure that these guys are the real thing, judging by their past experience breaking SHA-1 and how much notoriety they have. But they have been inconsistent with presenting information. It would be nice to see something thats really solid with information rather than what looks at best like a bit of speculation. Last I checked information on their last attack (2^69) was still pretty thin and I suppose its time to move on to SHA-256 anyways.
You arn't missing anything. I think its a big problem with the car industry and other fanatics in general (and abstractly a problem with marketing really), instead of touting real benefits of a given product they just tout some numbers that make it sound like its the best thing sinced sliced butter or XOR. The current problem with these hybrids is that they are mostly more expensive than pure gas vehicles, and the costs can't be recouped unless you put in some insane driving time on them. Theres also been a lot of talk about how dangerous the batteries are and how costly it will be to get rid of them once they can't hold a charge anymore. From reading TFA it seems like all this guy did was rig in a bunch of extra batteries to gain some extra mileage, which doesn't really do anything worth a damn, since those batteries still have to be charged. I would be more impressed personally if they had come up with something that allows you to charge the batteries while the vehicles in use (such as the brake-chargers that the Honda hybrids used), or some other technology that makes the batteries more bio-safe/longer lasting. I'm moreso looking forward to seeing progress made in Biodiesal before hybrids/pure electrical, since they attack the problem in (what I feel) is a better manner.
Freshie year of college (not that long ago) I wrote a short research paper on tech patents. Included were statistics showing the influx of patents around the tech boom, and more importantly the acceptance rate of these patents. What you could clearly see is that the acceptance rate was very high, and it wasn't because everybody was innovative. It's because at the time, the patent examiners wern't as technical in the relevant field of the patents they were examining, but this hasn't really changed much up to today. Since patents are mostly written to be over-generalized on purpose, its hard to get a real idea of what the patent is trying to do, and therefore hard to come up with prior art or to determine whether it is innovative, non-obvious, etc. Not even the computer system upgrade and bringing in more patent examiners has appeared to help with the quality of the accepted patents, or the immense backlog of patents thats causing problems.
You had better tell that to all those dbdraggers who run well over 3000wrms. There are plenty of 1000+wrms amps out there (class D), and they do plenty fine with heat. My 600wrms amp (DEI) rarely has heat issues unless its been sitting in the sun, or run for 6 hours straight without much ventilation, and its a few years old. Aside from whats been posted above, most media boxes will probably stay on a lot longer than most persons amps will. I don't know any people in car audio who run their vehicles 24/7 all cranked up. A better comparison would probably be home audio amps, which typically run larger casings and have gigantic heatsinks. It may also be arguable that there are more class A amplifiers in home audio, which would probably be a bit closer to PC power consumption as they are always on, always full.
Probably when the current US Administration no longer has any pesky people to worry about. The way they treat the American people are as if we are all terrorists.
I got into a rather heated battle a while back on HardForum about legal rights on wireless security, and somebody posted up a lot of the FCC guidelines for 802.11[insertflavorhere]. Basically what I got out of it was that as long as you are using FCC approved equipment, its really up to everybody else to figure things out for themselves. I might be wrong on this, but I thought that the FCC tried as hard as it could to keep itself out of situations exactly like this.
So wait, they are going to ban my drinking! What next, no more vodka shots during breaks? Then what, they are going to replace the coke and rum dispenser with WATER!? THEY CAN'T TAKE THAT AWAY FROM ME!
I was at Defcon this year, my first ever, and I can say without reading the article it was a superb event. The number of people there was simply amazing, and most speakers filled or nearly filled out each venue. A few speakers were what I would consider "underdogs", because they didn't get the attention of any large crowd, but were fantastic. The talk on sketchtools and on Meme Mining for Fun/Profit were both excellent. There was a random presentation by the (a?) assistant director of the DoD, which talked a lot about the information grid the DoD is building, and how the DoD wanted to recruit skilled persons.
Theres really too much to talk about in a small blurb here, but hopefully the article comes up soon.
Wrong... wrong... wrong...
I have taken the full tour of Pixar's building and I was really surprised at how many Mac's they had. From what I was told they were doing a lot of visuals on the Macs, rendering them on the clusters, and a lot of tool development was done on Windows. They ran a really mixed shop when I was there because they really don't settle for less, take the tour yourself.
What I meant by "raking in the dough" is that the added publicity, the added usage, and the ability to promote products will likely lead to an increase in profits, which even if they are a "public service", still has meaning.
Slashdot Mirror
Not without a real reason necessarily. I mean you may not be able to hear sub 20hz (most people can't hear below 30, especially as the age group gets older), but you can definitely feel it. The feeling of the lower frequencies can add a lot to the music, because it can add the real "boom" to certain things like cannon fire (used in on some classical concerts before you ask). Though I've never built a system sub 20hz (my current system peaks around 44hz and dips way down in the 30's) myself, I've heard a lower and they are really amazing. Just don't get going on kimber cables...
Thats why I specifically referred to laws that are put together with haste as being riddled with problems, and while not necessarily technologically specific, the PATRIOT act makes an excellent example of this. I'm no lawyer but I'd make a guess that proper laws (or really anything) that has a lot of time and debate put into it will make a better law than something pushed out the door in a few days.
That law has a hard time keeping up with technology. It takes a long time for laws to be made, changed, proven, and stand up in court. It doesn't take nearly as long in the technological world for attacks, defenses, and things in general to change. This is where a lot of the problems are coming from, since most of the time when you get things that are pushed out quickly there are all sorts of acts or laws such as the DMCA or Canadian Do-Not-Call list) which contain all sorts of problems in one way or another. It's just a shame it will take so long for things to really shape up.
Really quite a predicament when too fast means you get poorly written laws, and too slow means the bad guys can work "legally" for a while...
Or maybe its the MPAA/RIAA working hard to prevent future high speed Internet development?
When I last looked into it the protocol allows for MD5 and SHA1, but defaults to SHA1.
1) Wait for *AA's to make new software announcement 2) Post story with direct link to software on front page 3) Sip coffee as their server crumbles 4) Profit!
I've done only initial programming in MPI for a distributed systems course I took, so keep that in mind. What I think MPI is big for is how popular it is. MPI is a very open standard, has been adopted for a long time, and is used in quite a few research projects because some implementations are heavily optimized. Some of the bonuses of MPI include the ability to make groupings and do group-messages (with all sorts of abilities to combine/redirect group messages), blocking/nonblocking sending receiving (standard really), and its pretty easy to program in. It took me about two days to get a good feel for it and start designing some built-in features the hard way for the assignment, and it worked very well.
You should also note that Wikipedia calls it the "de facto standard", which I agree with (at least from a research pov).
What I was trying to get at is that security really is a tiered setup, your application is only as secure as your system, your system is only as secure as the people working on/around it, etc. Application security helps a lot, but really there are some great things out there that can help plug a lot of holes that attackers can use, and greatly reduce the damage they can cause in the first place. I've taken a particular liking to Hardened Gentoo and similar setups which take a very proactive approach at preventing break-ins. I do agree that people don't seem to be too concerned about it, which was sort of the point I was trying to get at. I don't mind the job security either :)
The article really fails to address any real issue with security. What the article really read like was something more along the lines of, "Six Things Dumb Management Sometimes Do In Relations to Computer Security". The real problem with technical computer security is the poor quality of software (software designed without security, or without enough security in mind), and the general lack of general system protection (NoExec memory, Stack Smashing/Active Bounds Checking, Targetted/Strict ACLs, etc). The damage worms/viruses/hackers can cause on a much stricter system is really far less than a normal system, if the penetration can even be achieved in the first place.
Even though nearly everyone on /. is against this erosion, at least there is some high official somewhere thats being honest about this. Since the governments probably arn't going to listen to rights advocates, I would much prefer to have somebody being straight honest to us. So kudos for that at least.
I believe that the way it works is that you must distribute source to those people that you distribute binaries to. So if say you use something for internal use only within a company, you arn't required to publish the source. And it probably isn't a big deal for them to have a source cd or source download available. Let us also not forget that not everything used in most distros is GPL, as there are plenty of Public Domain/BSD/LGPL licenses out there.
So they are releasing a beta, big whoop? The same thing happens in open source, hell in fact a lot of distros are holding back official reiser4 support until its released in the mainstream kernel. For some people it makes sense to try it out, or to look at what features are available for it that can be developed on. There is a reason it was released on MSDN (Keyword *DEVELOPER NETWORK*) and not to the general public (ie "casual-to-serious users"). As far as I see it, the eventual general usage of WinFS is basically them playing catch up to the fact that NTFS really isn't any good, given XFS/ReiserFS/a million other fs's that are much more efficient and targetted.
What I've encounted with Python is the overwhelming lack of crypto, not necessarily a lack of "security" (I use that term loosely here). What stems from the lack of good default crypto is a sense of a lack of security. For example, the Python SSL implementation has no certificate verification, which is a huge problem for anybody who wants to do any client work. There is also a complete lack of support in most libs for servers (https server? secure xmlrpc server?). This means that you can only half-ass the client side, and the server side is non-existant. While I havn't looked at the framework, I'm hoping that they implemented extra features into the system that makes it a bit better of a choice for security reasons. Right now I'm having a hell of a time trying to get some basic solid crypto security going over xmlrpc.
I am self-owned as the paper is actually deep down at the bottom of TFA.
I mean, I'm sure that these guys are the real thing, judging by their past experience breaking SHA-1 and how much notoriety they have. But they have been inconsistent with presenting information. It would be nice to see something thats really solid with information rather than what looks at best like a bit of speculation. Last I checked information on their last attack (2^69) was still pretty thin and I suppose its time to move on to SHA-256 anyways.
You arn't missing anything. I think its a big problem with the car industry and other fanatics in general (and abstractly a problem with marketing really), instead of touting real benefits of a given product they just tout some numbers that make it sound like its the best thing sinced sliced butter or XOR. The current problem with these hybrids is that they are mostly more expensive than pure gas vehicles, and the costs can't be recouped unless you put in some insane driving time on them. Theres also been a lot of talk about how dangerous the batteries are and how costly it will be to get rid of them once they can't hold a charge anymore. From reading TFA it seems like all this guy did was rig in a bunch of extra batteries to gain some extra mileage, which doesn't really do anything worth a damn, since those batteries still have to be charged. I would be more impressed personally if they had come up with something that allows you to charge the batteries while the vehicles in use (such as the brake-chargers that the Honda hybrids used), or some other technology that makes the batteries more bio-safe/longer lasting. I'm moreso looking forward to seeing progress made in Biodiesal before hybrids/pure electrical, since they attack the problem in (what I feel) is a better manner.
Respekt!
Freshie year of college (not that long ago) I wrote a short research paper on tech patents. Included were statistics showing the influx of patents around the tech boom, and more importantly the acceptance rate of these patents. What you could clearly see is that the acceptance rate was very high, and it wasn't because everybody was innovative. It's because at the time, the patent examiners wern't as technical in the relevant field of the patents they were examining, but this hasn't really changed much up to today. Since patents are mostly written to be over-generalized on purpose, its hard to get a real idea of what the patent is trying to do, and therefore hard to come up with prior art or to determine whether it is innovative, non-obvious, etc. Not even the computer system upgrade and bringing in more patent examiners has appeared to help with the quality of the accepted patents, or the immense backlog of patents thats causing problems.
You had better tell that to all those dbdraggers who run well over 3000wrms. There are plenty of 1000+wrms amps out there (class D), and they do plenty fine with heat. My 600wrms amp (DEI) rarely has heat issues unless its been sitting in the sun, or run for 6 hours straight without much ventilation, and its a few years old. Aside from whats been posted above, most media boxes will probably stay on a lot longer than most persons amps will. I don't know any people in car audio who run their vehicles 24/7 all cranked up. A better comparison would probably be home audio amps, which typically run larger casings and have gigantic heatsinks. It may also be arguable that there are more class A amplifiers in home audio, which would probably be a bit closer to PC power consumption as they are always on, always full.
Probably when the current US Administration no longer has any pesky people to worry about. The way they treat the American people are as if we are all terrorists.
I got into a rather heated battle a while back on HardForum about legal rights on wireless security, and somebody posted up a lot of the FCC guidelines for 802.11[insertflavorhere]. Basically what I got out of it was that as long as you are using FCC approved equipment, its really up to everybody else to figure things out for themselves. I might be wrong on this, but I thought that the FCC tried as hard as it could to keep itself out of situations exactly like this.
So wait, they are going to ban my drinking! What next, no more vodka shots during breaks? Then what, they are going to replace the coke and rum dispenser with WATER!? THEY CAN'T TAKE THAT AWAY FROM ME!
Oh wait, what was TFA about again?
I was at Defcon this year, my first ever, and I can say without reading the article it was a superb event. The number of people there was simply amazing, and most speakers filled or nearly filled out each venue. A few speakers were what I would consider "underdogs", because they didn't get the attention of any large crowd, but were fantastic. The talk on sketchtools and on Meme Mining for Fun/Profit were both excellent. There was a random presentation by the (a?) assistant director of the DoD, which talked a lot about the information grid the DoD is building, and how the DoD wanted to recruit skilled persons. Theres really too much to talk about in a small blurb here, but hopefully the article comes up soon.
Wrong... wrong... wrong... I have taken the full tour of Pixar's building and I was really surprised at how many Mac's they had. From what I was told they were doing a lot of visuals on the Macs, rendering them on the clusters, and a lot of tool development was done on Windows. They ran a really mixed shop when I was there because they really don't settle for less, take the tour yourself.
What I meant by "raking in the dough" is that the added publicity, the added usage, and the ability to promote products will likely lead to an increase in profits, which even if they are a "public service", still has meaning.