Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: It's great and all that but can you use it to call (Score 3, Interesting) 172

by Pow (#49220685) Attached to: Google Announces Android 5.1

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?

Comment: Re:Hopefully the applicants had a relevent backrou (Score 2) 809

by Pow (#49049851) Attached to: Ask Slashdot: What Portion of Developers Are Bad At What They Do?

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.

Comment: Re:New Permissions (Score 4, Informative) 249

by Pow (#47215537) Attached to: New Permission System Could Make Android Much Less Secure

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.

Comment: Re:7.1a for x64 linux (Score 2) 146

by Pow (#47206645) Attached to: Auditors Release Verified Repositories of TrueCrypt

Gentoo doesn't keep the source in the repository, but it has the hashes.
from /usr/portage/app-crypt/truecrypt/Manifest:

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.

Comment: Yes, seriously (Score 1) 374

by Pow (#46457821) Attached to: Ask Slashdot: How Can I Prepare For the Theft of My Android Phone?

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...

Comment: Re:Android Has Full Device Encryption (Score 1) 374

by Pow (#46451569) Attached to: Ask Slashdot: How Can I Prepare For the Theft of My Android Phone?

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.

Comment: Re:Is it possible to disable it on the card? (Score 1) 273

by Pow (#38870631) Attached to: Shmoocon Demo Shows Easy, Wireless Credit Card Fraud

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.

"You're a creature of the night, Michael. Wait'll Mom hears about this." -- from the movie "The Lost Boys"

Working...