I use Hangouts with Google phone number (voip). It works quite well and integrates nicely with Apple's CallKit.
* Google Voice is crippled Hangouts functionality. Why would they cut the Google talk functionality (or whatever it's called nowadays) - chat, voice and video between gmail users?
* No way to browse Google Voice application (like settings, messages, etc) while in call. This works just fine in Hangouts, but hey, it's Google. Probably a new dev team rewriting everything from scratch and reinventing the wheel.
* Finally it crashed on me while I tried a combination of sending myself SMS messages to Google Voice number while in Google Voice voip call. The call suddenly disconnected and when I started application it asked me if I want to send crash report.
Uninstalled and reconnected my Hangouts to Google phone number voice calls and SMS messages.
For Touch ID devices, you press the power button rapidly 5 times.
Thanks. Amazing tip.
Is there is a way to force this from iCould in case your phone gets confiscated? Now I imagine they can remove phone's network access by putting it into airplane mode or Faraday cage, then I would expect a feature "require lock code if can't contact iCloud servers for 24 hours" or similar. Apple should already have something similar in place for stolen devices. You can disable them from iCloud. But what happens if device has no network access to check policy?
What do I do? System architecture. Networking and security. No one in this house can touch me on that.
But does anyone appreciate that? While you were busy minoring in gender studies and singing a capella at Sarah Lawrence, I was gaining root access to NSA servers. I was one click away from starting a second Iranian revolution.
I prevent cross-site scripting, I monitor for DDoS attacks, emergency database rollbacks, and faulty transaction handlings. The Internet heard of it? Transfers half a petabyte of data every minute. Do you have any idea how that happens? All those YouPorn ones and zeroes streaming directly to your shitty, little smart phone day after day? Every dipshit who shits his pants if he can't get the new dubstep Skrillex remix in under 12 seconds? It's not magic, it's talent and sweat. People like me, ensuring your packets get delivered, un-sniffed. So what do I do? I make sure that one bad config on one key component doesn't bankrupt the entire fucking company. That's what the fuck I do.
Very similar story here. I bought PS3 for Bluray functionality and Linux factor. Did I run Linux on it? No. But I knew I could if I wanted. Until they removed the functionality. I bought 0 games, because I didn't buy PS3 for gaming. I never logged into PSN.
If you want car analogy it's like buying a pimped out 4x4 offroad SUV but never going offroad with it. Then company silently removes 4x4 capabilities but you can only get compensated for it if you used your vehicle offroad at least once... What the actual fuck?
"If you have to fill out cloudflare captchas when browsing, then maybe." Maybe... just maybe. In my case Google simply refused to work. They have a landing page that basically says "fuck you", not even a captcha. Interesting thing was that sometimes it worked. I tracked it down to the IPv6 version of google.com. Turned out that when it did work it was the IPv4 version that worked. I'm using Comcast with native IPv6 via DHCPv6 prefix delegation. Probably some other subscriber was participating in botnet with IPv6 address and Google decided to ban a large prefix. It's not like IPv4 when you can ban just a single address and every other device behind NAT is automatically banned. How do they decide prefix length of IPv6 to ban? I have no idea. The problem is they have banned more than just that 1 offender. So, yeah, you could say that IPv6 makes things worse...
* LG P509 (3.2" screen, Android 2.3) - Have 2 of those. Going strong with some old Cyanogen Mod version (7 I think) but I'm not really actively using them..
* Google Galaxy Nexus: Obsoleted by manufacturer. Also had cracked screen, the crack was small initially but then got bigger and bigger. Don't remember dropping it. OLED burn-in. Battery was not holding charge after 2 years but at least it was serviceable. Overall rating: crap (mainly due to poor screen). Granted it has been my best experience with Google Nexus line.
* Google Nexus 7 1st gen: Faulty charger circuit (took a day to fully charge, common issue). I configured it with encrypted file system, but little did I know then that Google released it without even testing it. Eventually it got slow to a point where a single operation would take 5 seconds to refresh screen - no TRIM support for encrypted fs driver, slow software encryption are the culprits if anyone is interested. Got rid of this shit the first chance I could (traded in for $50 BestBuy giftcard).
* Google Nexus 4: This is the biggest garbage of them all. Faulty hardware design - no cpu heatsink (or was it gpu?), battery too close to cpu and gpu. More info about this here: http://forum.xda-developers.co... . When you run any cpu-intensive app it would overheat so much that it gets uncomfortable to hold phone. Charger circuit would cut off battery charging due to high temperature. If you are not on charger it would reboot the phone at some point. That's how hot it was getting. The cpus are binned slow, nominal, fast. Luckily mine was "fast" so I was able to significantly undervolt this (yes, had to recompile the kernel) to make it somewhat better. It still randomly shuts down sometimes but not as bad as it was. Oh yeah, obsoleted by manufacturer (no updates).
At this point I stopped buying Android crap.
Personal anecdotal data (Apple devices):
* iPad 2: Still going strong with latest iOS. Granted the OS upgrade has made it very slow but this is only when you are starting apps or in main screen. Once app loads it's OK. Switching between apps is slow. I can't wait for it to die because it is super slow and I hate the low resolution screen but it just keeps on going.
* iPad Mini 2 - Have 2 of those. My favorite. Going strong.
* iPhone 5S - Have 2 of those. Going strong.
I know this is very anecdotal but I haven't had a single Apple device fail or require some tinkering to make it work.
This is a good solution but is there a way to add exceptions for some sites? If yes, which browser is this? I don't want to go through extra verification when logging into my online banking site because the cookies are missing or having to log into e.g. slashdot every time I restart the browser.
Maybe a feature to override cookie TTL can solve this. Force maximum lifetime of cookie to be 30 seconds (configurable) except for whitelist hosts.
Need browser feature that removes all cookies created by tab when tab is closed. Have ability to add exceptions for sites where you want the cookies to persist (like banking, slashdot, etc).
Does anything like that exist?
Incognito mode is great and all but I need exceptions to handful of sites where I want the cookies to persist.
My family switched from Android phones to iPhones a few months ago. Bought iPhones 5S $150 ea new. Had to do additional carrier unlock for $30 (it was locked to Sprint, I'm on super cheap T-Mobile MVNO). Can't beat that price. 5SE may have better camera and CPU but I don't see a need for that. 5S is still snappy and is not lagging.
The reason I switched, in case anyone is interested, is because Google is shit: https://code.google.com/p/andr... Are you fucking kidding me Google? It's been a year since this regression was reported and noone gives a shit. My option was to downgrade to Android 4 and live with security holes, fix it myself or toss the phone. Fixing it myself is an OK option but I'm too old for that shit.
Avoid an infinite loop that can occur when verifying a message with an unknown hash function OID. Diff based on OpenSSL. Fixes CVE-2015-1792 (however, this code is not enabled/built in LibreSSL). ok doug@ miod@
Avoid a potential out-of-bounds read in X509_cmp_time(), due to missing length checks. Diff based on changes in OpenSSL. Fixes CVE-2015-1789. ok doug@
Avoid an infinite loop that can be triggered by parsing an ASN.1 ECParameters structure that has a specially malformed binary polynomial field. Issue reported by Joseph Barr-Pixton and fix based on OpenSSL. Fixes CVE-2015-1788. ok doug@ miod@
I'm sorry, but Nexus 7 slow charging is anything but a rare problem. Run a search maybe? Google doesn't care. It's not charger problem and it's not a cable problem. The problem is either software or charger circuit. I just don't have time to hack this POS hardware, software to get it working.
I also have the charging problem on my original Nexus 7 as well as other headaches -- no TRIM support with encrypted partitions, super slow. Not really using that Google garbage anymore. Bought iPad Mini with retina and never looked back. I guess I'm too old for this hacking shit to get it working.
It's not just Nexus 7. Google seems to fuck up everytime they do a software update. I also have Nexus 4 and after 5.1 OTA upgrade device displayed error and was bricked. Not an issue for me as I can just go and install factory image wia fastboot but I did a search and a lot of users are hitting this issue and they don't know anything about fastboot or installng android sdk just to fix Googles failure to QA crap they are releasing.
Wi-Fi stopped reconnecting in sleep mode since 5.0 on my Nexus 4. It just seems that Google keeps breaking functionality with every update. I actually opened an issue in their tracker for this as it kinda is important for me https://code.google.com/p/andr... I'd go back to 4.4.4 but of course they had to make encrypted data partition backwards incompatible.
I'm fed up with issues I've had with Google Nexus line Android devices: 1) Nexus 7 first gen. Enable encryption and device becomes superslow due to not having a proper fstrim support. 2) Galaxy Nexus. No more updates after 4.3, not even security updates. 3) Nexus 4. This recent dialer issue. I'm still getting updates but what good are they if they only break things that worked before?
Producer-consumer with lock-free implementation. Producer thread (or threads) queues to linked list atomically (insert at head using compare-and-exchange). Consumer thread periodically empties the list by exchanging head pointer with NULL (compare-and-exchange). To make this list FIFO, consumer will now need to reverse the list.
Why not doubly linked list? Because we want a lock-free implementation for scalability.
Hint: you can still see the onld screen with new permissions marked as NEW by scrolling all the way down in app description to PERMISSIONS and clicking on"View details".
But I completely agree with you. Totally lame move by Google. I want to see this screen when I press the update button. Config option for advanced users would be sufficient.
Did you actually measure it (adrobench storage read/write test for example) and did not find any difference? I'm assuming not and since Nexus 5 is fast to begin with there isn't any *noticable* difference.
Only recently (KitKat release) Google added TRIM support for encrypted volumes. Without that the performance difference between unencrypted (with TRIM) and encrypted (no TRIM) was very noticable after device was used for some time. Unlucky for owners of older devices (1st gen Nexus 7, Galaxy Nexus) it does not work. This problem is very serious on 1st gen Nexus 7, to the point where it becomes unusable if encryption is used: https://code.google.com/p/andr...
No, android does not have full device encryption unfortunately. Only the encryption of/data partition. In most cases this should be sufficient though.
I'm not sure about external sdcard for devices that have it. I have Nexus so emulated sdcard is part of/data and it gets encrypted. If that is not the case with external sdcard, tough luck.
Also, doesn't look like google particularry cares about older devices and device encryption. See this issue for example (TRIM support on encrypted volume): https://code.google.com/p/andr... I'm not holding my breath to ever get this resolved for my 1st gen Nexus 7.
Recent Jellybean versions require adb authentication. You have to accept adb client's private key from the phone and the phone has to be unlocked before you can do so.
You can disable this "feature" with a hammer. It's pretty straightforward and I've done that with my Visa Paywave cards. Punching the hole will also work but I'm not sure if such card will be accepted by merchants. If your credit card has both RFid (like Visa Paywave) and chip/pin contacts, destroying RFid chip will also most likely destroy chip/pin interface because they would likely be packaged on the same chip.
I also find this a ReallyBadIdea(TM), at least not being able to have it turned off, as I frequently travel in crowded areas rips for the sort of proximity attacks described.
Tracfone SIM cards only work in Tracfone phones. There are cheaper pay as you go GSM plans, for example Spotmobile ($0.10/min, min recharge $5 every 120 days, uses T-Mobile and AT&T networks).
Actually, they just watch downloads. I have a hacked emule client that does not allow uploads (I know, I know, I'm bad) and received email from micros~1. Subject says: "NOTICE OF POTENTIAL UNLAWFUL DISTRIBUTION OF MICROSOFT SOURCE". I too noticed my download jumping to unusual speeds. So they are not tracking clients who upload, but downloaders assuming that if you download, you must be uploading. Well in my case it is total b/s.
Slashdot Mirror
Decided to give it a go on iPhone.
I use Hangouts with Google phone number (voip). It works quite well and integrates nicely with Apple's CallKit.
* Google Voice is crippled Hangouts functionality. Why would they cut the Google talk functionality (or whatever it's called nowadays) - chat, voice and video between gmail users?
* No way to browse Google Voice application (like settings, messages, etc) while in call. This works just fine in Hangouts, but hey, it's Google. Probably a new dev team rewriting everything from scratch and reinventing the wheel.
* Finally it crashed on me while I tried a combination of sending myself SMS messages to Google Voice number while in Google Voice voip call. The call suddenly disconnected and when I started application it asked me if I want to send crash report.
Uninstalled and reconnected my Hangouts to Google phone number voice calls and SMS messages.
An obvious lower bound is n! + n - 1
Only for very small values of n. Things get a bit more complex when n > 3.
The anonymous 4chan poster’s lower bound from TFA is n! + (n – 1)! + (n – 2)! + n – 3.
For Touch ID devices, you press the power button rapidly 5 times.
Thanks. Amazing tip.
Is there is a way to force this from iCould in case your phone gets confiscated?
Now I imagine they can remove phone's network access by putting it into airplane mode or Faraday cage, then I would expect a feature "require lock code if can't contact iCloud servers for 24 hours" or similar. Apple should already have something similar in place for stolen devices. You can disable them from iCloud. But what happens if device has no network access to check policy?
https://sensor-js.xyz/demo.htm...
Indeed it works on my iPhone. Javascript can read Orientation, Accelerometer (including gravity) and Gyroscope sensors in real time.
What do I do? System architecture. Networking and security. No one in this house can touch me on that.
But does anyone appreciate that? While you were busy minoring in gender studies and singing a capella at Sarah Lawrence, I was gaining root access to NSA servers. I was one click away from starting a second Iranian revolution.
I prevent cross-site scripting, I monitor for DDoS attacks, emergency database rollbacks, and faulty transaction handlings. The Internet heard of it? Transfers half a petabyte of data every minute. Do you have any idea how that happens? All those YouPorn ones and zeroes streaming directly to your shitty, little smart phone day after day? Every dipshit who shits his pants if he can't get the new dubstep Skrillex remix in under 12 seconds? It's not magic, it's talent and sweat. People like me, ensuring your packets get delivered, un-sniffed. So what do I do? I make sure that one bad config on one key component doesn't bankrupt the entire fucking company. That's what the fuck I do.
http://siliconvalleyism.com/si...
Very similar story here. I bought PS3 for Bluray functionality and Linux factor. Did I run Linux on it? No. But I knew I could if I wanted. Until they removed the functionality.
I bought 0 games, because I didn't buy PS3 for gaming. I never logged into PSN.
If you want car analogy it's like buying a pimped out 4x4 offroad SUV but never going offroad with it. Then company silently removes 4x4 capabilities but you can only get compensated for it if you used your vehicle offroad at least once... What the actual fuck?
"If you have to fill out cloudflare captchas when browsing, then maybe."
Maybe... just maybe.
In my case Google simply refused to work. They have a landing page that basically says "fuck you", not even a captcha. Interesting thing was that sometimes it worked. I tracked it down to the IPv6 version of google.com. Turned out that when it did work it was the IPv4 version that worked.
I'm using Comcast with native IPv6 via DHCPv6 prefix delegation. Probably some other subscriber was participating in botnet with IPv6 address and Google decided to ban a large prefix. It's not like IPv4 when you can ban just a single address and every other device behind NAT is automatically banned. How do they decide prefix length of IPv6 to ban? I have no idea. The problem is they have banned more than just that 1 offender.
So, yeah, you could say that IPv6 makes things worse...
My personal anecdotal data (Android devices):
* LG P509 (3.2" screen, Android 2.3) - Have 2 of those. Going strong with some old Cyanogen Mod version (7 I think) but I'm not really actively using them..
* Google Galaxy Nexus: Obsoleted by manufacturer. Also had cracked screen, the crack was small initially but then got bigger and bigger. Don't remember dropping it. OLED burn-in. Battery was not holding charge after 2 years but at least it was serviceable. Overall rating: crap (mainly due to poor screen). Granted it has been my best experience with Google Nexus line.
* Google Nexus 7 1st gen: Faulty charger circuit (took a day to fully charge, common issue). I configured it with encrypted file system, but little did I know then that Google released it without even testing it. Eventually it got slow to a point where a single operation would take 5 seconds to refresh screen - no TRIM support for encrypted fs driver, slow software encryption are the culprits if anyone is interested. Got rid of this shit the first chance I could (traded in for $50 BestBuy giftcard).
* Google Nexus 4: This is the biggest garbage of them all. Faulty hardware design - no cpu heatsink (or was it gpu?), battery too close to cpu and gpu. More info about this here: http://forum.xda-developers.co... . When you run any cpu-intensive app it would overheat so much that it gets uncomfortable to hold phone. Charger circuit would cut off battery charging due to high temperature. If you are not on charger it would reboot the phone at some point. That's how hot it was getting. The cpus are binned slow, nominal, fast. Luckily mine was "fast" so I was able to significantly undervolt this (yes, had to recompile the kernel) to make it somewhat better. It still randomly shuts down sometimes but not as bad as it was. Oh yeah, obsoleted by manufacturer (no updates).
At this point I stopped buying Android crap.
Personal anecdotal data (Apple devices):
* iPad 2: Still going strong with latest iOS. Granted the OS upgrade has made it very slow but this is only when you are starting apps or in main screen. Once app loads it's OK. Switching between apps is slow. I can't wait for it to die because it is super slow and I hate the low resolution screen but it just keeps on going.
* iPad Mini 2 - Have 2 of those. My favorite. Going strong.
* iPhone 5S - Have 2 of those. Going strong.
I know this is very anecdotal but I haven't had a single Apple device fail or require some tinkering to make it work.
This is a good solution but is there a way to add exceptions for some sites? If yes, which browser is this?
I don't want to go through extra verification when logging into my online banking site because the cookies are missing or having to log into e.g. slashdot every time I restart the browser.
Maybe a feature to override cookie TTL can solve this. Force maximum lifetime of cookie to be 30 seconds (configurable) except for whitelist hosts.
Need browser feature that removes all cookies created by tab when tab is closed. Have ability to add exceptions for sites where you want the cookies to persist (like banking, slashdot, etc).
Does anything like that exist?
Incognito mode is great and all but I need exceptions to handful of sites where I want the cookies to persist.
My family switched from Android phones to iPhones a few months ago. Bought iPhones 5S $150 ea new. Had to do additional carrier unlock for $30 (it was locked to Sprint, I'm on super cheap T-Mobile MVNO). Can't beat that price.
5SE may have better camera and CPU but I don't see a need for that. 5S is still snappy and is not lagging.
The reason I switched, in case anyone is interested, is because Google is shit: https://code.google.com/p/andr...
Are you fucking kidding me Google? It's been a year since this regression was reported and noone gives a shit. My option was to downgrade to Android 4 and live with security holes, fix it myself or toss the phone.
Fixing it myself is an OK option but I'm too old for that shit.
LibreSSL patches today:
Avoid an infinite loop that can occur when verifying a message with an unknown hash function OID.
Diff based on OpenSSL.
Fixes CVE-2015-1792 (however, this code is not enabled/built in LibreSSL).
ok doug@ miod@
Avoid a potential out-of-bounds read in X509_cmp_time(), due to missing length checks.
Diff based on changes in OpenSSL.
Fixes CVE-2015-1789.
ok doug@
Avoid an infinite loop that can be triggered by parsing an ASN.1
ECParameters structure that has a specially malformed binary polynomial field.
Issue reported by Joseph Barr-Pixton and fix based on OpenSSL.
Fixes CVE-2015-1788.
ok doug@ miod@
I'm sorry, but Nexus 7 slow charging is anything but a rare problem. Run a search maybe? Google doesn't care. It's not charger problem and it's not a cable problem. The problem is either software or charger circuit. I just don't have time to hack this POS hardware, software to get it working.
I also have the charging problem on my original Nexus 7 as well as other headaches -- no TRIM support with encrypted partitions, super slow. Not really using that Google garbage anymore. Bought iPad Mini with retina and never looked back. I guess I'm too old for this hacking shit to get it working.
It's not just Nexus 7. Google seems to fuck up everytime they do a software update. I also have Nexus 4 and after 5.1 OTA upgrade device displayed error and was bricked. Not an issue for me as I can just go and install factory image wia fastboot but I did a search and a lot of users are hitting this issue and they don't know anything about fastboot or installng android sdk just to fix Googles failure to QA crap they are releasing.
Wi-Fi stopped reconnecting in sleep mode since 5.0 on my Nexus 4. It just seems that Google keeps breaking functionality with every update.
I actually opened an issue in their tracker for this as it kinda is important for me https://code.google.com/p/andr...
I'd go back to 4.4.4 but of course they had to make encrypted data partition backwards incompatible.
I'm not buying an Android device ever again.
https://code.google.com/p/andr...
This is ridiculous.
I'm fed up with issues I've had with Google Nexus line Android devices:
1) Nexus 7 first gen. Enable encryption and device becomes superslow due to not having a proper fstrim support.
2) Galaxy Nexus. No more updates after 4.3, not even security updates.
3) Nexus 4. This recent dialer issue. I'm still getting updates but what good are they if they only break things that worked before?
Honest real life application:
Producer-consumer with lock-free implementation.
Producer thread (or threads) queues to linked list atomically (insert at head using compare-and-exchange).
Consumer thread periodically empties the list by exchanging head pointer with NULL (compare-and-exchange). To make this list FIFO, consumer will now need to reverse the list.
Why not doubly linked list? Because we want a lock-free implementation for scalability.
Hint: you can still see the onld screen with new permissions marked as NEW by scrolling all the way down in app description to PERMISSIONS and clicking on"View details".
But I completely agree with you. Totally lame move by Google. I want to see this screen when I press the update button. Config option for advanced users would be sufficient.
Gentoo doesn't keep the source in the repository, but it has the hashes. /usr/portage/app-crypt/truecrypt/Manifest:
from
DIST truecrypt-7.1a.tar.gz 1949303 SHA256 e6214e911d0bbededba274a2f8f8d7b3f6f6951e20f1c3a598fc7a23af81c8dc SHA512 b5e766023168015cb91bfd85c9e2621055dd98408215e02704775861b5070c5a 0234a00c64c1bf7faa34e6d0b51ac71cd36169dd7a6f84d7a34ad0cfa304796a WHIRLPOOL 5e7f4360746a30639aea96eaf4deac268289c111c0efa96f50487527f0406499 2c26ad4c8ae0fd565d80e77f0ce8add82b03930d877fe5adedc8a733b482fe38
(the filter did not like awful long strings of letters so I added spaces to WHIRLPOOL and SHA512 hash strings.
Did you actually measure it (adrobench storage read/write test for example) and did not find any difference?
I'm assuming not and since Nexus 5 is fast to begin with there isn't any *noticable* difference.
Only recently (KitKat release) Google added TRIM support for encrypted volumes. Without that the performance difference between unencrypted (with TRIM) and encrypted (no TRIM) was very noticable after device was used for some time.
Unlucky for owners of older devices (1st gen Nexus 7, Galaxy Nexus) it does not work. This problem is very serious on 1st gen Nexus 7, to the point where it becomes unusable if encryption is used: https://code.google.com/p/andr...
No, android does not have full device encryption unfortunately. Only the encryption of /data partition. In most cases this should be sufficient though.
I'm not sure about external sdcard for devices that have it. I have Nexus so emulated sdcard is part of /data and it gets encrypted. If that is not the case with external sdcard, tough luck.
Also, doesn't look like google particularry cares about older devices and device encryption. See this issue for example (TRIM support on encrypted volume): https://code.google.com/p/andr...
I'm not holding my breath to ever get this resolved for my 1st gen Nexus 7.
Recent Jellybean versions require adb authentication. You have to accept adb client's private key from the phone and the phone has to be unlocked before you can do so.
You can disable this "feature" with a hammer. It's pretty straightforward and I've done that with my Visa Paywave cards. Punching the hole will also work but I'm not sure if such card will be accepted by merchants.
If your credit card has both RFid (like Visa Paywave) and chip/pin contacts, destroying RFid chip will also most likely destroy chip/pin interface because they would likely be packaged on the same chip.
I also find this a ReallyBadIdea(TM), at least not being able to have it turned off, as I frequently travel in crowded areas rips for the sort of proximity attacks described.
You can turn the chip off with a hammer.
Tracfone SIM cards only work in Tracfone phones.
There are cheaper pay as you go GSM plans, for example Spotmobile ($0.10/min, min recharge $5 every 120 days, uses T-Mobile and AT&T networks).
What feature on the 300D unlocked by the hacked 10D firmware do you find most useful? (this is a genuine question)
+ Changing RAW Embedded JPEG quality to save space when shooting raw.
+ 1/200 Flash sync speed in Av mode.
+ Flash exposure compensation
Actually, they just watch downloads. I have a hacked emule client that does not allow uploads (I know, I know, I'm bad) and received email from micros~1.
Subject says: "NOTICE OF POTENTIAL UNLAWFUL DISTRIBUTION OF MICROSOFT SOURCE".
I too noticed my download jumping to unusual speeds.
So they are not tracking clients who upload, but downloaders assuming that if you download, you must be uploading. Well in my case it is total b/s.