That's what I thought too, until I read up on how 911 service works. It's completely automated and based on telephone trunk switching. They can shut down a call center and reroute all the calls from the affected area to the next nearest call center, this won't work if you use the NPA number. Basically you have to hook into 911 at the switch level and it's not designed to work from a remote exchange (like my case where my POP is about 12 miles and 3 cities from my residence). That's the reason that they don't even give the emergency call center their NPA number.
Nope, once it is used that sequence is removed from the valid pool. This is to insure against replay attacks just as you describe. I've done it to myself before where I hit disconnect on accident and was unable to relogin until the next number came up on the fob.
Yes, but if things were working as they should have been a password logger doesn't do you ANY good. The password as entered by the user consists of two parts, the first part is their passphrase, which is like a traditional password, but the second part is a numeric sequence which is spat out by a numeric FOB which is synced to the master access server. These combined passwords must be entered within a narrow window, and once accepted are no longer valid. Someone must have f'd up big time to allow an internet accessible machine to bypass this very strong access mechanism.
Cisco uses two factor one time passwords for remote access. I don't see how planting a trojaned copy of SSH on the lab computers would give the hacker access to Cisco's systems.
Don't save a little bit of cash on a crappy car and end up paying many, many, many times more for injuries likely to be sustained in a crash by a young driver! People like to look at the small picture (the cost of gas at the pump each week) and ignore the big picture (it costs a lot to be injured in a crappy car) way too much.
I assume that's 45MPH, not MPG. 45MPH is slow, try the same at 70 and the results will be VERY different, because the AC uses (roughly) the same amount of power but drag will have almost trippled!
That's not always true. Your leakage current loss can go so high that a smaller process processor with the same transistor count can use MORE current then the larger process chip. Intel mostly fought this with the use of strained silicon and by using nickel silicide instead of cobalt silicide when introducing Prescott at 90nm.
Not when it's as unsafe as the Cavalier! The 1995-2005 Cavalier was one of the few vehicles to get a Poor from the National Institue for Highway Safety in offset crash tests. To be fair the Cobalt gets a Good, but it's also a significantly more expensive vehicle. Small vehicle results can be seen here, and general information is available at the insitutes homepage.
I can tell you for a certainty that even on a car with a low coefficient of friction that there will be a HUGE difference in fuel economy between 60 and 90. According to an online calculator I found the amount of drag force for my car at 60 is 66.5lbs while at 90 it is 149.7lbs, that's almost a trippleing of drag force for a 50% increase in speed! Most modern cars have a drag coefficient somewhere around.30-.35 so they will have similar results.
No need to go underground, just build a Faraday cage. When I supported Cisco's wireless division we had several large test chambers which were copper sheet lined boxes used for testing high amplification gear without radiating everyone around. A similar setup would work for testing wireless virus transmission.
And even in high end server environments, failover is an odd excuse for more than one NIC - I'd suspect the motherboard would go bad far more often than *only one* NIC would go bad.
I've seen it quite a few times, and as often as not, it's a switchport, or an entire switch in the stack that goes bad, not the port on the server. If you do proper failover with each nic going to a seperate switch then you have the kind of redundancy needed for 5 9's uptime, which is a basic requirement in many environments. Another use for dual NIC's is to have a seperate backup network that doesn't impact the traffic on the production network. Personally I often use three nic's, two for failover and one for the backup network, that's assuming no SAN though.
Concrete roads have grooves built into them because a perfectly smooth concrete road would be about as slippery as black ice with even a little water on it.
You are wrong, the primary problem was that the force of the impact removed a significant amount of fire protectant from the beams in the area of the fire. The jet fuel probably threw a large amount of thermal energy into the mix, however it would have been long burned off by the time the towers fell. The best guesses at this point are plastics and paper from the office fueled by high speed winds from the large holes in the building were what caused the beams to weaken and ultimatly pull from their moorings.
hmm, my Ford Taurus with 165K miles on it still gets ~24mpg despite a 3400lb curb weight, and it runs on 87 octane. With correct fuel injector technology and proper air intake design there should be little need to use higher octane fuel.
Did you READ the website? Sure, the screenshot makes it look very similar to the real walmart foundations website, that's part of good parody, to conjure the image of the origional. The CONTENT of the parody site makes it obvious that it's a parody, unless you are a complete simpleton. A good example is this paragraph from the About Us page:
"Implementation
Wal-Mart's approach to community involvement is unique, because we're able to screw communities over and yet they seem to love us anyway. Even many people who think we're evil shop here anyway. Our prices are that irresistible! Then there are groups of people who think they're causing change by "boycotting" us, when they don't even tell anyone why they boycott us, and choose instead to spend their money at Target and Best Buy- do you think those guys are any better, just because they're smaller? If they were our size, and if you keep shopping there one day they might be, they'd be just as destructive."
Actually AOL has one of the best abuse departments I have had the pleasure of working with. They publish their general rules, and if you can't figure out why you are being blocked just give them a call. They have always been very helpfull with me and given me the exact reason for the block and how I can go about resolving the issue. If you are blocked and resolve the problem they will probably automatically detect the fix, but if they don't a phonecall to their abuse desk with an explanation that the problem is solved will get the block cleared. Personally I like the fact that AOL (and Earthlink) have championed the antispam crusade, they have made more impact than a thousand admins screaming into the night could ever have.
I take it you've never actually used Photoshop? With multiple undo's, copy and paste buffer, layering, etc the amount of memory used by an even moderatly sized image file can quickly grow to insane proportions. I only have a 3MP camera but during an editing session my Photoshop memory usage can quickly grow into the hundreds of MB's. I feel the pain of those working at professional resolutions.
Yes, RFC1033 and RFC1912 recommend a minimum TTL of one day,
NO, they do NOT, RFC 1033 specifically states: Then, if you know some data will be changing in the near
future, set the TTL for that RR down to a lower value (an hour to a
day) until the change takes place,
It couldn't be much more clear, if you need the TTL to be low you should be able to rely on it being observed specifically so that your changes can be properly propogated.
WHY? Akamai DNS servers will be colocated at any major ISP. Doing the network chat to get a new 1 minute long entry from the Akamai DNS server into their own cache will NOT be putting any significant load on their caching server. If they ignore Akamai updates then they risk having poor service as Akamai knows a LOT about doing load balancing and distribution, more than any admin who thinks they are being smart by ignoring TTL on DNS records. If you really need proof that you shouldn't mess with TTL's see RFC 2181 which states The TTL specifies a maximum time to live, not a mandatory
time to live.
In that case you just add a HOST file entry for the corrected IP and hostname. I've used this trick to check client systems immedietly after making a major change that our own caching DNS servers haven't picked up (generally I set client TTL down to 30 minutes before an expected IP change, I often have to test less than a half hour after the change). This allows you to test virtual servers without relying on outside DNS servers to provide the correct info.
--One worry for MS though, if this catches on, might the ease of administration, standardised licensing etc, start to hurt full Windows sales ?
They don't care, they probably get about as much for one of these licenses as they do for an OEM copy of windows, and then they get a TS CAL purchase, and a windows server seat license, and probably an Office CAL. So MS makes plenty of money on small machines hooked up to a TS box.
Ever been to a bank, an airport, a car rental agency, an insurance agents office? Chances are better than 50% that they were using a diskless workstation/dumb terminal to access a mainframe/mini for their backend apps. If they weren't then they were almost assuradly using a dumb terminal emmulation app to do the same with a full fledged PC. These days some of this is being moved to web services accessing the same backends, but that just serves to slow access down but make it a bit easier to learn.
--Ive not compared them, but how does the following compare: VNC compression, X with LBX module, ICA protocol, and gzip.
ICA beats every other remote protocol hands down. It's fast, efficient, and saves state across sessions.
--I dont understand... Maybe Im reading what this does wrong but why would you need to publish an app? Wouldnt you just copy it to the server and make links?
You can limit access to applications based on group membership, so if someone needs a new app all you have to do is add them to the published apps group and they can now run it.
Slashdot Mirror
Sorry, but doing things like refusing to come speak because a LUG uses the term Linux instead of his prefered term GNU/Linux IS arrogant.
From allwords.com:
having or showing too high an opinion of one's own abilities or importance; impudently over-presumptive.
That's what I thought too, until I read up on how 911 service works. It's completely automated and based on telephone trunk switching. They can shut down a call center and reroute all the calls from the affected area to the next nearest call center, this won't work if you use the NPA number. Basically you have to hook into 911 at the switch level and it's not designed to work from a remote exchange (like my case where my POP is about 12 miles and 3 cities from my residence). That's the reason that they don't even give the emergency call center their NPA number.
Nope, once it is used that sequence is removed from the valid pool. This is to insure against replay attacks just as you describe. I've done it to myself before where I hit disconnect on accident and was unable to relogin until the next number came up on the fob.
Yes, but if things were working as they should have been a password logger doesn't do you ANY good. The password as entered by the user consists of two parts, the first part is their passphrase, which is like a traditional password, but the second part is a numeric sequence which is spat out by a numeric FOB which is synced to the master access server. These combined passwords must be entered within a narrow window, and once accepted are no longer valid. Someone must have f'd up big time to allow an internet accessible machine to bypass this very strong access mechanism.
Hopefully before since they were talking about removing it back in 2002. Infosec must have been supremely pissed if that is in fact how they got in!
Cisco uses two factor one time passwords for remote access. I don't see how planting a trojaned copy of SSH on the lab computers would give the hacker access to Cisco's systems.
Don't save a little bit of cash on a crappy car and end up paying many, many, many times more for injuries likely to be sustained in a crash by a young driver! People like to look at the small picture (the cost of gas at the pump each week) and ignore the big picture (it costs a lot to be injured in a crappy car) way too much.
I assume that's 45MPH, not MPG. 45MPH is slow, try the same at 70 and the results will be VERY different, because the AC uses (roughly) the same amount of power but drag will have almost trippled!
That's not always true. Your leakage current loss can go so high that a smaller process processor with the same transistor count can use MORE current then the larger process chip. Intel mostly fought this with the use of strained silicon and by using nickel silicide instead of cobalt silicide when introducing Prescott at 90nm.
Not when it's as unsafe as the Cavalier! The 1995-2005 Cavalier was one of the few vehicles to get a Poor from the National Institue for Highway Safety in offset crash tests. To be fair the Cobalt gets a Good, but it's also a significantly more expensive vehicle. Small vehicle results can be seen here, and general information is available at the insitutes homepage.
I can tell you for a certainty that even on a car with a low coefficient of friction that there will be a HUGE difference in fuel economy between 60 and 90. According to an online calculator I found the amount of drag force for my car at 60 is 66.5lbs while at 90 it is 149.7lbs, that's almost a trippleing of drag force for a 50% increase in speed! Most modern cars have a drag coefficient somewhere around .30-.35 so they will have similar results.
No need to go underground, just build a Faraday cage. When I supported Cisco's wireless division we had several large test chambers which were copper sheet lined boxes used for testing high amplification gear without radiating everyone around. A similar setup would work for testing wireless virus transmission.
And even in high end server environments, failover is an odd excuse for more than one NIC - I'd suspect the motherboard would go bad far more often than *only one* NIC would go bad.
I've seen it quite a few times, and as often as not, it's a switchport, or an entire switch in the stack that goes bad, not the port on the server. If you do proper failover with each nic going to a seperate switch then you have the kind of redundancy needed for 5 9's uptime, which is a basic requirement in many environments. Another use for dual NIC's is to have a seperate backup network that doesn't impact the traffic on the production network. Personally I often use three nic's, two for failover and one for the backup network, that's assuming no SAN though.
Concrete roads have grooves built into them because a perfectly smooth concrete road would be about as slippery as black ice with even a little water on it.
You are wrong, the primary problem was that the force of the impact removed a significant amount of fire protectant from the beams in the area of the fire. The jet fuel probably threw a large amount of thermal energy into the mix, however it would have been long burned off by the time the towers fell. The best guesses at this point are plastics and paper from the office fueled by high speed winds from the large holes in the building were what caused the beams to weaken and ultimatly pull from their moorings.
hmm, my Ford Taurus with 165K miles on it still gets ~24mpg despite a 3400lb curb weight, and it runs on 87 octane. With correct fuel injector technology and proper air intake design there should be little need to use higher octane fuel.
Did you READ the website? Sure, the screenshot makes it look very similar to the real walmart foundations website, that's part of good parody, to conjure the image of the origional. The CONTENT of the parody site makes it obvious that it's a parody, unless you are a complete simpleton. A good example is this paragraph from the About Us page:
"Implementation
Wal-Mart's approach to community involvement is unique, because we're able to screw communities over and yet they seem to love us anyway. Even many people who think we're evil shop here anyway. Our prices are that irresistible! Then there are groups of people who think they're causing change by "boycotting" us, when they don't even tell anyone why they boycott us, and choose instead to spend their money at Target and Best Buy- do you think those guys are any better, just because they're smaller? If they were our size, and if you keep shopping there one day they might be, they'd be just as destructive."
Actually AOL has one of the best abuse departments I have had the pleasure of working with. They publish their general rules, and if you can't figure out why you are being blocked just give them a call. They have always been very helpfull with me and given me the exact reason for the block and how I can go about resolving the issue. If you are blocked and resolve the problem they will probably automatically detect the fix, but if they don't a phonecall to their abuse desk with an explanation that the problem is solved will get the block cleared. Personally I like the fact that AOL (and Earthlink) have championed the antispam crusade, they have made more impact than a thousand admins screaming into the night could ever have.
I take it you've never actually used Photoshop? With multiple undo's, copy and paste buffer, layering, etc the amount of memory used by an even moderatly sized image file can quickly grow to insane proportions. I only have a 3MP camera but during an editing session my Photoshop memory usage can quickly grow into the hundreds of MB's. I feel the pain of those working at professional resolutions.
Yes, RFC1033 and RFC1912 recommend a minimum TTL of one day,
NO, they do NOT, RFC 1033 specifically states:
Then, if you know some data will be changing in the near future, set the TTL for that RR down to a lower value (an hour to a day) until the change takes place,
It couldn't be much more clear, if you need the TTL to be low you should be able to rely on it being observed specifically so that your changes can be properly propogated.
WHY? Akamai DNS servers will be colocated at any major ISP. Doing the network chat to get a new 1 minute long entry from the Akamai DNS server into their own cache will NOT be putting any significant load on their caching server. If they ignore Akamai updates then they risk having poor service as Akamai knows a LOT about doing load balancing and distribution, more than any admin who thinks they are being smart by ignoring TTL on DNS records. If you really need proof that you shouldn't mess with TTL's see RFC 2181 which states The TTL specifies a maximum time to live, not a mandatory time to live.
In that case you just add a HOST file entry for the corrected IP and hostname. I've used this trick to check client systems immedietly after making a major change that our own caching DNS servers haven't picked up (generally I set client TTL down to 30 minutes before an expected IP change, I often have to test less than a half hour after the change). This allows you to test virtual servers without relying on outside DNS servers to provide the correct info.
--One worry for MS though, if this catches on, might the ease of administration, standardised licensing etc, start to hurt full Windows sales ?
They don't care, they probably get about as much for one of these licenses as they do for an OEM copy of windows, and then they get a TS CAL purchase, and a windows server seat license, and probably an Office CAL. So MS makes plenty of money on small machines hooked up to a TS box.
Ever been to a bank, an airport, a car rental agency, an insurance agents office? Chances are better than 50% that they were using a diskless workstation/dumb terminal to access a mainframe/mini for their backend apps. If they weren't then they were almost assuradly using a dumb terminal emmulation app to do the same with a full fledged PC. These days some of this is being moved to web services accessing the same backends, but that just serves to slow access down but make it a bit easier to learn.
--Ive not compared them, but how does the following compare: VNC compression, X with LBX module, ICA protocol, and gzip.
ICA beats every other remote protocol hands down. It's fast, efficient, and saves state across sessions.
--I dont understand... Maybe Im reading what this does wrong but why would you need to publish an app? Wouldnt you just copy it to the server and make links?
You can limit access to applications based on group membership, so if someone needs a new app all you have to do is add them to the published apps group and they can now run it.