No, it isn't. Weather occurs in the troposphere, the layer of the atmosphere closest to the earth, extending up to between 7 - 20 km above ground level. About 80% of the mass of the atmosphere is here.
The ionosphere is about 0.1% of the mass of the atmosphere, starting from about 90 km above ground level and continuing to between 500 - 1,000 km above ground level.
Educate yourself a little. Science is a beautiful thing.
Paxil Diaries is $28.50 at Lulu right now.
Once my copy shows up, is there any way to send it an "Nobots" to you for autographing?
In the link in the third sentence of the summary titled "forward secrecy". Is this a trick question?
10. The companies listed do large amounts of business with the U.S. government, which requires FIPS certification of crypto software.
20. OpenBSD has explicitly stated that FIPS certification is off the table for OpenSSH. NOT one of their goals.
30. Taking that off the table leaves a large pile of money ON the table.
40. GOTO 10
The core encryption functions of an older version (0.9.8, I think) was spun off into a separate module and certified for FIPS. The certification process is that the code is provably correct and the implementation is flawless, which is why it takes so damn long. It is also why only the core crypto transforms are certified.
You CAN, and vendors DO update the wrapper module around the core functions and update things without having to go back under certification.
Case in point. The Red Hat version of FIPS-OpenSSL was susceptible to HeartBleed, even though the core FIPS module was based off of an older version that was produced before the code error was introduced! Why? Because the error wasn't in the core crypto but rather the wrapper, non-crypto code. The actual cryptographic transforms (AES, HMAC-SHA, etc.) functioned perfectly, but information was leaked by the non-crypto code.
LOTS of people -- like almost everyone in the U.S. Gov't or contractors that work on their systems -- use the FIPS certified module for OpenSSL. Or, at least, Red Hat's version of it.
Not necessarily. It looks like they're removing what they can't support, such as VMS, Netware and OS/2. The few people that care can still use the original OpenSSL code.
I'd expect them to ensure it support the hardware platforms OpenBSD supports at the very least. Then, if they go the "portable" route like they did for OpenSSH, support for the other Unix and Unix-like systems.
http://www.openssh.com/portable.html
More power to them.
For someone seemingly intelligent enough to try and enumerate the tie options in code, they were brain dead fucking stupid enough to try to illustrate it with small pictures of a black tie on a black shirt.
Sheer genius.
Uh, no thanks.
I much prefer that wireles to be on a mini-PCIe card so I can upgrade it if necessary.
Damn near everything that comes with Wifi/BT ends up being single-band b/g/n and BT 2.0. For $35 I can get a dual-band, a/b/g/n/ac card w/BT 4.0.
Slapping it on the board greatly reduces options.
The song started playing in my head as soon as I read that phrase.
Led Zeppelin When the Levee Breaks.
The song started playing in my head as soon as I read that phrase.
Led Zeppelin When the Levee Breaks.
Ouch. Those are taxed at 28%, IIRC.
No, you're supposed to pay your taxes in the form the government with the military SAYS you're supposed to pay your taxes regardless of what you personally use for a medium of exchange.
"Luke, I'm yer father, eh. Come over to the dark side, you hoser." -- Dave Thomas, "Strange Brew"
