[Tickets #811] new horde application

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=811
-----------------------------------------------------------------------
 Ticket             | 811
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | new horde application
 Queue              | Horde Base
 Version            | HEAD
-State              | Assigned
+State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | Horde Developers
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2005-02-15 09:54) wrote:

I finally found some time to take a look at this application. Beside that it
still needs a *lot* of cleanup in the code, UI, and documentation, there are
a few issues I'd like to discuss:
- I'm not sure if I like the concept of all data being encrypted by a global
password. While I see that this might be  necessary for shared passwords, I
personally would never store a password in such a system. One should at
least be able to select a personal or group password instead of the global
one.
- Instead of creating a separate permissions system, Horde's permissions
should be used instead, or even better, the password groups should be
implemented as Horde Shares.
- Horde's Crypt or Cipher API should be used for en-/decryption and maybe
the admin should be able to configure the cipher.
- The password group subscription doesn't make sense to me. If at all the
groups should be imlemented as shares (see above) and selectable like the
shares in other Horde applications. The password list should simply show all
passwords from all selected shares.