"The accuracy of the GPS signal is identical for both the civilian GPS service (SPS) and the military GPS service (PPS). Civilian SPS broadcasts on only one frequency 1575.42 MHz, while military PPS uses two 1575.42 MHz and 1227.60 MHz."
"Once upon a time, the unencrypted signal included a random error factor that would make the civilian GPS randomly wrong in a different direction each day. I believe it started with errors up to 400 meters, which was still plenty accurate for general ocean navigation. The policy / feature was called “Selective Availability” and was killed in 2000."
I don't think the morons are paying attention to scientific facts. You bring to mind the stupidest line of dialog i ever heard from a WW II movie: "Johnson, take a reading with the compass so we can tell graves registration later where to find those bodies we buried." The half-wit writer actually thought a compass magically tells you exactly where you are, latitude and longitude!
You don't have a clue in hell what you're talking about. Destroyers have NEVER been armored in history. They don't call them "tin cans" for nothing. As a matter of fact, NO naval ships were ever "armored" the way you're thinking. Even battleships had no more than a narrow belt of armor at the waterline, and some armoring of decks and turrets. Well below the waterline, and above the waterline, there's nothing much there. Look how the South Dakota had her upperworks shot to hell in night action at Guadalcanal, mostly from small to medium caliber hits. Her communications, radar, and fire control were all wrecked.
The hull plating of a destroyer is like an eggshell. By comparison, tanker and cargo ship bows are built much sturdier, and the shape makes an excellent ram.
The disgusting part of this disaster was the way the US Navy persecuted Captain McVay, railroading him in a court martial with trumped-up charges shown to be nonsense by testimony of the Japanese sub captain, and finally driving McVay to suicide. He was the final victim, 24 years delayed. It took an act of Congress to force the Navy, kicking and screaming, to finally clear his record of all findings of wrongdoing, 56 years too late.
The mismanagement of the stupidly, needlessly, and literally carelessly delayed search and rescue of survivors, as day after day drifting in the water dehydrating, starving, going mad, and being picked off by sharks, is also a huge part of the disaster. Something very similar happened at the Battle off Samar, in which hundreds of sailors from a small group of destroyers and escort carriers, after being pulverized by a huge Japanese battle fleet, were also left to drift for days, with many needless drowning and shark bite deaths.
Bwahaha, these monkeys set up rsyncd naked on port 873? And all these stupid commenters are bleating about firewalls when using rsync with ssh is perfectly secure.
Wha? Are you daft? Setting an "at least" says NOTHING about how many you CAN have beyond that. The password could have one UC, or two, or three,... or ALL UC. >= 2 LC + >= 1 UC could be satisfied by LULL, UULL, LUUU, or UUUL. The brute force cracker still has to try all combinations. OK, he can eliminate a trivial part of the combinations, like UUUU and LLLL, but his life if not made "a lot easier".
If "similar combinations" produce the SAME hash, then your goddam hash is no goddam good. It's not a real hash. Hash collisions, no matter how trivial the difference in input, should be virtually impossible. Certainly that is true for SHA512. Change one character in the input, and the hash is COMPLETELY changed.
If the friggin auth mechanism even knows/stores your password, the system is hopeless from a security standpoint. The auth mechanism only needs to know the non-reversible HASH of your password, so it can compare it to the HASH of the input you type to log in. There is no excuse for storing passwords ANYWHERE.
But nobody could memorize 11 random characters, while anyone can easily memorize 4 random words. So the comparison is unfair. To be fair you have to compare 11 random characters with 11 random words, or 4 random characters with 4 random words.
If you need that much performance in a single CPU then $13K is trivial relative to the rest of the costs.
A complete and utter non-sequitur. If may or may not be trivial relative to total cost. I'm actually pretty goddam sure a $13K CPU is likely to dwarf the cost of the rest of the system - unless it has some outlandish amount of installed RAM - like terabytes.
If you think optical is any good whatsoever for archiving, you have never wasted time on it, No two optical drives can even agree on whether a written media can be read. Even the original drive is likely to reject a disk it wrote itself the day before. It is garbage technology on which I wasted all kinds of time and money, only to find it to have a reliability of zero. You can't have recording surfaces exposed to fingerprints and dust like that if you want something to depend on.
Slashdot Mirror
Pssst ... light travels only 1 meter in 3 microseconds. I don't think a goddam phone can capture an image, let alone process it, that fast.
"The accuracy of the GPS signal is identical for both the civilian GPS service (SPS) and the military GPS service (PPS). Civilian SPS broadcasts on only one frequency 1575.42 MHz, while military PPS uses two 1575.42 MHz and 1227.60 MHz."
"Once upon a time, the unencrypted signal included a random error factor that would make the civilian GPS randomly wrong in a different direction each day. I believe it started with errors up to 400 meters, which was still plenty accurate for general ocean navigation. The policy / feature was called “Selective Availability” and was killed in 2000."
https://www.quora.com/Is-there-any-difference-between-military-GPS-data-and-civilians-in-terms-of-accuracy
I don't think the morons are paying attention to scientific facts. You bring to mind the stupidest line of dialog i ever heard from a WW II movie: "Johnson, take a reading with the compass so we can tell graves registration later where to find those bodies we buried." The half-wit writer actually thought a compass magically tells you exactly where you are, latitude and longitude!
You don't have a clue in hell what you're talking about. Destroyers have NEVER been armored in history. They don't call them "tin cans" for nothing. As a matter of fact, NO naval ships were ever "armored" the way you're thinking. Even battleships had no more than a narrow belt of armor at the waterline, and some armoring of decks and turrets. Well below the waterline, and above the waterline, there's nothing much there. Look how the South Dakota had her upperworks shot to hell in night action at Guadalcanal, mostly from small to medium caliber hits. Her communications, radar, and fire control were all wrecked.
The hull plating of a destroyer is like an eggshell. By comparison, tanker and cargo ship bows are built much sturdier, and the shape makes an excellent ram.
Careful. NiFe blows off hydrogen when charged. Hydrogen will explode from a tiny spark.
The disgusting part of this disaster was the way the US Navy persecuted Captain McVay, railroading him in a court martial with trumped-up charges shown to be nonsense by testimony of the Japanese sub captain, and finally driving McVay to suicide. He was the final victim, 24 years delayed. It took an act of Congress to force the Navy, kicking and screaming, to finally clear his record of all findings of wrongdoing, 56 years too late.
The mismanagement of the stupidly, needlessly, and literally carelessly delayed search and rescue of survivors, as day after day drifting in the water dehydrating, starving, going mad, and being picked off by sharks, is also a huge part of the disaster. Something very similar happened at the Battle off Samar, in which hundreds of sailors from a small group of destroyers and escort carriers, after being pulverized by a huge Japanese battle fleet, were also left to drift for days, with many needless drowning and shark bite deaths.
Go back to grammar school. You don't advocate "for" something. That is illiterate. You just advocate something. Same as "recommend".
No they won't. Christ, how stupid do you think we are?
Whoosh.
I resemble that remark, since I would only have to be 17 years older than my present age of 70 to have been a possible K-ration eater.
Bwahaha, these monkeys set up rsyncd naked on port 873? And all these stupid commenters are bleating about firewalls when using rsync with ssh is perfectly secure.
Wha? Are you daft? Setting an "at least" says NOTHING about how many you CAN have beyond that. The password could have one UC, or two, or three, ... or ALL UC. >= 2 LC + >= 1 UC could be satisfied by LULL, UULL, LUUU, or UUUL. The brute force cracker still has to try all combinations. OK, he can eliminate a trivial part of the combinations, like UUUU and LLLL, but his life if not made "a lot easier".
Do they also break control-Insert paste? I've never used control-V. All my life I've used control-Insert to paste.
If "similar combinations" produce the SAME hash, then your goddam hash is no goddam good. It's not a real hash. Hash collisions, no matter how trivial the difference in input, should be virtually impossible. Certainly that is true for SHA512. Change one character in the input, and the hash is COMPLETELY changed.
Practices like that should be a hanging offense.
If the friggin auth mechanism even knows/stores your password, the system is hopeless from a security standpoint. The auth mechanism only needs to know the non-reversible HASH of your password, so it can compare it to the HASH of the input you type to log in. There is no excuse for storing passwords ANYWHERE.
But nobody could memorize 11 random characters, while anyone can easily memorize 4 random words. So the comparison is unfair. To be fair you have to compare 11 random characters with 11 random words, or 4 random characters with 4 random words.
ALL internal combustion engines produce NOx, sparky. Diesel exhaust is just more difficult and expensive to aftertreat to remove the last vestiges.
Just what we need. Alkaleaks now with increased chances of ruining equipment.
Bullshit. Alkalines can sometimes be "rejuvenated" to some limited extent. It's not the same thing.
LiFePO is expensive and has terrible energy density.
Yes. Duh.
A complete and utter non-sequitur. If may or may not be trivial relative to total cost. I'm actually pretty goddam sure a $13K CPU is likely to dwarf the cost of the rest of the system - unless it has some outlandish amount of installed RAM - like terabytes.
If you think optical is any good whatsoever for archiving, you have never wasted time on it, No two optical drives can even agree on whether a written media can be read. Even the original drive is likely to reject a disk it wrote itself the day before. It is garbage technology on which I wasted all kinds of time and money, only to find it to have a reliability of zero. You can't have recording surfaces exposed to fingerprints and dust like that if you want something to depend on.
Have some more pot and go back to sleep.