All Projects

This prevents reading files from external (or emulated external) storage in API 19 and above (Kitkat, until then it wasn’t enforced).

See: http://developer.android.com/reference/android/Manifest.permission.html#READ_EXTERNAL_STORAGE

The share button correct behaviour when no file is selected is to fire file selection, but after sharing and un-sharing a file it no longer behaves like that, instead doing nothing but activating and deactivating itself when tapped.

No need for description

This is a meta-item depending on bugs/features required to complete before releasing QFS 0.12

No need for description

No need for description

No need for description

It would be better to only use it to start the server

Sometimes a negated type will be ignored.

e.g.:

Fine:

$ relevation -t website java.net

-> Search "java.net" ('website' entries):  1 matches

$ relevation -t -website java.net

-> Search "java.net" ('not website' entries):  No results

Not fine:

$ relevation google.com

-> Search "google.com" ('not folder' entries):  6 matches

$ relevation google.com | grep -c ^Type:\ website
5

$ relevation -t -website google.com

-> Search "google.com" ('not website' entries):  6 matches
$ relevation  -t -website google.com | grep -c ^Type:\ website
5

$ relevation -t website google.com

-> Search "google.com" ('website' entries):  5 matches

Might be due to entries inside folders being repeated?

When the decryption password is wrong a zlib exception is raised:

Traceback (most recent call last):
  File "/usr/bin/relevation", line 359, in <module>
    main()
  File "/usr/bin/relevation", line 332, in main
    xmldata = zlib.decompress(cleardata_gz[:-padlen], 15, 2**15)
zlib.error: Error -3 while decompressing data: incorrect header check

Should handle more gracefully

Files should be checked for the appropriate format instead of blindly opening them

main(sys.argv[1:])
  File "./relevation.py", line 628, in main
    numhits = dump_all_entries(xmldata)
  File "./relevation.py", line 213, in dump_all_entries
    return dump_result(res, 'all')
  File "./relevation.py", line 290, in dump_result
    dumpfn(typeName, name, descr, notes, fields)
  File "./relevation.py", line 253, in dump_single_result
    print s
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in position 19: ordinal not in range(128)

Traceback (most recent call last):
  File "./relevation.py", line 658, in <module>
    main(sys.argv[1:])
  File "./relevation.py", line 638, in main
    numhits += dump_entries(xmldata, needles, 'folder', caseInsensitive, True)
  File "./relevation.py", line 224, in dump_entries
    res = tree.xpath(xpath)
  File "lxml.etree.pyx", line 1509, in lxml.etree._Element.xpath (src/lxml/lxml.etree.c:50702)
  File "xpath.pxi", line 306, in lxml.etree.XPathElementEvaluator.__call__ (src/lxml/lxml.etree.c:145829)
  File "apihelpers.pxi", line 1395, in lxml.etree._utf8 (src/lxml/lxml.etree.c:26485)
ValueError: All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters

Meta-task depending on tasks scheduled for the 1.1 release

PyCryptoPlus is a drop-in replacement for PyCrypto written in Python, meaning it can run much more easily on Windows.

lxml provides a cleaner (or more pythonic) implementation, is easier to install and more commonly required.

cryptopy provides a pure python implementation of ciphers, allowing easier install on some systems (e.g. 64bits Windows) than PyCrypto.
Unlike PyCryptoPlus it doesn’t seem to depend on PyCrypto but has a different API.

The performance degrades considerably, of course.