-Re: [jira] [Commented] (FLUME-1424) File Channel should support encryption
Arvind Prabhakar 2012-08-10, 23:07
@Mike - please go ahead. I have done some preliminary analysis but no patch
yet. It is similar to what Ralph has suggested below but not based on
input/output streams. My findings are that it is possible to use built in
JCE supported algorithms such as PBEWithMD5AndDES but have not yet done a
performance impact analysis.
On Fri, Aug 10, 2012 at 3:31 PM, Ralph Goers <[EMAIL PROTECTED]>wrote:
> It would be great for you to pick this up. We need this at Intuit asap
> and we are planning on having one of our engineers work on it next week if
> no one here can do it first. What I had suggested was to have add a
> FlumeEventFactory that could be configurable. We could then use an
> EncryptedFlumeEventFactory that wraps the OutputStream with a
> CipherOutputStream and likewise when reading. Ideally, the key should be
> able to be stored either in the default keystore something pluggable.
> On Aug 10, 2012, at 3:22 PM, Mike Percy wrote:
> > @Arvind: JIRA is down but I would like to look @ this issue. Are you
> > working on a patch or can I pick this up?
> > Regards,
> > Mike
> > On Tue, Aug 7, 2012 at 12:37 AM, Arvind Prabhakar (JIRA) <
> [EMAIL PROTECTED]>wrote:
> >> [
> >> Arvind Prabhakar commented on FLUME-1424:
> >> -----------------------------------------
> >> Yes, the put records do store the data in them. We can perhaps start
> >> that as a first step and if more requirements pop-up, we can address
> >> in follow-up Jiras as necessary.
> >>> File Channel should support encryption
> >>> --------------------------------------
> >>> Key: FLUME-1424
> >>> URL: https://issues.apache.org/jira/browse/FLUME-1424
> >>> Project: Flume
> >>> Issue Type: Bug
> >>> Reporter: Arvind Prabhakar
> >>> Assignee: Arvind Prabhakar
> >>> When persisting the data to disk, the File Channel should allow some
> >> form of encryption to ensure safety of data.
> >> --
> >> This message is automatically generated by JIRA.
> >> If you think it was sent incorrectly, please contact your JIRA
> >> administrators:
> >> For more information on JIRA, see: