3 ms·
I mean, competently implemented background indexing shouldn't be a security risk or a performance issue. Microsoft had those problems, too, when they introduce
by throwanem 10y ago
I mean, competently implemented background indexing shouldn't be a security risk or a performance issue.
Microsoft had those problems, too, when they introduced their own indexer with XP. Doing desktop support for slow XP boxes, you rapidly learned to disable the indexer first. But by roughly mid- to late Vista, it had ceased to be a general problem. (Maybe earlier; I had ceased to be closely involved with support by then.)
The other thing about an indexer like this is that you need it well integrated into the UI to get the benefit. macOS has Spotlight, which is excellent. Windows has Start search, which is OK for programs if you don't misspell the name, and tolerable for documents if you use the MS default home directory structure. I haven't used desktop Linux since Ubuntu 8 or so, so I don't know what it has, but if it is indeed a Spotlight-like experience they're shooting for, file indexing is just the start.
- josteink 10y ago> I mean, competently implemented background indexing shouldn't be a security risk or a performance issue. Except ofcourse in the 100% theoretical, never ever seen in the wild, case of bugs in file-format parsers. It's not like Linux's "file" or "strings"-utility[1] has had a local exploits in the past or anything. Uhm... So yeah... About that.... Back in the real world, this is a very real attack vector. Especially when it runs in the background on a large batch of files, automatically and unasked for. Note: I'm not saying I'm against indexing content for easier access and help locating files. I'm just saying that you can't simply dismiss it as a security-risk because it runs in the background. [1] http://lcamtuf.blogspot.no/2014/10/psa-dont-run-strings-on-untrusted-files.html http://lcamtuf.blogspot.no/2014/10/psa-dont-run-strings-on-u...