This file is indexed.

/usr/share/doc/parcimonie/TODO is in parcimonie 0.8-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
* Robustness++
  - The applet does not get the daemon signals anymore after the latter was
    restarted. It should periodically check if it's still connected to the
    daemon's D-Bus signals, and try to reconnect if needed.
  - Don't wait indefinitely for spawned gpg processes. Somehow timeout.

* User feedback
  - custom applet icons
    Inspiration:
      /usr/share/icons/hicolor/48x48/status/aptdaemon-add.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-cleanup.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-delete.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-download.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-resolve.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-update-cache.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-upgrade.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-wait.png
      /usr/share/icons/hicolor/48x48/status/aptdaemon-working.png
    and background:
      /usr/share/icons/hicolor/48x48/apps/seahorse.png
  - log/tooltip message: tell "parcimonie is resting until $TIME"
    rather than just "Resting"
  - avoid passing "at .../../xxx.pm" in the signal message
  - non-desktop log viewer:
    Either log to syslog instead of sending D-Bus signals,
    or fork a tiny D-Bus signal receiver + dispatcher early in the main daemon
    startup process.
  - painful torsocks "error" output filtering does not work

* l10n/i18n:
  - documentation for translators
  
* Add functional tests, probably using Test::Trap.

* Write design documentation: threat and risk models, hypothesis, etc.

* Debian packaging
  - Split into two binary packages: parcimonie and parcimonie-applet

* Make sure an update is attempted for every key on a regular basis.
  Remember last time a given key update has been attempted, and randomly
  pick the key to update among the oldest-updated keys. Beware: key update
  attempt time shall be recorded instead of successful key update time,
  else there is a risk to loop trying to update keys that are not available
  on the keyserver.

* Improve tests coverage
  - App::Parcimonie::Role::HasEncoding and
    App::Parcimonie::Role::HasCodeset could be quite easily tested

* Bug: starting parcimonie outside of X fails
  org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

* Test suite: configure, use and run Tor