Question for anyone who knows: how the hell did KlearGear report a debt to a credit reporting agency in the first place? The credit reports are indexed by SSN, and they only have other identifiers like credit card numbers to go by if you don't have that. They paid by PayPal. Doesn't PayPal hide your credit card number from the merchant? With just a name, how did they report it? Does anyone know?
MythTV works fine for me and many other people. I'm not sure what went wrong in your case, but your experience is not representative. Encrypted QAM is supported through the HDHomeRun Prime and other CableCARD recorders, though you have to make sure the provider flags the channels you want copy-freely before going that route. I've never had database corruption issues, and I haven't heard it to be a common problem.
Hey, I do the same thing in the US! *High-five*! My biggest problem is mobile phones that like to get their time from the server. I have an Android phone, so I disable server time sync and use the NTP-based ClockSync program to avoid that issue.
Sorry, the keys never leave the debug registers -- the keys are not computable from anything in RAM.
The security gain comes from the fact that it is feasible to perform a side-channel attack on RAM but infeasible to perform a side-channel attack on CPU registers. The data to recreate the keys is scrubbed from RAM; the keys never leave RAM. I have done work on a similar project to TRESOR, called Loop-Amnesia, which uses MSRs instead of the debug registers to perform the same task and does not require AES-NI support.
Canadian courts do, eh?
Was this footage made public? If not, why not?
The report states that "the engine N1's were at about 55%". I'm not a pilot, but 55% doesn't sound like anywhere near full thrust to me.
I can't find the section you're referring to, and my research seems to indicate that laws passed by Congress supersede earlier conflicting international treaties. Perhaps you could indicate what you're referring to?
Link to Original Source
I've solved the cold boot attack, discussed here back when the original paper on it was published. There have been some other attempts at solving this, but as far as I can tell, mine is the only one currently available with actual working code, OSS or otherwise. It comes with a small performance price (read the paper), but I've been using this on my machines for months and I really haven't noticed a significant slowdown in system performance. Get the code and paper here. Instructions for using the code here."
Link to Original Source
Parent is trolling. I took the bait so I'm giving up karma bonus.
What I'm saying is that Linux on minority architectures that doesn't get much love, such as SPARC, has QA problems, because, no, unlike the assertion I was replying to, "just recompiling" doesn't cut it. Anything written in a C derivative (other than C#, which is really a Java derivative) on Windows will suffer from the same QA concerns that hit Linux on SPARC, which is why some companies don't even port stuff to AMD64. In the proprietary world, you just don't get software on your favorite platform; in the open source world, you get it, but you might not work. I know which I think is better, especially since I'm using much of the same software I ran on Linux/SPARC on Solaris/SPARC now using OpenCSW, and it works better now since more people use Solaris and so it gets more bug reports and therefore more QA.
You want to make an argument that Windows developers -- who typically have no experience with cross-architecture development -- will be better at writing cross-architecture software than Linux/UNIX developers, who typically do, go ahead and make it. I'd love to hear it.
Oh, suuuuure. Just rebuild. It'll be fiiiiiiine.
Yeah, man, go see how that works for you. Take it from someone who spent 3 years running Linux on SPARC before giving up in frustration. Even though most things on Linux are MAINTAINED ACTIVELY for basically every architecture thanks to Debian, you'll run into weird little issues like Firefox crashing randomly, X crashing randomly, GhostScript for some reason crashing quite consistently unless you use a crazy old version, and tons of other little annoying problems that eventually force you to switch to Solaris. And this is with people maintaining the code, just not looking at it too much since few people run or report bugs on Linux/SPARC.
"It's not a big deal. You just rebuild your software." What a laugh. News flash: it's very easy to write totally nonportable C if you don't know what you're doing without even realizing it if you're not careful. News flash 2: most Linux/UNIX developers are careful, and they still mess up (per above). News flash 3: most crap Windows developers aren't careful at all.
Microsoft can't even get people onboard for AMD64 yet. And that's an architecture transition that's actually important.
It does seem unfair. For instance, even if the police "know" someone is a drug pusher (like he got convicted of it before), they still need probable cause to search him if he's walking around town minding his own business. The difference here is that there are NO LIMITS to reasonableness of searches conducted by Customs at the border (the real one, not the alarmist ACLU one). They could give every US citizen returning home a body-cavity search if they wanted to. It's up to the people to use the democratic process to decide how much we want to balance the risk of being personally humiliated at the border with the risk that we will tie Customs' hands and prevent them from doing their job. Now, my personal opinion is that transferring digital files across the border is not something Customs should be guarding against, since there's this little thing called the Internet that bad guys can use to transfer digital files across the border just as easily. My vote would go to a politician who supported reducing Customs' role here. But that's just me. I'm one voter out of many.