@dijef I can see how encryption (and compression) would be implemented much better into the serializer. I was thinking of providing a simple listener interface that acts right at the beginning for deserialization, converting the encrypted value into a normal buffer and at the end for serialization: when the buffer is created, before returning is encrypted.
Providing a listener could be the quick solution. The best would be providing the listener and a pluggable implementation (an implementation of the listener interface) that does the job of accepting the algorithm to use, keys, etc. So everybody can just configure and use it.
The next step could be allowing to encrypt/decrypt only specific buckets (by configuration) or even only specific properties (probably overkill).
@dijef if you can find time to draft an implementation it would be awesome.
Originally posted by @lvca in #535 (reply in thread)
@dijef I can see how encryption (and compression) would be implemented much better into the serializer. I was thinking of providing a simple listener interface that acts right at the beginning for deserialization, converting the encrypted value into a normal buffer and at the end for serialization: when the buffer is created, before returning is encrypted.
Providing a listener could be the quick solution. The best would be providing the listener and a pluggable implementation (an implementation of the listener interface) that does the job of accepting the algorithm to use, keys, etc. So everybody can just configure and use it.
The next step could be allowing to encrypt/decrypt only specific buckets (by configuration) or even only specific properties (probably overkill).
@dijef if you can find time to draft an implementation it would be awesome.
Originally posted by @lvca in #535 (reply in thread)