 ?
 Trusted Contacts
 Its a new app in the Play Store
 yep, just downloaded it
 so i just spend about 10 minutes looking for a blank dvd (don't judge) because the kali installer would just not work
 i tried one last thing with the usb installer, and was almost sure it wasn't going to work, at which point i was looking for the dvd
 when i found one, the imager was finished... of course THAT'S the one that freaking worked, making the whole DVD thing moot
 Hey dude...  seriously...  get a freakin' 2 TB thumb drive for $12.  https://www.wish.com/search/2tb%20thumb%20drive#cid=576ca282393a5c6fbd1aa864
 the wish?
 china stuff
 It's a reality.
 have you gotten yours yet?
 coming on 30dec.
 i'll wait until you confirm that it's legit
 I got a few things from wish so far...  Christmas lights, and some other misc stuff.  It was recommended by a coworker who uses it all the time.
 hm...
 Don't get me wrong. it's cheap crap!  but it's cheap crap!
 true, i'd say if in a bind, it would be good, but it takes a month to get there, lol
 Well, i have just one thing to say about that....  2TB thumb drive
 How long would it take you to haul 2,000,000,000,000,000 bytes?
 technically more than that
 but that's like saying how long would it take you to haul 2,000,000,000,000 microliters?
 heh, yeah, but your thumb drive is probably only 8, or 16 gigs.
 @govatent - http://www.androidpolice.com/2016/12/07/bloomberg-pebble-time-2-pebble-core-canceled-part-fitbit-buyout-kickstarter-pledges-refunded/
 https://source.android.com/compatibility/7.0/android-7.0-cdd.html#9_10_device_integrity
 please read this and tell me if it is required that the user be provided a way to boot the device if the system verification fails.
 Reading
 Thanks.  They used proper RFC2119 rules throughout the document.  the sentance regarding this is just confusing though.  They said MUST NOT boot, unless.....  but they didn't say must be given the option to boot.
 MUST NOT allow boot to complete when system verification fails, unless the user consents to attempt booting anyway, in which case the data from any non-verified storage blocks MUST not be used
 Yeah.
 That's a confusing sentence.  They don't say must be allowed to boot.
 they don't say the user must be given the option to concent.
 That says to me that the boot process must be halted and some sort of a prompt be displayed to the user to tell them the system has been modified or does not pass the validation. Ideally they should also see a warning of the risks this may have, They should then be given the option to proceed after agreeing to the risk.
 sure, and I see the key word SHOULD, there as well
 but it's just not written.
 ok.
 But the part of it that does not make sense is " in which case the data from any non-verified storage blocks MUST not be used"
 It's talking about corruption or modification to a SYSTEM partition on Android.
 Maybe wipe userdata?
 if you modify the system partiton, it will cause this situation.
 If done officially yes, but if a root exploit modifies the system partition, it wont trigger a factory reset
 for Android 7.0 on deviecs with AES cryptio >50mbps that is.
 No, this isn't factory reset.  This is stopping the boot process to allow the user to know the device is modified.
 Unless they want it done the same way it is done on ChromeOS
 Android 6.0 + knows if the system partition is modified or not by default, using continuous checks from DM-Verity
 that's how it's done.
 I'm just trying to figure out if the OEM can legally shutdown the device if the System is modified according to that CCD above.
 I would hope not - It is one thing to drop support and some features (NFC payments/DRM/etc) but to actually brick or lock a user out of their own device is really a scary proposition.
 In my option, it comes down to who actually owns the device, the user or the OEM?
 This has industry-wide ramifications.  Verizon would have users bring devices back to service.
 Yeh, it is a very slippery slope.
 Wow - http://thehackernews.com/2016/12/linux-kernel-local-root-exploit.html
 Well, I just installed kali on my other laptop last night which is a rolling distro, so that side is safe
 Kali isn't exactly a "safe" distro.
 It likely hasn't been updated yet.
 You know what I mean, as far as the kernel goes
 It likely won't receive updates for a while.
 Ah, true
 Kali is an Offensive Security distro.  Ubuntu is a Defensive Security distro.
 or debian
 either way.
 I wouldn't really call ubuntu a security distro...
 More of a production distro
 Well, in terms of security updates, Ubuntu is generally first.
 Hmm....
 I think they just sent a security update to all versions of Ubuntu
 What I'm saying is: just like changes to Debian don't directly affect Ubuntu, changes to Ubuntu won't directly affect Kali.
 Ubuntu is proactive about defensive security.  Kali isn't known for that.
 Wow, T-Mobile may have made a huge security blunder
 https://twitter.com/JohnLegere/status/806556501070356480
 Look at the guy who logged in and got another customers information. I was able to replicate it and got 2 other customers details (phone number, email address and name)
 https://www.xda-developers.com/t-mobile_digits_security/
 Yup. I want to hear T-Mobiles response
 so what is DIGIT?
 It's like google voice for T-Mobile
 That was one of the ones I got, censored a bit
 oh
 wow @Ivoriesablaze 's LG Neon got Marshmallow