-1. I think that encryption and/or compression should be supported by
the network layer and not by input/output ports. It should be property
of a stream like stream locality or globally enabled for a DAG. There is
not much point to have EncryptedInputPort for thread or container local
streams. It is not clear how to handle encrypted port connected to a
regular port.
Thank you,
Vlad
On 12/14/15 22:30, Priyanka Gugale wrote:
Sounds good. This is good feature for banks and security domain.
One suggestion: We can do key management ourself at application (may be by
providing default keys) and there should be an option to override keys if
user really want to do so.
-Priyanka
On Tue, Dec 15, 2015 at 11:37 AM, Chinmay Kolhatkar <[email protected]
wrote:
Hi All,
I wanted to propose an idea using which one can have encrypted stream
flowing in a DAG.
Basically, the idea is to create a new EncryptedInputPort which will extend
from DefaultInputPort and will return a StreamCodec object which will take
care of encryption/decryption.
As the same StreamCodec object will be used at OutputPort, the encryption
can be done in toByteArray method at Output port and decryption can be done
in fromByteArray at Input port.
By default we can support some basic encryption algorithms like RSA and DSA
where user need to provide the key(s) to EncryptedInputPort.
Any thoughts?
~ Chinmay.
