That's the thing, JSSE is an add-on encryption component in Java. If the
product requires it, you have to register it.
Ideally the product shouldn't require it and make it an optional feature to
enable.
The latter is just my $0.02
John
On May 4, 2016 21:30, "Ted Dunning" wrote:
I am pretty du
I am pretty dubious that simply building a credential store using standard
JSSE requires registration. Same for HTTPS support.
On Wed, May 4, 2016 at 6:23 PM, Ted Dunning wrote:
>
> My guess is that this would fall to me.
>
> There is considerable analysis to be done to determine whether filin
My guess is that this would fall to me.
There is considerable analysis to be done to determine whether filing is
required.
Are you guys documenting the decision points?
On Wed, May 4, 2016 at 4:45 AM, Stian Soiland-Reyes
wrote:
> On 2 May 2016 at 03:23, Stian Soiland-Reyes wrote:
>
> > Form
You now have access to edit the report.
On Wed, May 4, 2016 at 9:01 PM Ed Cable wrote:
> User Name is EdwardCable
>
User Name is EdwardCable
On 2 May 2016 at 03:23, Stian Soiland-Reyes wrote:
> Formally - would it need to be the Incubator PMC chair sending the
> ECCN encryption email?
Could anyone from IPMC (e.g. our mentors) do it, or just Ted Dunning?
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubat
