That's all pointless when the defendant can prove he doesn't have all the components of the password. This is not trickery.
All that is needed is some computer the police cannot get to within a prescribed time frame, which provides random numbers (RN) only within specific time frames, and disposes of those numbers at the end, and does so with 2 or 3 different RNs overlapping in a sliding-window fashion. You can even be the owner of that computer, or it can be one run by someone else that you trust. That RN, combined with your pass-phrase, {en,de}crypts the real blob-key (BK) stored in an obvious place on the computer. This BK {en,de}crypts the other files.
Lets's say the time frame for these RNs is 3 weeks. Each week a new one is available and the oldest one is erased and no longer exists (of course, you have to trust the operator that this is actually done). At least every 3 weeks you must re-encrypt your BK. When the new RN is available, you fetch it, along with the older one your BK is currently encrypted with. Keep the RNs only in volatile unswapped RAM (VURAM). You provide the pass-phrase with the older RN and decrypt the BK. Then provide the pass-phrase (you can change it here if you like) with the newest RN and re-encrypt the BK. Put the the decrypted BK only in VURAM. Discard the RNs that were downloaded.
If you fail to perform this re-encryption cycle before the RN you were using is no longer available, you will lose access to your clear BK, and hence to all your data encrypted with that BK. You still remember the pass-phrase, but it is useless.
This scheme is still vulnerable to the Evil Maid attack, and maybe others. But it is plausible deniability for being able to access the clear KB which is needed to decrypt other files. It depends on the RN being no longer available after 3 weeks or less. The server will need to provide a different set of RNs to each user to prevent one user from keeping permanent copies that could be used on other users. And the user authentication for this needs to be secure during the time of using it.
I chose 3 weeks for the time frame for illustration purposes. You can choose whatever time frame you want. The basic idea is that the currently used RN automatically expires after a specified time frame (and you must trust that this will happen).
Modding doesn't prevent people who want to see it from seeing it. Hey, there's an idea. Just give the court judges some free mod points so they can mod down all those nasty comments about someone's favorite god.
The content was not really offensive. They just pretended that it was. But they are removing it from online so you will not be able to see the content and realize the lies perpetrated upon you.
This is why we need to keep all removed content online, so people can see what they would be missing if the liars are allowed to prevail. If the content is actually removed, then we know it's all just a coverup.
It should just a be a flag on the account "this account is not eligible for outside service billing". All outside billing would be rejected to those doing the billing (and then it's up to them to not provide those services for the legitimate services). Whether on or off, it only takes 1 bit.
We don't need hardware that pushes Linux. We just need open documented hardware that doesn't impede end users from installing whatever they want on their own hardware. The penguin will come, followed by a red demon.
It's Linux. Exercise your OS-bildskilz (or just wait for others to do it for you and steal theirs). Just replace what bits you don't want with what you do want. I might get one of these and put Armed-Slack on it with Xfce. Or I might not just to tick you off.
"Snag" also means you're stuck with it until you make a significant effort to get rid of it. Other possible words include "Snarf" (get it quickly) and "Snatch" (get it with the impression you are stealing it or getting it for your girlfriend). But I do like "boost" in this case.
Maybe it is the details of the licensing that differ between CDMA and GSM. The devil uses details as hiding places, ya know. I suspect Google hates having the OS tainted with having to handle proprietary stuff.
I'd rather have a fully open platform. However, I can accept a platform with well isolated sections where things like firmware to drive parts like the RF section do not need to involve the primary smart apps section where open innovation needs to play. But this does mean the proprietary sections need to have their firmware images stored and loadable from there, not from the OS. Then an app can be used to load the firmware, and the proprietary section can validate the firmware image signatures (every time it loads it from flash, too).
Personal responsibility. Corporate responsibility. It takes a lack of both for privacy to be violated. And it sure seems that between Facebook users and Facebook, there is a lack of both. But either users or the company can fix it. That's why you don't see me on Facebook (well, at least not under my own name).
They just need to avoid conference calls on unvetted conference systems, and in the clear networks, to organize this. I suspect they have figured this out by now.
Back then, corporations were not the same kind of thing as they are today. Those that did exist were government chartered companies by act of legislature. Over the 19th century, restrictions on corporations was reduced, and corporations were allowed to grow larger. And with it gradually came political corruption through donations and bribery, which today is virtually unlimited. The "pay" is now no longer so low; it's in the millions of dollars counting all the legalized and illegal money congressional reps and senators get.
Rather than term limits, if we completely sever all other sources of pay besides what their government paycheck is, maybe we can restore true representation of the people (which in term represents the non-government corporations by way of the people who own stock in these corporations).
Obviously not competent in how to move servers. But whether this is a case of bottom of the barrel IT employees, or idiot executives badly micromanaging (or both) is unclear. They can let us know which it is, if they know how to login to Slashdot (which I doubt).
... upgrade the ARM architecture to 64 bit (hopefully, they have some experience in that), put 64 cores of it on one die, and crank the speed up to 4 GHz.
A $244 million plane has $25 million dollars damage. So someone decides it's better to go buy a replacement plane at $244 million instead of $25 million (to be extracted from the contractor's insurance company) to fix the damage?
Where are the Republicans when you need them? Out campaigning? Oh wait, they're on the golf course with the Northrop Grumman executives.
Slashdot Mirror
That's all pointless when the defendant can prove he doesn't have all the components of the password. This is not trickery.
All that is needed is some computer the police cannot get to within a prescribed time frame, which provides random numbers (RN) only within specific time frames, and disposes of those numbers at the end, and does so with 2 or 3 different RNs overlapping in a sliding-window fashion. You can even be the owner of that computer, or it can be one run by someone else that you trust. That RN, combined with your pass-phrase, {en,de}crypts the real blob-key (BK) stored in an obvious place on the computer. This BK {en,de}crypts the other files.
Lets's say the time frame for these RNs is 3 weeks. Each week a new one is available and the oldest one is erased and no longer exists (of course, you have to trust the operator that this is actually done). At least every 3 weeks you must re-encrypt your BK. When the new RN is available, you fetch it, along with the older one your BK is currently encrypted with. Keep the RNs only in volatile unswapped RAM (VURAM). You provide the pass-phrase with the older RN and decrypt the BK. Then provide the pass-phrase (you can change it here if you like) with the newest RN and re-encrypt the BK. Put the the decrypted BK only in VURAM. Discard the RNs that were downloaded.
If you fail to perform this re-encryption cycle before the RN you were using is no longer available, you will lose access to your clear BK, and hence to all your data encrypted with that BK. You still remember the pass-phrase, but it is useless.
This scheme is still vulnerable to the Evil Maid attack, and maybe others. But it is plausible deniability for being able to access the clear KB which is needed to decrypt other files. It depends on the RN being no longer available after 3 weeks or less. The server will need to provide a different set of RNs to each user to prevent one user from keeping permanent copies that could be used on other users. And the user authentication for this needs to be secure during the time of using it.
I chose 3 weeks for the time frame for illustration purposes. You can choose whatever time frame you want. The basic idea is that the currently used RN automatically expires after a specified time frame (and you must trust that this will happen).
Modding doesn't prevent people who want to see it from seeing it. Hey, there's an idea. Just give the court judges some free mod points so they can mod down all those nasty comments about someone's favorite god.
The content was not really offensive. They just pretended that it was. But they are removing it from online so you will not be able to see the content and realize the lies perpetrated upon you.
This is why we need to keep all removed content online, so people can see what they would be missing if the liars are allowed to prevail. If the content is actually removed, then we know it's all just a coverup.
Oh yeah, and Windows is malware.
And it is pre-installed. You need do nothing. It is factory infected.
Exactly. This is not a request to overturn a conviction on some legal basis of an error in the conviction.
It should just a be a flag on the account "this account is not eligible for outside service billing". All outside billing would be rejected to those doing the billing (and then it's up to them to not provide those services for the legitimate services). Whether on or off, it only takes 1 bit.
... and there a zero apps directly from the community.
We don't need hardware that pushes Linux. We just need open documented hardware that doesn't impede end users from installing whatever they want on their own hardware. The penguin will come, followed by a red demon.
It's Linux. Exercise your OS-bildskilz (or just wait for others to do it for you and steal theirs). Just replace what bits you don't want with what you do want. I might get one of these and put Armed-Slack on it with Xfce. Or I might not just to tick you off.
"Snag" also means you're stuck with it until you make a significant effort to get rid of it. Other possible words include "Snarf" (get it quickly) and "Snatch" (get it with the impression you are stealing it or getting it for your girlfriend). But I do like "boost" in this case.
... whose access to the internet and computers needs to be denied.
Maybe it is the details of the licensing that differ between CDMA and GSM. The devil uses details as hiding places, ya know. I suspect Google hates having the OS tainted with having to handle proprietary stuff.
I'd rather have a fully open platform. However, I can accept a platform with well isolated sections where things like firmware to drive parts like the RF section do not need to involve the primary smart apps section where open innovation needs to play. But this does mean the proprietary sections need to have their firmware images stored and loadable from there, not from the OS. Then an app can be used to load the firmware, and the proprietary section can validate the firmware image signatures (every time it loads it from flash, too).
So pitch GSM, now.
Maybe they just need their own "social media" site, but change "social" to "academic", and make "media" be the papers they publish.
Easier to just break away from Europe.
Personal responsibility. Corporate responsibility. It takes a lack of both for privacy to be violated. And it sure seems that between Facebook users and Facebook, there is a lack of both. But either users or the company can fix it. That's why you don't see me on Facebook (well, at least not under my own name).
They just need to avoid conference calls on unvetted conference systems, and in the clear networks, to organize this. I suspect they have figured this out by now.
Back then, corporations were not the same kind of thing as they are today. Those that did exist were government chartered companies by act of legislature. Over the 19th century, restrictions on corporations was reduced, and corporations were allowed to grow larger. And with it gradually came political corruption through donations and bribery, which today is virtually unlimited. The "pay" is now no longer so low; it's in the millions of dollars counting all the legalized and illegal money congressional reps and senators get.
Rather than term limits, if we completely sever all other sources of pay besides what their government paycheck is, maybe we can restore true representation of the people (which in term represents the non-government corporations by way of the people who own stock in these corporations).
Obviously not competent in how to move servers. But whether this is a case of bottom of the barrel IT employees, or idiot executives badly micromanaging (or both) is unclear. They can let us know which it is, if they know how to login to Slashdot (which I doubt).
... upgrade the ARM architecture to 64 bit (hopefully, they have some experience in that), put 64 cores of it on one die, and crank the speed up to 4 GHz.
I'm lining up ahead of you.
A $244 million plane has $25 million dollars damage. So someone decides it's better to go buy a replacement plane at $244 million instead of $25 million (to be extracted from the contractor's insurance company) to fix the damage?
Where are the Republicans when you need them? Out campaigning? Oh wait, they're on the golf course with the Northrop Grumman executives.
They're just focusing on people who upload unencrypted stuff.
... there's no actual terrorist threat going on right now. Gotta keep looking busy somehow.
... to NBC: Sue 'em
... to Romney: Counter sue 'em
This is America, in case you don't know.