[
https://issues.apache.org/jira/browse/PIRK-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15560695#comment-15560695
]
ASF GitHub Bot commented on PIRK-45:
------------------------------------
Github user wraydulany commented on the issue:
https://github.com/apache/incubator-pirk/pull/107
Ok, I've expurgated references (import and comment) to jackson in the code,
and I've run the style checker against the code i touched.
Additionally, I've investigated the problems with the 1:ES and 1:ESS tests
that I'm having, and I'm convinced that they are due to misconfiguration of the
cluster I'm testing on.
This passes the build tests and distributed tests 1:J, 1:JS, 1:JSS, 1:SS,
and 1:E for me. If anyone has been able to successfully execute the 1:ES and/or
1:ESS tests with this PR *and* fail them, please comment and kill this PR.
Otherwise, I'm going to move this from WIP to full PR in the late morning on
the US East Coast tomorrow.
> Remove dependency on Java serialization
> ---------------------------------------
>
> Key: PIRK-45
> URL: https://issues.apache.org/jira/browse/PIRK-45
> Project: PIRK
> Issue Type: Improvement
> Reporter: Tim Ellison
> Assignee: Walter Ray-Dulany
>
> Pirk should not depend upon Java serialization as a persistent object format.
> Maintaining support for a variety of versions of Java serialized form can be
> difficult, this includes both the querier and responder sides of a PIR.
> Alternative formats such as XML and JSON are more forgiving/extensible.
> Furthermore, and despite Pirk's trust between querier and responder, there
> are potential implications for loading the binary representation of Java's
> serialized instances as a vector for security vulnerabilities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
