4
0
mirror of https://github.com/QuasarApp/qca.git synced 2025-05-10 17:59:33 +00:00
Justin Karneges c2d3bf934b lots todo!
svn path=/trunk/kdesupport/qca/; revision=499010
2006-01-16 20:12:20 +00:00

91 lines
3.2 KiB
Plaintext

* Additional unit tests
* Convert unit tests to QtTestLib
* Update to latest Botan, and remake the botantools patch as appropriate
* create .prf for auto-discovery by qmake-based projects
* ability to compile plugins in statically (check 'plugins' subdir)
* update the README
* special thanks to Jack Lloyd
* API documentation
clean up Algorithm
clean up Filter
document all the stuff in qca_securelayer.h
document all the stuff in qca_securemessage.h
think about documenting the various providers (qcaprovider.h)
Change Doxyfile config to capture whole API, and to generate Latex manual.
PKey has see-also references to uncallable functions (eg, toRSAPublicKey)
* Considerations
api:
make qca-gnupg's qpipe public?
add a None type for PKey?
cert extensions
include author/advertising info in plugin?
make sure there aren't any cases where a Foo::supportsBar()-style function
reports true, but then when the object is created, it doesn't actually
support the feature (because the wrong provider was used).
Q_DISABLE_COPY on some objects
give all classes non-default ctors/dtors/copy/op=, and dpointers?
add more "getters" to the library?
don't forget to QCA_EXPORT everything
it's possible we use QSecureArray in some unnecessary places
get rid of Cert/CertReq ::signature() ? it is quite useless, I think
other:
add asserts
standardize on count() vs size() when iterating?
printf + latin1()/toLatin1() -> qPrintable() ? (in code/examples/docs/etc)
* finish code for APIs:
plugin stuff for 4.1
Q_EXPORT_PLUGIN2
QLibrary::isLibrary()
interfaces?
better handling of static QCAPlugins:
we delete them, is this ok? maybe they are supposed to be persistent.
if deleted, how do we get them back?
don't create qobjects during init (that means you, keystoremanager)
qcatool should have an option to list qt plugin paths and plugins found
remove the quality enum for randomness? (see botan)
qca-openssl: we have email altname but not email DN?
securemessage: algorithm selection for cms/pgp (and use SecurityLevel?)
tls: SSL_get_client_CA_list
tls: renegotiation
cert/key mismatch error for cms (do we want this for TLS also?)
don't allow smart card providers to be used by default
functions that don't trip a scan should do so on the first try
proper parenting of all objects
dirwatch: thread safety
dirwatch: test on all platforms
if KeyStore::needPassphrase has no listener, reject the request somehow
qca-gnupg: ignore newlines from passphrase, to avoid advancing command-fd
core: properties
cert: rfc 2818 hostname validation
keystore: cleanup
securemessage
tls
sasl
* examples
create example for BigInteger
fix SASL examples (client and server)
fix SSL example
* write plugin support
qca-botan: implement
qca-egads (or qca-egd): implement for Random support
* possibilities for the future:
Key wrapping - RFC3217 and RFC3394
quoted-printable TextFilter
keygen on smart cards
keystore: symmetric keys, arbitrary app data
cms: fine-grained control over smime attribs
providers for:
Mozilla NSS
Windows CryptoAPI
Linux kernel crypto support, if the userspace API ever gets sorted out
Intel Performance Primatives library