[
https://issues.apache.org/jira/browse/LUCENENET-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shad Storhaug closed LUCENENET-502.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: Lucene.Net 3.6)
I am closing this as a won't fix based on the conversation I had with Microsoft
(see
[LUCENENET-574|https://issues.apache.org/jira/projects/LUCENENET/issues/LUCENENET-574]).
It is no longer considered a good practice to make classes serializable so
they can be made into "distributed objects". Instead, another more secure
serialization method should be used.
{quote}It's crucial that we state as often as possible that binary
serialization is not intended to be used for new applications but to make
porting from Desktop to Core easier. There are tons of security concerns that
are introduced by binary serialization, one of it is reading from a stream that
could be compromised (network transferred date, e.g. in remoting).{quote}
> Recreate the missing files needed to build Lucene.Net.Distributed
> -----------------------------------------------------------------
>
> Key: LUCENENET-502
> URL: https://issues.apache.org/jira/browse/LUCENENET-502
> Project: Lucene.Net
> Issue Type: Improvement
> Components: Lucene.Net Contrib
> Affects Versions: Lucene.Net 3.6
> Reporter: Zachary Gramana
> Priority: Minor
> Attachments: DistributedSearch.zip
>
>
> Zack Gramana - Recommend commit to trunk, and re-evaluate for 3.6 release.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
