Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] ssl-based generic provider

Since I haven't heard any response to this, my plan is to go ahead and commit the addition of an ssl-based generic provider in the coming few days...assuming release for ECF 3.6 in late Feb/early March 2013.

One question for Markus and/or Wim: Do we have a CA-approved cert on our build machine at OSUOSL? Reason I would be helpful to be able to test this new provider in an actual use scenario...where the server has a CA-approved cert, so that clients...with a 'normal' cert store...can connect to the server.



On 12/29/2012 10:16 AM, Scott Lewis wrote:
Hi Folks,

I've been working on a contribution to address this bug:

Create generic provider that uses SSL transport

I've almost got it going/ready for testing, etc., but wanted to notify the community about one implication: The bundle org.eclipse.ecf.provider (where the generic provider is located), currently has a minimum execution environment set to CDC 1.1. The addition of this ssl-based generic provider requires that the minimum EE be set to jre 1.4 (because of dependence on, which is not included in CDC 1.1).

I don't really know of any consumers that are using CDC 1.1 any longer, so perhaps this affects no one, but I wanted to make sure before I make the change. If you are a consumer of ECF (this bundle) that is using CDC 1.1 then please let us know.



ecf-dev mailing list

Back to the top