I'm trying to write a package that links to the OpenSSL libs on the C side and communicates with another server that will be running Java's JCE. I can get the two to talk using DES ECB (and I expect Triple DES, but haven't tried that yet.) This is because both sides internally agree to use PKCS5 padding. But for DES CBC or others that want an IV, I'm not sure how to communicate the IV (or another padding scheme). Both sides use a binary shared key. I considered encoding it into the head of the transmission, sort of like the way the base64 salt is prepended to Unix passwords. But this is problematic. But I've read some stuff that indicates that some sort of this scheme exists already. Its not in the KeyAgreement stuff, which seems to want to open a socket based path between the two end points. This won't work in our case. I just need the entire ciphertext to be interpreted correctly by my libs on the other end. Can anyone help? Are there existing protocols for this sort of thing? Thanks Ed Ed Howland Director, Unix Development StreamSearch.com (314) 746-1827 (314) 406-6836 (mobile) ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
