Well, I have an android 2.3 device, and all it takes to get to safe mode is to turn it on, and as soon as the logo comes up, hold volume down until boot is finished. No password required.
Though this is likely something specific to this device, and not an android feature.
Wikipedia provides database dumps. Just use a transparent proxy to serve from your own private wikipedia - instead of irritating everyone else who might be looking at that information legitimately!
As far as the file style analysis - this wouldn't be possible except at the very beginning of the connection, as the data in the middle looks like garbage.
The beginning though - where certificates are exchanged and handshakes made - this could be picked up on, and if the connection was squashed at this point, it wouldn't be possible to continue.
Using a one-time-pad type of stream cipher would work, so long as you made sure to send the next pad before you ran out on the existing one. The danger of that though, is if they can grab a pad, they could theoretically decrypt any subsequent data (so long as they didn't "miss" recording the part with the next pad).
Provided the pads are generated in an actually random or near-random manner, then the ciphertext would be indistinguishable from said random/near-random data.
A proper encryption without a header of some kind, and without the key, looks like random noise. You can suspect it's encrypted, but you cannot know for certain (ignoring context. even then, the context only suggests, not proves)
So, pedantically, I suppose it IS possible. But not over in practical land.
Send the SSL data in a standard HTTP stream. Even better, base64 encode the data, so it looks like actual text.
To block this means either blocking HTTP as a whole, or building/buying some expensive stuff that can understand HTTP and do some kind of content analysis on it.
Indeed. Google should detect these mangled 'lol' instances and replace them with a statement that reads to the effect of "I am a raging idiot, so I tried to put too many O's in my LOL."
I did, until I was 12. We technically had one, an old TI-99, but I never used it for anything more than playing atari-style games - hardly any text to read.
Even then I hated cursive. Things were printed, books etc - so I insisted on blowing it off and just learning "block letters" or whatever you call hand printing. I can't say I've ever missed being able to write it... or even read it.
IBM mainframes (think iSeries, AS/400 etc) have been mostly case-insensitive uppercase by default until recently. I'd imagine it's quite common on the ancient-history-mainframe side.
Slashdot Mirror
Wrong side of the spectrum, idiot. You're thinking of near-infrared.
Well, I have an android 2.3 device, and all it takes to get to safe mode is to turn it on, and as soon as the logo comes up, hold volume down until boot is finished. No password required.
Though this is likely something specific to this device, and not an android feature.
That works precisely as long as it takes someone to figure out how to boot into safe mode or some other such thing, and bypass the fancy launcher.
Though at that point they are clearly behaving maliciously, and I don't see why this policy problem has to be solved with technology.
You realize this guy made Twisted Metal? He'll get 5 minutes in and quit because there weren't enough Michael Bay Explosions.
A smart man would have moved to New Zealand before posting the tweets. Hard to be intercepted for doing something you had not done, after all.
Nope. It's leftover cold war bullshit, back when considering encryption a munition made sense.
But you can't be seen weakening our nation these days, can you? Hence it hasn't been killed yet.
I suppose you missed this part, right there in the fucking summary:
Designed to speed industrial inspection systems — such as detecting whether food is spoiled
(emphasis mine)
To paraphrase an AC, you basically follow an established-by-development script over and over and over and over and over and over...
You do not think, you do not troubleshoot. You perform prescribed actions and check marks on your... checklist.
Wikipedia provides database dumps. Just use a transparent proxy to serve from your own private wikipedia - instead of irritating everyone else who might be looking at that information legitimately!
... because people reading this thread may not be subject matter experts, and know all of that?
As far as the file style analysis - this wouldn't be possible except at the very beginning of the connection, as the data in the middle looks like garbage.
The beginning though - where certificates are exchanged and handshakes made - this could be picked up on, and if the connection was squashed at this point, it wouldn't be possible to continue.
Using a one-time-pad type of stream cipher would work, so long as you made sure to send the next pad before you ran out on the existing one. The danger of that though, is if they can grab a pad, they could theoretically decrypt any subsequent data (so long as they didn't "miss" recording the part with the next pad).
Provided the pads are generated in an actually random or near-random manner, then the ciphertext would be indistinguishable from said random/near-random data.
A proper encryption without a header of some kind, and without the key, looks like random noise. You can suspect it's encrypted, but you cannot know for certain (ignoring context. even then, the context only suggests, not proves)
So, pedantically, I suppose it IS possible. But not over in practical land.
I can see it now.
Analyst A: Wow, this cat photo has gotten VERY popular.
Analyst B: Hey... why do these otherwise identical photos have different checksums?
encapsulation.
Here's one way to do it:
Send the SSL data in a standard HTTP stream. Even better, base64 encode the data, so it looks like actual text.
To block this means either blocking HTTP as a whole, or building/buying some expensive stuff that can understand HTTP and do some kind of content analysis on it.
Indeed. Google should detect these mangled 'lol' instances and replace them with a statement that reads to the effect of "I am a raging idiot, so I tried to put too many O's in my LOL."
Filter error: That's an awful long string of letters there. ... It's like YELLING.
Filter error:
Filter error: I hate you.
It does. It's the various +1 moderations.
You have to "earn" them though.
They already own a license for it. They (presumably) sublicense it to customers?
Indeed. WTF are Kardashians and did they realize what they were naming themselves?
Shame you left your commas with the cursive script, though :P
I did, until I was 12. We technically had one, an old TI-99, but I never used it for anything more than playing atari-style games - hardly any text to read.
Even then I hated cursive. Things were printed, books etc - so I insisted on blowing it off and just learning "block letters" or whatever you call hand printing. I can't say I've ever missed being able to write it... or even read it.
IBM mainframes (think iSeries, AS/400 etc) have been mostly case-insensitive uppercase by default until recently. I'd imagine it's quite common on the ancient-history-mainframe side.
Contact them. I'm sure they'll take donations in a variety of means.
Most people (we are not all paragons of virtue) do that. The difference was that Jobs was apparently good at it.