Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment: Re:The big advantage of XOR (Score 1) 277

thanks, for those explanations. it's nice to know that custom signing keys for system images might make to nexus devices someday.
The only, sad thing is that if a device is dropped, even if it s capable of all the new and shinny things, no one would be able to bring it up to speed.
I still have that bitter after taste after support for galaxy nexus was dropped, althought it was -and still-- very much a capable device. it even had the hardware https://android.googlesource.c... /rant
again thanks for the info :)

Comment: Re:The big advantage of XOR (Score 1) 277

I always deplored the absence of the possibility to replace bootloader signing/verification keys with my own (that way I don;t have to unlock/relock every time I need to do something). I do have a nexus 5, and I don't like new nexus line, so I guess I'm out of luck, since hammerhead will be dropped soonish :'(.

Comment: Re:Sooo .. (Score 1) 127

there's an app I saw on F-droid, that checks the device's accelerometer and locks it if it detects a sudden violent movement (snatched, falling ... etc) and locks it right away. It is availabale of course in google's play store. Pluck Lock (there are plenty others
with that said this smart lock thing is very very bad -IMHO which is why I deactivated it completely-, it makes locking the phone a joke.

Comment: Re:Bulls... since when will self driving cars have (Score 1) 451

by kenshin33 (#49294117) Attached to: Lyft CEO: Self-Driving Cars Aren't the Future
same could be said about pedestrians (I say that as both, a driver and a pedestrian).
One as, I was trying to cross a street a a swarm of said pedestrians (for which the light was RED) prevented me and a bunch of other people (cars included) from doing just that, because they wen't paying any attention (and I'm fairly certain that it is not an exception at that particular intersection).
Another time, a drone forced me and a whoever was behind, to come to a COMPLETE STOP in an intersection when the light was GREEN because whatever he was doing on his phone was more important that his or others's people life.

Comment: Re:Speed penalty of encryption (Score 1) 124

sorry, I made a mistake : if the file: "/data/misc/adb/adb_keys" can't be open for any reason at all (fopen returns NULL), "ade.secure" is not set and it will accept connections from any computer (with root privileges no less). if it can be open , it is copied to / (in recovery) and "adb.secure" is set.

Comment: Re:Speed penalty of encryption (Score 1) 124

the cm recovery (i.e the one that gets built with the OTA package : out/target/product/hammerhead/recovery.img ) enforeces adb.secure, pre cm-12 looked like CWM, the new doesn't (and doesn't have a backup option either -not yet anyways-), if I clear the authorizations, I see a device in adb devices but it says simply offline, If I attempt to connect (ex: adb shell) it spits something that goes along those lines : "unlock the device, authorize then try again".

Comment: Re:Speed penalty of encryption (Score 1) 124

by kenshin33 (#49258147) Attached to: Google Backs Off Default Encryption on New Android Lollilop Devices
a locked bootloader will prevent you from changing 1 the bootloader itself, the recovery and the modem. Unlock it and you wipe the whole phone clean (including internal storage AKA sdcard in the case of a nexus device). if you install the public (you do not build it yourself makeing sure that it DOESN'T accept test keys and ENFORCES signature verification) build of any recovery out there you're at risk because of the simple fact that signature verification of OTA packages is either disabled or accepts the know, wildly available TEST KEYS!
Now ADB, since few years ago adb is always run in SECURE mode, meaning it will ASK when you connect the device a computer the first time (for that you need to unclock the device and ACCEPT), that is enforced in recovery (I don;t know about TWRP though, stcok CM does) that means if you never connected the device to any computer before, there's NO way in hell you're having access to ADB.
The only downside is backup in recovery, but for that you have Titanium, or helium they do a fine job (with titanium, you can even encrypt and upload the backup to some "cloud thingy out there")!.

Comment: Re:Speed penalty of encryption (Score 1) 124

by kenshin33 (#49186159) Attached to: Google Backs Off Default Encryption on New Android Lollilop Devices
Lock it. Once rooted, the bootloader is lockable/unlockable at will without wiping. Plus, you don;t need to keep it unlocked once the recovery is replaced.
Abd by default is in secure mode, meaning it need authorization, which is something honored by the recovery (CM's at least, can'st speak of other recoveries).
Last but not least, do you own builds and sign them with your own keys! (again CM's recovery installs only and only zips that are signed with the right release key). And then you can add the extra layer of encryption.
My beef with encryption is that it kills any chance of recovering the phone (cerberus, android device manager ... etc) if the phone is turned off.
Let's not forget the password thingy.

Invest in physics -- own a piece of Dirac!

Working...