On Wed, May 16, 2012 at 5:30 PM, David Sommerseth
<openvpn.l...@topphemmelig.net> wrote:
>> But now that you describe you can do this using the plugin API,
>> why not modify the plugin to perform this and just remove this?
>
> I don't know if I'm the only user of this information or not.  If I'm
> not, then we will break things for others as well.  That I don't like,
> especially when the current implementation covers both plug-ins and
> scripts.

Well, this is exactly my point in rejecting these kind of merges into
the code, examples: Android case, Windows privilege separation case.
A great example!

There are no temporary merges, only maintenance costs and code complexity.
This why features should be maintained outside of tree until properly
merged with proper design.
This process it is not unique to this project.

I am for announcing the removal have the time for all plugins authors
which may use this feature to modify their code. There is enough time
to do so, we are talking about ~5 months.

I am not sure that anyone knows this one even exists as was unique to
David's need. So most probably only the eurephia should be modified.

Samuli, I think it is simple enough... in the 2.3_alpha2 announcement,
announce that the tls_digest_* environment is obsolete and until 2.3
release all plugins authors must modify their plugins to use the V3
interface to extract this information (if needed).

Alon.

Reply via email to