The DEA has figured out that getting a wiretap order for an iPhone, executed at the phone company, doesn’t get them iMessage content. It’s pretty obvious the various TLAs engaged in law enforcement will use this as a concrete example to push the “Going Dark” initiative to get CALEA reinterpreted (or legislated) to cover various internet based communication services. And designing a service to use end-to-end protection will be right out.
iMessage is a special case here, since it inserts itself into the normal text message user interface. It’s the phone’s preferred way to send messages, and from the user’s (and law enforcement’s) perspective, it’s a native feature of the phone rather than an app.
I’m worried this will bring up yet another concern–even if they get what they want with CALEA, they are going to discover that they have execute multiple, maybe even many, wire tap orders to track a single subject. How long until we require each ISP to be able to MiTM attach every TLS connection? Or another clipper chip initiative?
Apple’s iMessage encryption trips up feds’ surveillance | Politics and Law – CNET News
… for forgetting that my new iPhone will do video until the moment was past.
I pulled into our alley tonight at 9:38 CDT, to the sight of a family of raccoons running directly towards my car, until they had an attack of good sense and turned and ran the other direction. By other direction, I mean straight back down the alley so that I could follow slowly and keep them in my headlights for a good 90 seconds.
By family, I mean 1 adult (I assume mom) and 5, count them, 5, juveniles. Mind you, I was in the Miata with the top down. They probably could have taken me, had they not been awed by the glory of my HID headlights.
In the process of setting up the new iPhone 3.0 note sync feature, I ran across this relic from my first day with the original iPhone:
This is a test to see how fast I van go with one fibgerJpq alpirr rjiimba so they qpekj sow doingmirao fast
I’m somewhat better at it now.
I just updated my iPhone to 1.1.3. On restart, it popped a window telling me how to use the new feature allowing me to rearrange icons on the home screen. You simply touch and hold an icon until it, get this, starts to “wiggle”. Yes, it actually used the word “wiggle.”
Sounds disturbing? You have no idea. (Unless of course you have one.) All the icons start wiggling. But it’s a subtle wiggle. Just enough to wonder if you’ve had a bit too much rum or something.
Not that I ever have that problem.
Anyhow, finally getting the “find yourself” function in Google Maps is way cool. Even though all the Nokia E6x users have had it for months. Heck, the freakin’ MDA users have had it for a while. But I bet my user interface for it is better.
(btw, FIRST post for 2008!)
There are an increasing number of jailbroken applications that can be loaded onto the iPhone — so many, in fact, that someone has thrown together a nifty package manager for installing and managing all of them.
One of the more interesting things to do, of course, is run an SSH client so you can perform remote administration of other machines. Apparently, the installation of SSH from the package manager is a full-fledged OpenSSL install — including the server side of things.
And yes, it does start up the SSH service.
Combine this with the well-known passwords for both “root” and “mobile” accounts and what do you get?
orthrus:~/ adam$ ssh email@example.com
The authenticity of host '172.17.1.44 (172.17.1.44)' can't be established.
RSA key fingerprint is 7f:c4:18:1d:08:63:6c:04:0c:14:30:b2:09:f4:ee:17.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.17.1.44' (RSA) to the list of known hosts.
Warning: No xauth data; using fake authentication data for X11 forwarding.
Last login: Mon Aug 27 17:34:23 2007 from 127.0.0.1
# uname -a
Darwin Q40 9.0.0d1 Darwin Kernel Version 9.0.0d1: Fri Jun 22 00:38:56 PDT 2007;
root:xnu-9188.8.131.52.obj~1/RELEASE_ARM_S5L8900XRB iPhone1,1 Darwin
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/disk0s1 307200 193116 111012 64% /
devfs 18 18 0 100% /dev
/dev/disk0s2 7622368 6624600 997768 87% /private/var
Hmm… methinks the potential for havoc may be high here.