All this means is, the human species will evolve in unison, rather than splintering off into different daughter species. How is this a bad thing?
Monocultures have their own set of issues.
More individuals means more chances for the species to survive. Wasn't there an article a month or so ago that said the human race got knocked down to like 2,000 members or less and almost became extinct?
Wasn't that due to a supervolcano? There are some theories that pure luck has about the same effect as numbers in populations of large mammals. Of course we're apt to nuke each other out of existence for the last spot of habitable land.
The future is 'brown'? What kinda white supremacist shit is this?
Err, again without looking it up.. if you interbred all the different races equally, you'd end up with a brown skin race. Not exactly sure why you think that's white supremacist.
However, silicon is silicon, capacitors are still made from the same things
Thank you for playing the game, but you have lost. Rather then using more expensive Nippon electronics, the Chinese parts you used had a few part per million more impurities. This lead to early thermal failure of your mainboard.
If you would like to play the game again, please acquire more venture capital and buy quality next time. You may still lose the game to your manufacture buying counterfeit parts, using the wrong specification solder, or unforeseen interactions from running at many gigahertz at high temperature.
This show has been hosted by an automation robot that costs 75 times what your laptop does and still has occasional electronics failures.:)
I love these comments the best! "You are only allowed violence by proxy, see if you shoot, stab, or trap an animal you are morally evil and wrong, eternal punishment is the best you deserve. Now if you take that same animal and put it though and equally violent industrial process, well, that's A'O.K."
I eat meat both from the store and that I've hunted, it's still meat. My family are farmers and my mom worked in a slaughterhouse for years.
This is just the same old hypocracy rehashed over and over again.. "I don't believe in guns.. but I'll call the cops and have them shoot you down" or "I don't do X, but I'll gladly take the benefits of the society that does X."
If you don't want to get in legal trouble, you go to court and get such things made de-classified or stripped of confidential status first, then you can reveal whatever you like. The students first step should have been getting a court order to strip protection from the MBTA information, because MBTA actually has some legal precedent on their side here.
Really, instead of going thru all that bullshit, the students should have released all the information first (before the court order). Two times this has happened at DEFCON, and it's easy to do because the offense knows what date you're going to speak and can put a stop to it right before it happens. Not enough time to defend yourself and get the motion dropped. Drop the whitepaper (blackpaper?) on the net a week before the talk, and let them close the barndoors after the horse is already gone.
If this witch hunt gets out of hand, we can expect to see prosecutions for "wiretapping" in cases where suspicious wives install keyloggers to snare their husbands.
From my understanding, it is legal for the wife to 'monitor' the usage of the computer because it is a shared property, aka while they are married she claims ownership of it. Now if she installed the keylogger on a computer (laptop for example) that was owned by his company, but he carried around, she would be in violation.
http://en.wikipedia.org/wiki/DNSSEC is also suprisingly good with a lot of easy to read information, and includes why the current DNSSEC specs may open up more security risks.
example1 >Note that someone could deliberately or inadvertently cause a degradation of service by sending large number of queries for uncached RRs, for example, traversing the NSEC RR chain for a large TLD.
example2>DNSSEC forces the exposure of information that by normal DNS best practice is kept private. NSEC3 drafted in march 2008 may correct this.
Also, most people don't realize that DNSSEC is not an end-to-end security mechanism. It only protects DNS data between an authoritative name server and a caching name server. Currently no operating system resolver libraries that I know of verify that the caching server is providing legitimate results to DNSSEC protected domains. Until your OS or applications provide DNSSEC support, running your own DNSSEC enabled cache is the only way to currently protect your dnssec queries from being forged.
That list my oldest still running djb dnscache install, yes the kernel and glibc have been upgraded around it. The mail server it's on has handled 750k messages per day. Does rdns lookup on smtp connections from servers, from our tests almost every valid smtp mail source has a reverse dns name of some sort. Spambots virus are the largest amount of mail from unnamed IPs.
This being said, if your running out of file descriptors you probably have one of the following issue. -Linux kernel 2.4, Solaris or AIX. (recent bind beta fixes most of this) -Messed up ulimit settings. -Poorly engineered dns caching network.
Trying to run all your clients on a few 'big/fast' caching servers in general is a poor design that uses more bandwidth (to contact the centrally located dns server) and puts the entire userbase at risk if one of the caches does become poisoned. The cable company I worked with realized this years ago and distributed the dns load to each market with at least two dns servers in each city, then more per 'area' as the customer base grew. The boxes were diskless with an extremely stripped linux/glibc installs with dnscache, SSH, and SNMP support. No hard disks let these servers run more like an appliance, they were easily switched out, and rarely suffered failures. Just put the new numbers for the node in the dhcp server and over the period of a day or so as the dhcp clients renewed the load balanced out.
As per D.J.s security suggestions, only ip addresses that belonged to their networks could resolve off the cache. This is significant as many large ISP currently allow anyone to resolve DNS off their networks. Which in the current security context no trickery or fishing is necessary to poison an ISPs cache. A hacker anywhere in the world could poison the cache at their leisure.
They used Bind on there authoritative nameservers, since it fit in with their toolchain, but they turned off the forwarding mode so queries outside of the servers scope would not be resolved.
It's been awhile since I worked there, but I'm sure someone from the network security department after reading the news, called a meeting on how they were going to deal with this issue. I'm sure he may have been surprised when the answer was 'We fixed that 5 years ago'. It's funny, a lot of people wrote off D. J. Bernstein, not because of what he said, but how he said it. Time has now shown he was right, and even Paul Vixie admitted that he was wrong.
Is your plug/home properly grounded? If your not grounded at all or the grounds resistance is too high (25 Ohms is the standard for new housing) your UPS (and surge protector) is worthless as it has no where to dump the surge to and will fault (reset) to protect itself. It sounds like you may already have some wiring issues. http://www.howstuffworks.com/surge-protector.htm is always a good read.
The biggest problem with eating other human beings is that our current society tends to value human life to the point that doing so is a bad plan for your own survival.
The 'moral' issue with human consumption is not the biggest issue, the biological problems are. Take bovine spongiform encephalopathy for example.
A British inquiry into BSE concluded that the epidemic was caused by cattle, who are normally herbivores, being fed the remains of other cattle with mad cow disease in the form of meat and bone meal (MBM), which caused the infectious agent to spread. --from Wikipedia
Eating your own kind is dangerous because you're handling and eating something that carries and spreads the same diseases as you. See http://en.wikipedia.org/wiki/Kuru_epidemic.
Yes, and this is where people fail and security problems come from. FTP is not HTTP. It is a different protocol. Your webbrowser uses a different mechanism to transfer files with it, and it goes over different ports on the internet. Your anti-virus/anti-spyware/firewall doesn't auto-magically block this stuff, it must be programmed to do so. If the programmer didn't think of a mechanism that files could get by the firewall for example, then a virus could get on the network.
Let me create an analogy (and probably get it wrong). You have a jewelry factory that you want to keep secure. You check all incoming and out going employees that arrive in a car for stolen merchandise. A number of semis come and go per day, but you do not perform a security check on them. Where do you think the thief is going to attack?
Slashdot Mirror
Never trust anybody over 25!
All this means is, the human species will evolve in unison, rather than splintering off into different daughter species. How is this a bad thing?
Monocultures have their own set of issues.
More individuals means more chances for the species to survive. Wasn't there an article a month or so ago that said the human race got knocked down to like 2,000 members or less and almost became extinct?
Wasn't that due to a supervolcano? There are some theories that pure luck has about the same effect as numbers in populations of large mammals. Of course we're apt to nuke each other out of existence for the last spot of habitable land.
The future is 'brown'? What kinda white supremacist shit is this?
Err, again without looking it up.. if you interbred all the different races equally, you'd end up with a brown skin race. Not exactly sure why you think that's white supremacist.
However, silicon is silicon, capacitors are still made from the same things
Thank you for playing the game, but you have lost. Rather then using more expensive Nippon electronics, the Chinese parts you used had a few part per million more impurities. This lead to early thermal failure of your mainboard.
If you would like to play the game again, please acquire more venture capital and buy quality next time. You may still lose the game to your manufacture buying counterfeit parts, using the wrong specification solder, or unforeseen interactions from running at many gigahertz at high temperature.
This show has been hosted by an automation robot that costs 75 times what your laptop does and still has occasional electronics failures. :)
Especially if it's Ice 9
We have slaughterhouses for that.
I love these comments the best! "You are only allowed violence by proxy, see if you shoot, stab, or trap an animal you are morally evil and wrong, eternal punishment is the best you deserve. Now if you take that same animal and put it though and equally violent industrial process, well, that's A'O.K."
I eat meat both from the store and that I've hunted, it's still meat. My family are farmers and my mom worked in a slaughterhouse for years.
This is just the same old hypocracy rehashed over and over again.. "I don't believe in guns.. but I'll call the cops and have them shoot you down" or "I don't do X, but I'll gladly take the benefits of the society that does X."
Both are breaking the law, if you go by the letter of the law. You can be ticketed for both. A reasonable judge will toss the 1mph ticket.
Wait, this story is about a guy riding with a drunk driver getting killed...
"and his passenger"
If you choose to ride with a drunk driver, you might die.
From my understanding that was only partial and is missing some key details.
If you don't want to get in legal trouble, you go to court and get such things made de-classified or stripped of confidential status first, then you can reveal whatever you like. The students first step should have been getting a court order to strip protection from the MBTA information, because MBTA actually has some legal precedent on their side here.
Really, instead of going thru all that bullshit, the students should have released all the information first (before the court order). Two times this has happened at DEFCON, and it's easy to do because the offense knows what date you're going to speak and can put a stop to it right before it happens. Not enough time to defend yourself and get the motion dropped. Drop the whitepaper (blackpaper?) on the net a week before the talk, and let them close the barndoors after the horse is already gone.
If this witch hunt gets out of hand, we can expect to see prosecutions for "wiretapping" in cases where suspicious wives install keyloggers to snare their husbands.
From my understanding, it is legal for the wife to 'monitor' the usage of the computer because it is a shared property, aka while they are married she claims ownership of it. Now if she installed the keylogger on a computer (laptop for example) that was owned by his company, but he carried around, she would be in violation.
I never said I didn't reboot, this was the install date. I've used DJBDNS before that, but all of those servers have been replaced.
Cryptography is not magic.
While I don't expect the AC to read this, it lays out why we are not going to see DNSSEC for some time. http://www.internetnews.com/security/article.php/3758566/Is+DNSSEC+the+Answer+to+Internet+Security.htm
http://en.wikipedia.org/wiki/DNSSEC is also suprisingly good with a lot of easy to read information, and includes why the current DNSSEC specs may open up more security risks.
example1 >Note that someone could deliberately or inadvertently cause a degradation of service by sending large number of queries for uncached RRs, for example, traversing the NSEC RR chain for a large TLD.
example2>DNSSEC forces the exposure of information that by normal DNS best practice is kept private. NSEC3 drafted in march 2008 may correct this.
Also, most people don't realize that DNSSEC is not an end-to-end security mechanism. It only protects DNS data between an authoritative name server and a caching name server. Currently no operating system resolver libraries that I know of verify that the caching server is providing legitimate results to DNSSEC protected domains. Until your OS or applications provide DNSSEC support, running your own DNSSEC enabled cache is the only way to currently protect your dnssec queries from being forged.
6 root root 4096 2002-10-11 11:10 dnscache
That list my oldest still running djb dnscache install, yes the kernel and glibc have been upgraded around it. The mail server it's on has handled 750k messages per day. Does rdns lookup on smtp connections from servers, from our tests almost every valid smtp mail source has a reverse dns name of some sort. Spambots virus are the largest amount of mail from unnamed IPs.
This being said, if your running out of file descriptors you probably have one of the following issue.
-Linux kernel 2.4, Solaris or AIX. (recent bind beta fixes most of this)
-Messed up ulimit settings.
-Poorly engineered dns caching network.
Trying to run all your clients on a few 'big/fast' caching servers in general is a poor design that uses more bandwidth (to contact the centrally located dns server) and puts the entire userbase at risk if one of the caches does become poisoned. The cable company I worked with realized this years ago and distributed the dns load to each market with at least two dns servers in each city, then more per 'area' as the customer base grew. The boxes were diskless with an extremely stripped linux/glibc installs with dnscache, SSH, and SNMP support. No hard disks let these servers run more like an appliance, they were easily switched out, and rarely suffered failures. Just put the new numbers for the node in the dhcp server and over the period of a day or so as the dhcp clients renewed the load balanced out.
As per D.J.s security suggestions, only ip addresses that belonged to their networks could resolve off the cache. This is significant as many large ISP currently allow anyone to resolve DNS off their networks. Which in the current security context no trickery or fishing is necessary to poison an ISPs cache. A hacker anywhere in the world could poison the cache at their leisure.
They used Bind on there authoritative nameservers, since it fit in with their toolchain, but they turned off the forwarding mode so queries outside of the servers scope would not be resolved.
It's been awhile since I worked there, but I'm sure someone from the network security department after reading the news, called a meeting on how they were going to deal with this issue. I'm sure he may have been surprised when the answer was 'We fixed that 5 years ago'. It's funny, a lot of people wrote off D. J. Bernstein, not because of what he said, but how he said it. Time has now shown he was right, and even Paul Vixie admitted that he was wrong.
Is your plug/home properly grounded? If your not grounded at all or the grounds resistance is too high (25 Ohms is the standard for new housing) your UPS (and surge protector) is worthless as it has no where to dump the surge to and will fault (reset) to protect itself. It sounds like you may already have some wiring issues. http://www.howstuffworks.com/surge-protector.htm is always a good read.
Thank goodness I took ownership of /sbin/init.
Not if I call them first... here take the little shit.
number of posts != quality of content.
Yea, it's not like the drunk would ever think to carry a SECOND SET OF KEYS :)
It's called a dark cutter. It's not a good thing the majority of the time.
http://www.ext.vt.edu/news/periodicals/livestock/aps-98_03/aps-891.html
The 'moral' issue with human consumption is not the biggest issue, the biological problems are. Take bovine spongiform encephalopathy for example.
A British inquiry into BSE concluded that the epidemic was caused by cattle, who are normally herbivores, being fed the remains of other cattle with mad cow disease in the form of meat and bone meal (MBM), which caused the infectious agent to spread. --from Wikipedia
Eating your own kind is dangerous because you're handling and eating something that carries and spreads the same diseases as you. See http://en.wikipedia.org/wiki/Kuru_epidemic.
Awesome, now I can finally create the fabled Grey Goo!
>Sounds all about the same to me.
Yes, and this is where people fail and security problems come from. FTP is not HTTP. It is a different protocol. Your webbrowser uses a different mechanism to transfer files with it, and it goes over different ports on the internet. Your anti-virus/anti-spyware/firewall doesn't auto-magically block this stuff, it must be programmed to do so. If the programmer didn't think of a mechanism that files could get by the firewall for example, then a virus could get on the network.
Let me create an analogy (and probably get it wrong). You have a jewelry factory that you want to keep secure. You check all incoming and out going employees that arrive in a car for stolen merchandise. A number of semis come and go per day, but you do not perform a security check on them. Where do you think the thief is going to attack?
Yes because http is the best way to download a directory of uncompressed files all at once
Stuffing everything in a big compressed file sucks for dial up users, ftp has its purpose.
http://xkcd.com/327/
John;')DROP DATABASE users;--Right, so your ISP can intercept your plan text traffic and build a profile of what your communicating about instead.