javadoc updates for SKM changes

This commit is contained in:
zzz
2009-08-30 16:04:28 +00:00
parent 80f9f857e5
commit 62a3da2fa6
2 changed files with 13 additions and 5 deletions

View File

@ -388,9 +388,13 @@ public class I2PAppContext {
* The session key manager which coordinates the sessionKey / sessionTag * The session key manager which coordinates the sessionKey / sessionTag
* data. This component allows transparent operation of the * data. This component allows transparent operation of the
* ElGamal/AES+SessionTag algorithm, and contains all of the session tags * ElGamal/AES+SessionTag algorithm, and contains all of the session tags
* for one particular application. If you want to seperate multiple apps * for one particular application.
* to have their own sessionTags and sessionKeys, they should use different *
* I2PAppContexts, and hence, different sessionKeyManagers. * This is deprecated for client use, it should be used only by the router
* as its own key manager. Not that clients are doing end-to-end crypto anyway.
*
* For client crypto within the router,
* use RouterContext.clientManager.getClientSessionKeyManager(dest)
* *
*/ */
public SessionKeyManager sessionKeyManager() { public SessionKeyManager sessionKeyManager() {

View File

@ -59,14 +59,18 @@ public class ElGamalAESEngine {
} }
/** /**
* Decrypt the message using the given private key using tags from the given key manager. * Decrypt the message using the given private key using tags from the default key manager.
*
* @deprecated specify the key manager!
*/ */
public byte[] decrypt(byte data[], PrivateKey targetPrivateKey) throws DataFormatException { public byte[] decrypt(byte data[], PrivateKey targetPrivateKey) throws DataFormatException {
return decrypt(data, targetPrivateKey, _context.sessionKeyManager()); return decrypt(data, targetPrivateKey, _context.sessionKeyManager());
} }
/** /**
* Decrypt the message using the given private key. This works according to the * Decrypt the message using the given private key
* and using tags from the specified key manager.
* This works according to the
* ElGamal+AES algorithm in the data structure spec. * ElGamal+AES algorithm in the data structure spec.
* *
*/ */