Follow Slashdot stories on Twitter


Forgot your password?
Slashdot Deals: Cyber Monday Sale! Courses ranging from coding to project management - all eLearning deals 25% off with coupon code "CYBERMONDAY25". ×

Comment Re:So I know something about this.... (Score 1) 242

So is it OK if I drop by and hand you my Galaxy S6, and start a timer to see how long it takes you to break in? I'd guess 8-10 hours of solid work for you, someone who appears knowledgeable in this area. That qualifies at least as "very difficult" to me, though perhaps I overstated it with "extraordinarily difficult".

You seem quite knowledgeable, and I find no fault with your analysis and subsequent posts, other than the quibble with the level of effort needed.

Comment So I know something about this.... (Score 5, Interesting) 242

Finally, a slashdot topic where I can be informative. Disclaimer: I work in the industry building fingerprint sensors.

Fingerprints aren't perfect security. As so many others have pointed out, you leave them everywhere. That doesn't mean that they're not useful.

1. It's extraordinarily difficult to create a fingerprint spoof from a latent print. Yes, there are people who can do it - I can do it - but it's not easy. Notice on the videos of breaking into the iPhone 5s or 6 that latent prints are taken from a single fingerprint placed carefully on a squeaky clean screen. On your average phone, not so much. Someone who picks up my phone off the seat in a subway will be incapable of breaking in - unless I've just cleaned the screen with windex and carefully placed my fingerprint on it.

2. A fingerprint on a phone makes an excellent two-factor authentication system. The average hacker in east Elbonia can't break fingerprint security - because they don't have my phone or my fingerprint.

Perfect? No, but strong? Yes.

Submission + - Busybox Deletes systemd Support

ewhac writes: On 22 October, in a very terse commit message, Busybox removed its support for the controversial 'systemd' system management framework. The commit was made by Denys Vlasenko, and passed unremarked on the Busybox mailing lists. Judging from the diffs, system log integration is the most obvious consequence of the change.

Comment Re:Why was package versioning left out? (Score 4, Insightful) 185

Because package versioning is not a language issue. It's a build issue, and should be part of your build system.

"But go get ... reaches out and..." Stop. go get isn't part of the Go langauge; it's the default Go build environment. And yes, it lacks many features you'd want in a so-called "professional" build system (whatever that means this week).

I get the impression that Go was perhaps intended to be used with repo, a tool principally used for managing the Android project, but also used elsewhere inside Google to manage large numbers of independent Git repositories. With repo, you establish a common branch or tag name across all the repositories that comprise your project, then "repo sync" to them. Poof! Build and version management. (Sorta.)

Comment *WIN-BATTERIES?!?* (Score 1) 42

Someone needs to punch this idea in the throat right now before it gets deployed anywhere.

Need I remind the membership of the decades-long clusterfsck resulting from so-called "Win-modems" whose codecs were moved from hardware into host software and to this day remain completely undocumented? Even people who put down hard cash for a WinModem driver found themselves left to twist in the wind when the 3.x kernel series came out (modems may be mostly obsolete, but FAXes aren't (yet)).

Now: Who would like to bet that the WinBattery interface will not significantly extend battery life over what we have now, remain completely undocumented (or trapped behind onerous licensing that forbids Open Source implementations), and leave Linux and *BSD users with systems with significantly shortened battery life because they can't control the power interface?

This is yet another naked attempt to bottle up critical system functionality behind a Microsoft-only wall (because apparently fscking everyone over with UEFI and (In-)Secure Boot wasn't enough).

Comment DO NOT WANT (Score 4, Interesting) 55

Let me see if I'm understanding this correctly.

You want me to install an invasive gaming client that delivers no actual game content to me, imposes a network lag on all input, does not allow me to run a zero-latency LAN gaming session, does not allow me to run my own public server for my friends... And your business model is to get me to pay for this degraded experience?

...Good luck.

Nothing is finished until the paperwork is done.