Little-known? It's been in Clancy's books for a couple of decades, as well as many other military-thriller author's books. It's been documented six ways from sideways since way back into the Cold War.
Little-known because folks don't pay any attention at all outside of military circles, but even though it's probably still under some level of Classification, it's certainly well-known by even the laziest military-thriller or "President deals with a crisis" fictional novel reader since the late 1980's at least.
The "Mrs. Degree" isn't as popular as it once was, but no doubt there's people out there pursuing it. It should be updated to the "Mr. or Mrs. Degree" these days.
Just look at the god-awful mess GNOME just became again, outside of kernel-space. Or try to get LDAP authentication working on 100 servers already running on different distros.
Linux can't even hack centralized authentication properly yet. I love Linux and working on it, but it's kludge on top of kludge. Those that work, do so pretty well. The rest is a mess.
Ahh, been using Linux since 1995. Never seen that "more solid" thing come out of open-source yet.
Reason is, most devs don't look at code, they write it. Looking at someone's old code and trying to fix it is something a smaller percentage of devs do than those who just slap more code out.
Linux's stability lies in the original design (UNIX), not so much in the "many eyes/many hands" thing. That and distros who are willing to slow the process so businesses can actually use the stuff.
And the most stable things on Linux aren't so much the OS, as they are great applications which somehow have stood the test of time... Apache comes to mind...
VxWorks or Microware OS/9 still kick Linux's butt in the RTOS world for reliability and strength/stability of codebase. Just sayin'... if you're building missile systems, you're probably reaching for one of those.
And you only get a +2...? I'm not surprised, I guess. But you're right. Government is always controlled by whoever buys the politicians. That's pretty clear from history.
Name a single large software package that hasn't had at least one major serious screw-up like this in the last few years. The industry's retarded to keep allowing code to be handled as if it weren't real engineering with building codes, inspectors, etc.
The law of unintended consequences will join in on this one very soon, and there'll be a rash of beer-can thin aluminum 100 MPG econo-boxes crushed along with their contents by everything else on the road since fleets don't turn over that quickly.
The news media will only focus on the trucks and truck-body SUVs that some of us actually have real uses for, like towing and off-road locations that we really do need to get to, as the "cause" of the problem.
The retardedness continues. Have you seen the NHTSA video of what happens to a "Smart"Car (quotation marks added) when it's hit in a quartering head-on with a standard four-door sedan? Hint: Launch in T-minus... 3... 2... 1... it not only gets clobbered, it also has its direction *reversed* by the much larger mass.
I was hoping that scientists would point out that basing anything in life on a *model* (either their "good one" or the other guy's "bad one" (take your pick) is not science. It's religion.
In Jerry's day, you couldn't location-shift at will via inexpensive telecommunications links. You're temporarily shifting cultures today every time you answer or place a phone call.
A huge notable ISP or government would have to start this... someplace everyone wants to send mail through or to... Gmail would be perfect.
- Enable TLS on your inbound mail server. Start immediately tracking mail servers that fall into these categories:... Use TLS properly and identify themselves with properly signed keys from a third-party source.... Use TLS for encryption using self-signed keys.... Don't use TLS.
- Immediately filter out servers that are dumb enough to use TLS as spam senders. (The really dumb one's.) - Notify all senders that after X date, ONLY TLS enabled servers will be able to communicate with your domain or through it. - Notify all senders that after Y date, ONLY TLS enabled servers with properly signed keys will be able to communicate.
Yup, it means a metric ton of CPU upgrades or TLS front-ends need to be put in front of large mail farms.
But if you can identify every server that talks to yours and/or block the servers and or keys that are known to have been compromised, spam drops to an annoyance. SpamAssassin and other services are far less likely to even be needed but can still backstop the process, and all sorts of good things happen.
Why mail server authentication and encryption haven't taken off yet on a massive scale, is only a matter of willpower by one huge entity willing to make the sacrifice of "guess we won't get mail from servers that can't identify themselves properly with PKI". Once it's in place, you just block servers you don't ever want mail from and you have traceable IDs for all the rest.
It's possible. No one has the cojones to do it at a place like Google or Amazon or some large branch of government. Make TLS mandatory to e-mail information about government bids to their procurement people, every large company in the U.S. with government contracts would cost-justify it overnight and deploy it.
Why should mail servers still be running SMTP unauthenticated and unencrypted in 2011? Browsers have been doing SSL for how long?
It's far better to make up crap out of thin air, of course.
And far wiser to assume that they just didn't give a flying leap until someone showed them numbers on paper and they either didn't want to be embarrassed or wanted to impress someone with their energy-saving savvy.
Which they could have done if they'd walked their building even once at night, or even just had the forethought to ask if the HVAC was on 24/7.
Seen plenty of real-world managers ask that question without being prompted by a fancy monitoring system. Seen hotel managers crunch the numbers on energy efficient light bulbs. The difference here is there's no profit motive and they're spending other people's money.
The study just gave light to the truth of what they were wasting and a political reason to change it. Typical government job laziness and ineptitude.
Shouldn't the accountant and department that pays the energy bill for the entire school district have already found this and implemented it? Yup.
Ha. You've never seen the replacement budget for a Corporate IT department. The best laptops should go to those without children, judging by the destruction reason list.
Little off there. My employer was giving away P3 machines by the pallet by 2006 to employees and charities..P4s were given away by pulling names out of hats.
Slashdot Mirror
Little-known? It's been in Clancy's books for a couple of decades, as well as many other military-thriller author's books. It's been documented six ways from sideways since way back into the Cold War.
Little-known because folks don't pay any attention at all outside of military circles, but even though it's probably still under some level of Classification, it's certainly well-known by even the laziest military-thriller or "President deals with a crisis" fictional novel reader since the late 1980's at least.
The "Mrs. Degree" isn't as popular as it once was, but no doubt there's people out there pursuing it. It should be updated to the "Mr. or Mrs. Degree" these days.
Agreed.
Just look at the god-awful mess GNOME just became again, outside of kernel-space. Or try to get LDAP authentication working on 100 servers already running on different distros.
Linux can't even hack centralized authentication properly yet. I love Linux and working on it, but it's kludge on top of kludge. Those that work, do so pretty well. The rest is a mess.
Ahh, been using Linux since 1995. Never seen that "more solid" thing come out of open-source yet.
Reason is, most devs don't look at code, they write it. Looking at someone's old code and trying to fix it is something a smaller percentage of devs do than those who just slap more code out.
Linux's stability lies in the original design (UNIX), not so much in the "many eyes/many hands" thing. That and distros who are willing to slow the process so businesses can actually use the stuff.
And the most stable things on Linux aren't so much the OS, as they are great applications which somehow have stood the test of time... Apache comes to mind...
VxWorks or Microware OS/9 still kick Linux's butt in the RTOS world for reliability and strength/stability of codebase. Just sayin'... if you're building missile systems, you're probably reaching for one of those.
Anonymous is getting pretty bold, jamming the downlink like that.
They get a vote.
And you only get a +2...? I'm not surprised, I guess. But you're right. Government is always controlled by whoever buys the politicians. That's pretty clear from history.
Name a single large software package that hasn't had at least one major serious screw-up like this in the last few years. The industry's retarded to keep allowing code to be handled as if it weren't real engineering with building codes, inspectors, etc.
What? Actually build from your release-candidate source and regression test? You must be kidding. This is open source we're talking about here, right?
The law of unintended consequences will join in on this one very soon, and there'll be a rash of beer-can thin aluminum 100 MPG econo-boxes crushed along with their contents by everything else on the road since fleets don't turn over that quickly.
The news media will only focus on the trucks and truck-body SUVs that some of us actually have real uses for, like towing and off-road locations that we really do need to get to, as the "cause" of the problem.
The retardedness continues. Have you seen the NHTSA video of what happens to a "Smart"Car (quotation marks added) when it's hit in a quartering head-on with a standard four-door sedan? Hint: Launch in T-minus... 3... 2... 1... it not only gets clobbered, it also has its direction *reversed* by the much larger mass.
Enjoy the flight.
I was hoping that scientists would point out that basing anything in life on a *model* (either their "good one" or the other guy's "bad one" (take your pick) is not science. It's religion.
Who says they didn't see the collapse coming and knew the government would bail them out at the expense of the taxpayer?
"All different versions"?
In Jerry's day, you couldn't location-shift at will via inexpensive telecommunications links. You're temporarily shifting cultures today every time you answer or place a phone call.
Do these things, spam dies...
A huge notable ISP or government would have to start this... someplace everyone wants to send mail through or to... Gmail would be perfect.
- Enable TLS on your inbound mail server. Start immediately tracking mail servers that fall into these categories: ... Use TLS properly and identify themselves with properly signed keys from a third-party source. ... Use TLS for encryption using self-signed keys. ... Don't use TLS.
- Immediately filter out servers that are dumb enough to use TLS as spam senders. (The really dumb one's.)
- Notify all senders that after X date, ONLY TLS enabled servers will be able to communicate with your domain or through it.
- Notify all senders that after Y date, ONLY TLS enabled servers with properly signed keys will be able to communicate.
Yup, it means a metric ton of CPU upgrades or TLS front-ends need to be put in front of large mail farms.
But if you can identify every server that talks to yours and/or block the servers and or keys that are known to have been compromised, spam drops to an annoyance. SpamAssassin and other services are far less likely to even be needed but can still backstop the process, and all sorts of good things happen.
Why mail server authentication and encryption haven't taken off yet on a massive scale, is only a matter of willpower by one huge entity willing to make the sacrifice of "guess we won't get mail from servers that can't identify themselves properly with PKI". Once it's in place, you just block servers you don't ever want mail from and you have traceable IDs for all the rest.
It's possible. No one has the cojones to do it at a place like Google or Amazon or some large branch of government. Make TLS mandatory to e-mail information about government bids to their procurement people, every large company in the U.S. with government contracts would cost-justify it overnight and deploy it.
Why should mail servers still be running SMTP unauthenticated and unencrypted in 2011? Browsers have been doing SSL for how long?
Correct. Wasn't paying attention to the dual part.
The developers of TSA scanners.
You just described every theme park in America.
It's far better to make up crap out of thin air, of course.
And far wiser to assume that they just didn't give a flying leap until someone showed them numbers on paper and they either didn't want to be embarrassed or wanted to impress someone with their energy-saving savvy.
Which they could have done if they'd walked their building even once at night, or even just had the forethought to ask if the HVAC was on 24/7.
Seen plenty of real-world managers ask that question without being prompted by a fancy monitoring system. Seen hotel managers crunch the numbers on energy efficient light bulbs. The difference here is there's no profit motive and they're spending other people's money.
The study just gave light to the truth of what they were wasting and a political reason to change it. Typical government job laziness and ineptitude.
Shouldn't the accountant and department that pays the energy bill for the entire school district have already found this and implemented it? Yup.
Ha. You've never seen the replacement budget for a Corporate IT department. The best laptops should go to those without children, judging by the destruction reason list.
Little off there. My employer was giving away P3 machines by the pallet by 2006 to employees and charities..P4s were given away by pulling names out of hats.
Ahh, I can see you've been to Comdex!
Time to stop buying gadgets so you can afford to move. ;-)
Picky, picky. Whiner.