[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    [gSOC] Encrypted and signed koffice files
From:       Brad Hards <bradh () frogmouth ! net>
Date:       2006-04-19 8:26:40
Message-ID: 200604191826.48945.bradh () frogmouth ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


G'day,

In a time past, I did some minor work on KOffice. One day I found this bug:
https://bugs.kde.org/show_bug.cgi?id=24399
which is a wishlist item for encrypting KOffice files.

The Oasis format has a particular way of doing this (see bug for more details, 
but basically it compresses each file, and then encrypts using blowfish, then 
builds the zip file). I wanted a Qt interface for the crypto, and have spent 
about the last year and a half working on QCA (which can now do a lot more 
than is required for straight encryption / decryption).

It would make a reasonable Google Summer of Code project to actually connect 
this to KOffice. In addition to calling the right crypto functions with the 
right arguments, there is also obviously going to be some work on parsing the 
XML metadata and of course some appropriate user-interface changes.

Task deliverables could include appropriate manual changes and a test suite. 
Test documents could be contributed to one or more of the various collections 
that are emerging.

To make the task more challenging, it could be extended to include digital 
signature support. I understand OpenOffice can do this, but it isn't 
described in the Oasis OpenDocument specification. The task could include 
deducing the way it works, writing up an addendum to the opendoc spec, 
implementing it in code (perhaps as a standalone tool as a proof of concept 
initially, then adding it to KOffice if time permitted).

Manik Chand Patnaik's competition proposal also has some interesting ideas 
along these lines: 
http://www.koffice.org/competition/gui1results/manik_chand_patnaik.pdf

I'm happy to co-supervise such a task (ideally with someone that understands 
the useability / GUI part), and can write this up in an alternative format if 
someone can point me to what that might be.

This task would have to be based on Qt4 (i.e. KOffice 2.0?) to use QCA2. I 
could probably still help a little with Qt3 version.

Thoughts? Comments?

Brad



[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]