qca/TODO
Justin Karneges 03777622a3 update
svn path=/trunk/kdesupport/qca/; revision=674779
2007-06-13 02:33:30 +00:00

81 lines
2.6 KiB
Plaintext

* beta7
api:
securemessage bytesWritten?
problem: pgp can cause token event while pgp store is available
textfilter: remove unnecessary SecureArray usage
code:
keystore: complete
securelayer: complete
other:
rename qca-openssl
update README/INSTALL, special thanks to Jack Lloyd
regenerate botantools.diff
* test1
doc:
documentation overhaul
document provider interface
Change Doxyfile config to capture whole API, and to generate Latex manual
code:
synchronizer: cleanup
publickey: cleanup
cert: cleanup
keystore: cleanup
securelayer: cleanup
securemessage: cleanup
add logging to qca lib and other plugins
add more asserts?
other:
finish cmssigner, set to 1.0
cmssigner: i'm getting a crash sometimes during sign.. test and trace
update the rootcerts with mozcerts
make sure the version is correct in all locations (README, etc)
* examples
create example for BigInteger
create example for OpenPGP
create example for CMS
create example for using TLS with smart cards (maybe reuse ssltest?)
fix SASL examples (client and server)
* additional unit tests (using QTestLib):
- OpenPGP
- CMS
- TLS ?
- SASL ?
- QPipe
- FileWatch / DirWatch
- Complete the pkits tests
* write plugin support
qca-botan: implement
qca-egads (or qca-egd): implement for Random support
* possibilities for the future:
publickey: sign/verify plaintext input uses secure memory. overkill?
cert: better makeFriendlyName diffing for key usage (consider OIDs) ?
qcatool: streaming securemessage operations
qcatool: instead of printing full usage at every wrong turn, we might try
to print something closer to the context
access to list of known cached certs, similar to how cmssigner works?
securemessage: ability to know which key has performed a decrypt?
emsa3Encode: implement in provider instead of qca?
OCSP
tls ocsp stapling
internally managed intermediate object storage
securemessage: algorithm selection for cms/pgp (and use SecurityLevel?)
tls: renegotiation
Key wrapping - RFC3217 and RFC3394
quoted-printable TextFilter
keygen on smart cards
keystore: symmetric keys, arbitrary app data
cert: any other fields we don't support but might be used out there
cert: support for arbitrary extensions?
cms: fine-grained control over smime attribs
convertToPublic should return a publickey rather than change itself
providers for:
Mozilla NSS
Windows CryptoAPI
Linux kernel crypto support, if the userspace API ever gets sorted out
Intel Performance Primatives library