I wanna let you know that I released a new stable version and all of you should change to the keepassc package from aur as keepassc-git is thought as an unstable development version for the future. Furthermore the homepage and the whole project has moved to github: http://raymontag.github.com/keepassc/ Look there for the (big :-) changelog.

First. Thank you so much for this, KeePass is the only thing preventing me from throwing mono out.Second. Where is the donation button?

Third. It's missing two features preventing me from switching right now.- 2.0 database support ( I know it's coming )- Browser integration. On both firefox and chrome I'm using passifox to integrate with keepass , it autofillls, updates and saves passwords straight to database, could someone look into it? https://github.com/pfn/passifox/Would be MARVELOUS if someone could integrate one of the keyboard operated browsers (luakit, dwb, jumani, etc.) in such way with KeePassC.

Thank you for a great program. I am using it on Fedora. Python3-crypto and xsel were in the Fedora repos. I installed kppy and KeePassC manually and it works great.

I am also using Dropbox to share my password db between a few computers. I also use KeePassX, Keepass and iKeePass. I am thinking of using Bittorrent Sync instead of Dropbox, because I like the idea with it. Has anyone used it?

A small hint. You have to use 'python3 setup.py install' on fedora instead of 'python'. Otherwise it will be executed with python2. This could be added to the web page and README.

The last couple of weeks I worked sporadically on a server/client structure. If you want to give it a try you can use the git-package from AUR (possible that this branch hasn't some modifications from stable keepassc package!).

WARNING: At this moment information are sended in plain text! SSL/TLS-layer will be added soon!

Explanation:

- start the server with 'keepassc-server -d /path/to/database start' (for other options look at --help)- receive entry information with 'keepassc -dc -e ENTRY' (it's of course possible to connect to a remote server (i.e. not localhost which is default); again look at --help)- stop the server with 'keepassc-server stop'

Planned:

- add an optional ssl/tls-layer- send received information to the original keepassc interface

Added the (optional) SSL/TLS-layer. The protocol used is TLSv1. A manual will follow soon. For those who know how to create self-signed certificates:

- Create root certificate with filename cacert.pem- Create a server certificate and a server key with cacert.pem with filenames servercert.pem and serverkey.pem (Common Name: KeePassC Server)- Server-Side: Put servercert and serverkey to .local/share/keepassc/ (or your data directory specified by XDG_DATA_HOME/keepassc)- Client-Side: Do the same but with cacert.pem

Of course take care of your private keys!

That's it. Use -s option on both sides. Remember it's still WIP. E.g. it's not possible to run bot SSL and non-SSL and the server works non-threaded, everything is very unstable if sth. unexpected happens.

A new version (1.6.0) is out and in AUR. Bad news are: KeePass v.2.x is still not supported (but that's the next big thing...). Good news: KeePassC is ready for network! You can create a server and use KeePassC over your network (Internet should work though it's not tested as I've not the possibilities) or on localhost to omit password entering in conjunction with the included agent. Watch http://raymontag.github.com/keepassc/server.html for an introduction. Another nice new feature is that expired entries are marked red.

If someone has the possibilities to test this feature over the internet please let me know if it works. Both should work, entering the server ip or the domain.